umbrellio / jaravel
Library for integration Laravel and Jaeger.
Installs: 24 269
Dependents: 0
Suggesters: 0
Security: 0
Stars: 8
Watchers: 6
Forks: 1
Open Issues: 0
Requires
- php: ^7.4|^8.0
- ext-json: *
- guzzlehttp/guzzle: ^6.0|^7.0
- laravel/framework: ^7.0|^8.0|^9.0|^10.0
- open-telemetry/opentelemetry: ^0.0.15
- php-http/guzzle7-adapter: ^1.0
- spatie/macroable: ^1.0
Requires (Dev)
- orchestra/testbench: ^6.17
- php-coveralls/php-coveralls: ^2.4
- umbrellio/code-style-php: ^1.2
This package is auto-updated.
Last update: 2024-10-24 21:50:41 UTC
README
Library that allows easy integrate your Laravel application with Jaeger (OpenTracing).
Installation
Installation can be done with composer
composer require umbrellio/jaravel
Usage
Jaravel is able to trace your incoming http requests, console command, your guzzle requests to other services and event your queued jobs.
You can check your configuration in jaravel.php. All configuration is described in comment blocks.
You can configure span name or tags for every type of span:
// config/jaravel.php ... 'http' => [ 'span_name' => fn (Request $request) => 'App: ' . $request->path(), 'tags' => fn (Request $request, Response $response) => [ 'type' => 'http', 'request_host' => $request->getHost(), 'request_path' => $path = $request->path(), 'request_method' => $request->method(), 'response_status' => $response->getStatusCode(), 'error' => !$response->isSuccessful() && !$response->isRedirection(), ], ... 'guzzle' => [ 'span_name' => Umbrellio\Jaravel\Configurations\Guzzle\SpanNameResolver::class, 'tags' => Umbrellio\Jaravel\Configurations\Guzzle\TagsResolver::class, ], ...
You can use any callable or fully qualified class name, that points to class
having __invoke
method (it will be initialized via Service Container,
so you can inject anything that you want in constructor). Its preferred way, if you are using
config:cache` Artisan command, because closures can't be serialized.
Params passed to callable depends on what type of span (http, console, etc).
Tracing incoming http requests
To enable tracing incoming http requests, you need to add middleware HttpTracingMiddleware
to specific routes or globally, for example.
Requests can be filtered via 'allow_request' or 'deny_request' callables. If 'allow_request' is defined, http request will be traced only if this callable will return true. After 'allow_request' Jaravel checks 'deny_request' callable, and doesn`t make a trace, if it returns false. If you dont want to filter any requests, you can skip this settings.
For example, if you want to trace only requests having '/api' in the path:
// config/jaravel.php ... 'http' => [ 'allow_request' => fn (Request $request) => str_contains($request->path(), '/api'), ...
If 'trace_id_header'
is configured, header with trace id will be added to response.
field.
Tracing console commands
Enabled by default.
It`s able to filter commands via 'filter_commands', that will not be traced:
// config/jaravel.php ... 'console' => [ 'filter_commands' => ['schedule:run'], ...
Tracing jobs
To start tracing your jobs and even relate it with parent span, you need just
add JobTracingMiddleware
to jobs:
<?php declare(strict_types=1); namespace App\Jobs; use Illuminate\Contracts\Queue\ShouldQueue; use Illuminate\Queue\InteractsWithQueue; use Umbrellio\Jaravel\Middleware\JobTracingMiddleware; class JaravelTestJob implements ShouldQueue { use InteractsWithQueue; public function handle() { ... } public function middleware() { return [new JobTracingMiddleware()]; } }
It recommends to use InteractsWithQueue
trait, because with this trait you can
use methods of Job
instance while tagging span for job:
// config/jaravel.php ... 'job' => [ 'tags' => fn ($realJob, ?Job $job) => [ 'type' => 'job', 'job_class' => get_class($realJob), 'job_id' => optional($job) ->getJobId(), 'job_connection_name' => optional($job) ->getConnectionName(), 'job_name' => optional($job) ->getName(), 'job_queue' => optional($job) ->getQueue(), 'job_attempts' => optional($job) ->attempts(), ], ], ...
Tracing outgoing http requests with Guzzle
To start tracing your Guzzle requests, you need just add middleware to your Guzzle client:
use GuzzleHttp\Client; use GuzzleHttp\HandlerStack; use Umbrellio\Jaravel\HttpTracingMiddlewareFactory; $stack = HandlerStack::create(); $stack->push(HttpTracingMiddlewareFactory::create()); $client = new Client(['handler' => $stack]);
To add tracing to all your requests you can bind above client to
GuzzleHttp\Client
in your Service Provider.
Making your own spans
If you need to make your own span, you can follow next example:
use App\Services\MyService; use OpenTracing\Tracer; use Umbrellio\Jaravel\Services\Span\SpanCreator; use Umbrellio\Jaravel\Services\Span\SpanTagHelper; // You should use dependency injection in your code, it`s just an example $spanCreator = app(SpanCreator::class); $myService = app(MyService::class); $tracer = app(Tracer::class); // First you need to create a span. It will be a child of current active span, if active span exists $span = $spanCreator->create('Call MyService'); // Do something $myService->doSomething(); // Close active scope (span will be finished automatically) and flush tracer. optional($tracer->getScopeManager()->getActive())->close(); $tracer->flush();
If you need to retrieve current trace id, you can use:
Umbrellio\Jaravel\Services\Span\ActiveSpanTraceIdRetriever::retrieve()
License
Released under MIT License.
Authors
Created by Vitaliy Lazeev.
Contributing
- Fork it ( https://github.com/umbrellio/jaravel )
- Create your feature branch (
git checkout -b feature/my-new-feature
) - Commit your changes (
git commit -am 'Add some feature'
) - Push to the branch (
git push origin feature/my-new-feature
) - Create new Pull Request