logfire-fleet-otel
OpenTelemetry auto-instrumentation for Python, under an OpAMP server.
Quickstart
Install it next to the instrumentations the application needs, then run the application under
opentelemetry-instrument with the server's address and key:
pip install logfire-fleet-otel opentelemetry-instrumentation-flask
OTEL_SERVICE_NAME=checkout \
OTEL_OPAMP_ENDPOINT=https://opamp.example.com/v1/opamp \
OTEL_OPAMP_HEADERS="Authorization=Bearer%20<key>" \
opentelemetry-instrument python app.py
In Logfire, Fleet → Connect an application gives the endpoint and the key. When it works, it says so once, with no logging setup:
OpAMP: connected to https://opamp.example.com/v1/opamp; this SDK is managed as checkout, instance <uid>
When it can't connect, it warns once, with what to check. The instance keeps its UID across restarts with no configuration (default-state-dir.md).
An application on the Logfire SDK calls logfire_fleet_otel.configure_logfire() in place of
logfire.configure() (pip install 'logfire-fleet-otel[logfire]'). One that sets its
OpenTelemetry SDK up in code already keeps that setup and calls logfire_fleet_otel.manage()
after it.
Everything else, including setting the SDK up in code with logfire_fleet_otel.configure(), is in
docs/python-otel.md.
Metadata
Release files for logfire-fleet-otel 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| logfire_fleet_otel-0.2.1-py3-none-any.whl | Python 3 | none | any | Details for logfire_fleet_otel-0.2.1-py3-none-any.whl |
Release files / logfire_fleet_otel-0.2.1-py3-none-any.whl
| Download URL | logfire_fleet_otel-0.2.1-py3-none-any.whl |
|---|---|
| Size | 45.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7e25a0086c0e3d5ec6797acb03b1840ae30b67097dad8606e6c97caa307c936c
|
|
BLAKE2b-256 checksum How to use checksums |
bf79787682bbd4582203ca4357d0371cda12a8a88df4576f42b170c3615d1cfa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logSecurity for logfire-fleet-otel 0.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
1 file in this release has been uploaded with provenance metadata.
Attestation for logfire_fleet_otel-0.2.1-py3-none-any.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
