Download the PHP package shish/microotlp without Composer
On this page you can find all versions of the php package shish/microotlp. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download shish/microotlp
More information about shish/microotlp
Files in shish/microotlp
Package microotlp
Short Description A minimal OpenTelemetry logging library
License MIT
Homepage https://github.com/shish/microotlp
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 microotlp
MicroOTLP
Because I don't want my logging framework to require a specific web serving framework @_@
MicroOTLP is a minimalistic OpenTelemetry Protocol (OTLP) client library for sending telemetry data (traces, metrics, and logs) to an OTLP collector or backend. It is designed to be lightweight and easy to integrate into various applications without the need for a full-fledged OpenTelemetry SDK.
Benefits
- Zero dependencies
- 40x faster than the official OpenTelemetry SDK for PHP
- No assumption for PSR-7/15/18/etc, frameworks, or logging libraries
Differences
- Simpler API -- less flexible, but covers all the common cases with much less code
Limitations
- Only supports HTTP transport for sending data
- Assumes one Trace per request (though you can create multiple
Clients if you want multiple traces) - Assumes metrics, logs, and traces are sent to the same Collector
Example
Performance
This is probably an unfair comparison because I don't have the OTLP SDK native extension installed (PRs to update the benchmark setup are welcome)
A loop of 10,000 x "create span, log message, end span":
In a more real-world use case, response times for my image gallery were typically around 50ms -- when I added OTSDK logging, that added 50ms of overhead; microotlp adds 1ms of overhead.
