Download the PHP package taisph/laravel-opentracing without Composer
On this page you can find all versions of the php package taisph/laravel-opentracing. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package laravel-opentracing
OpenTracing for Laravel
Reference implementation of the OpenTracing API for Laravel including a server-less local tracer for application logging purposes.
See OpenTracing for more information.
Supported Clients
Currently supported clients:
- Local: No-op tracer used mainly for adding trace ids to logs.
- Jaeger: open source, end-to-end distributed tracing. See Jaeger and Jonah George's Jaeger Client PHP.
Note that a patched version of Jaeger Client PHP is currently required to retain PHP 5.6 support. If you need that in
your application, add the config below to your composer.json file in the repositories section.
Installation
Install the latest version using:
Copy the default configuration file to your application if you want to change it by running the command below. Note
that you have to use --force if the file already exists.
Basic Usage
Example setup
Example bootstrap/app.php file:
Tracing
To trace a specific process in your application you can wrap the process in a trace closure like below. This will take care of starting a new trace span and closing it again when the closure either returns or throws.
Nested traces are also possible like below. It will automatically take care of the span child/parent relations.
If you want to add context information or tags to your spans, it is possible like below.
Tracing Jobs
Configure your dispatcher to pipe jobs through the tracing pipe. This is similar to middleware, only for jobs.
Tracing Across Service Boundaries
Trace contexts can easily be used across services. If your application starts a tracing context, that context can be carried over HTTP to another service with an OpenTracing compatible implementation.
To automatically accept trace contexts from other services, add the tracing middleware to your application by adding it
to your app/Http/Kernel.php file like below:
Assuming your application uses GuzzleHttp for sending requests to external services, you can use the provided tracing handler when creating the client like below. This will automatically send the necessary trace context headers with the HTTP request to the external service.
Testing
docker run --rm -it -v $(pwd):/app php:5.6-cli-alpine /bin/sh -c 'apk add --no-cache $PHPIZE_DEPS && pecl install xdebug-2.5.5 && cd app && php -dzend_extension=xdebug.so vendor/bin/phpunit'
About
Requirements
- PHP 5.6 or newer.
Contributions
Bugs and feature requests are tracked on GitHub.
License
OpenTracing for Laravel is licensed under the Apache-2.0 license. See the LICENSE file for details.
All versions of laravel-opentracing with dependencies
guzzlehttp/guzzle Version ^6.2
illuminate/support Version ^5.4.36
jonahgeorge/jaeger-client-php Version dev-feature/php56
opentracing/opentracing Version 1.0.0-beta6
paragonie/random_compat Version ^2
psr/cache Version ~1.0.1