-
opentelemetry-examples
Example code and resources for working with OpenTelemetry, provided by Lightstep
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
More specifically, auto-instrumentation uses shims or bytecode instrumentation agents to intercept your code at runtime or at compile-time to add tracing and metrics instrumentation to the libraries and frameworks you depend on. The beauty of auto-instrumentation is that it requires a minimum amount of effort. Sit back, relax, and enjoy the show. A number of popular Python libraries are auto-instrumented, including Flask and Django. You can find the full list here.
Note how we don’t have to set a LS_ACCESS_TOKEN, since that’s already configured in the Collector’s config.yml file. Just make sure that you have a running OTel Collector instance!
If you thought it was easy-peasey to send OTel data to Lightstep à la auto-instrumentation agent, then it’s even easier to do it via the OTel Python Launcher! Think of it as an OTel wrapper to make it extra-easy to send data to Lightstep, by having a bunch of things pre-configured for you to lower that barrier to entry.
We need to force a specific version of protobuf because of Launcher compatibility issues with newer versions. This was already fixed in opentelemetry-python.
A basic understanding of Python and Python virtual environments
Related posts
-
What existing libraries are there for implementing Kubernetes liveness and readiness probes?
-
Honeycomb, Python, and I: an OpenTelemetry Horror Story (With a Happy Ending)
-
Pydantic Logfire
-
Did OpenTelemetry deliver on its promise in 2023?
-
Show HN: Digma.ai – A full-blown APM running in the IntelliJ IDE