OpenTelemetry traces for every usecase.
Generate and push OpenTelemetry Trace data to an endpoint in JSON format.
YouTube: tracepusher tracing a GitLab pipeline.
If you like tracepusher and want to do the same thing with logs, check out logpusher.
- .har file to OpenTelemetry Converter
- Trace Kubernetes Jobs and Cronjobs with OpenTelemetry
- Trace CICD Pipelines with OpenTelemetry
- Trace shell scripts with OpenTelemetry
- Trace Helm with OpenTelemetry
- 🆕 Tracking GitHub Codespace creation with OpenTelemetry
- Trace anything with OpenTelemetry!
See try tracepusher in-browser without installation.
See download and use tracepusher as a standalone binary
See use tracepusher as a Python script.
See use tracepusher as a docker image.
See run a CI pipeline step as a docker image with tracepusher.
See dry run mode flag.
See debug mode flag.
See time shifting.
See multi-span traces.
Only supported with
v0.6.0
and above.
See span attribute types.
Only supported with
v0.7.0
and above.
See span events.
Only supported with
v0.8.0
and above.
See span kind
Only supported with
v0.8.0
and above.
tracepusher will generate spans of n
seconds.
This behaviour can be overridden by using the --duration-type
parameter.
See duration type page.
Only supported with
v0.9.0
and above.
tracepusher users can set the status of the span (OK
, ERROR
or UNSET
).
Default is OK
.
See span status page.
Only supported with
v0.9.0
and above.
tracepusher users can set --insecure [false|true]
to allow sending spans to http://
vs. https://
endpoints.
Defaults to false
but behaviour differs by version.
See insecure flag for more info.
Only supported with
v0.10.0
and above.
tracepusher users can (optionally) set the span start time using the --start-time
flag. If unset, defaults to now
.
See start time flag for more info.
See OpenTelemetry Collector configuration
Do you use tracepusher? Thanks and we'd love to know!
Submit a PR and add your details to ADOPTERS.md
See FAQ.
See Breaking changes
Note: PyInstaller is platform dependent. You must build on whatever platform you wish to run tracepusher on.
When tracepusher is released, the build_standalone_binaries.yml workflow completes this step and uploads the resulting binaries to S3 where we (currently manually) attach each generated binary to the release notes.
python -m PyInstaller --onefile tracepusher.py
Run all build commands from the root directory:
docker buildx build --platform linux/arm64,linux/amd64 --push -t tracepusher:dev-ci -f ./docker/ci/Dockerfile .
docker buildx build --platform linux/arm64,linux/amd64 --push -t tracepusher:dev -f ./docker/standard/Dockerfile .
For Non-Developers
pip install -r requirements.txt
For Developers
pip install -r requirements-dev.txt
Run the test suite:
pytest
All contributions are most welcome!
Get involved:
- Tackle a good first issue
- Create an issue to suggest something new
- File a PR to fix something
Made with contrib.rocks.