Download the PHP package code-tool/jaeger-client-symfony-bridge without Composer
On this page you can find all versions of the php package code-tool/jaeger-client-symfony-bridge. 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 jaeger-client-symfony-bridge
Symfony Bridge for Jaeger library
Getting started
Register JaegerBundle like any other bundle for Symfony 4+
Denylist sampling operations
This feature allows to disable sampling for deny-listed operations.
It will be useful when your infrastructure initiates some operations which you are not insterested for tracking in Jaeger.
Operation names used in package configuration refers to first (parent) span operation name (https://www.jaegertracing.io/docs/latest/architecture/#span).
Hint: if you use default name generator (class
\Jaeger\Symfony\Name\Generator\DefaultNameGenerator), your operation name for HTTP requests will be the same as matched symfony route name.
Example bundle config with denylist feature:
Name generation options
You can configure custom name generators based on regular expression pattern, which will be evaluated for operation name.
Configuration for this feature looks like key-value list, where key - regexp pattern, value - custom name generator DI service id (see details below).
Name generator should implement an Jaeger\Symfony\Name\Generator\NameGeneratorInterface interface.
As a custom name generator you can specify a full DI service id, or just the suffix if your name generator service is named as jaeger.name.generator.*.
Keys are considered body of the regular expression pattern, do not put any modifiers (e.g. /i, /g) or slashes; route of the request or name of the command should match to use alternative generator.
Expressions are checked top to bottom, if no match is found, default generator will be used
Example bundle config with name generation feature:
All versions of jaeger-client-symfony-bridge with dependencies
code-tool/jaeger-client-php Version ^3.4
symfony/config Version ^4.4|^5.4|^6.0|^7.0
symfony/console Version ^4.4|^5.4|^6.0|^7.0
symfony/dependency-injection Version ^4.4|^5.4|^6.0|^7.0
symfony/event-dispatcher Version ^4.4|^5.4|^6.0|^7.0
symfony/http-kernel Version ^4.4|^5.4|^6.0|^7.0
symfony/yaml Version ^4.4|^5.4|^6.0|^7.0
symfony/service-contracts Version ^2|^3