Skip to main content

Instrumentation Tools & Auto Instrumentation for OpenTelemetry Python

Project description

pypi

Installation

pip install opentelemetry-instrumentation

This package provides commands that help automatically instrument a program:

opentelemetry-bootstrap

opentelemetry-bootstrap [-a |--action=][install|requirements]

This command install default instrumentation packages and detects active Python site-packages to figure out which instrumentation packages the user might want to install. By default, it prints out a list of the default and detected instrumentation packages that can be added to a requirements.txt file. It also supports installing the packages when run with --action=install or -a install flag. All default and detectable instrumentation packages are defined here <https://github.com/open-telemetry/opentelemetry-python-contrib/blob/main/opentelemetry-instrumentation/src/opentelemetry/instrumentation/bootstrap_gen.py>.

opentelemetry-instrument

opentelemetry-instrument python program.py

The instrument command will try to automatically detect packages used by your python program and when possible, apply automatic tracing instrumentation on them. This means your program will get automatic distributed tracing without having to make any code changes. This will also configure a global tracer and tracing exporter as well as a meter and meter exporter. By default, the instrument command will use the OTLP exporter but this can be overridden.

The command supports the following configuration options as CLI arguments and environment variables:

  • --traces_exporter or OTEL_TRACES_EXPORTER

  • --metrics_exporter or OTEL_METRICS_EXPORTER

  • --distro or OTEL_PYTHON_DISTRO

  • --configurator or OTEL_PYTHON_CONFIGURATOR

The exporter options define what exporter destination to use and can be set to one or more exporter names (see below). You can pass multiple values to configure multiple exporters (e.g., zipkin_json,otlp).

  • Defaults to otlp.

  • Can be set to none to disable automatic tracer initialization.

  • Can be set to ‘console` to display JSON results locally.

Trace exporter names:

  • jaeger_proto

  • jaeger_thrift

  • opencensus

  • otlp

  • otlp_proto_grpc (deprecated)

  • otlp_proto_http (deprecated)

  • zipkin_json

  • zipkin_proto

Metric exporter names:

  • otlp

  • otlp_proto_grpc (deprecated)

  • prometheus

Note: The default transport protocol for otlp is gRPC.

  • --id-generator or OTEL_PYTHON_ID_GENERATOR

Used to specify which IDs Generator to use for the global Tracer Provider. By default, it will use the random IDs generator.

The code in program.py needs to use one of the packages for which there is an OpenTelemetry integration. For a list of the available integrations please check here

  • OTEL_PYTHON_DISABLED_INSTRUMENTATIONS

If set by the user, opentelemetry-instrument will read this environment variable to disable specific instrumentations. e.g OTEL_PYTHON_DISABLED_INSTRUMENTATIONS = “requests,django”

Examples

opentelemetry-instrument --traces_exporter console flask run --port=3000

The above command will pass --traces_exporter console to the instrument command and --port=3000 to flask run.

opentelemetry-instrument --traces_exporter zipkin_json,otlp celery -A tasks worker --loglevel=info

The above command will configure global trace provider, attach zipkin and otlp exporters to it and then start celery with the rest of the arguments.

opentelemetry-instrument --id_generator random flask run --port=3000

The above command will configure the global trace provider to use the Random IDs Generator, and then pass --port=3000 to flask run.

Programmatic Auto-instrumentation

from opentelemetry.instrumentation import auto_instrumentation
auto_instrumentation.initialize()

If you are in an environment where you cannot use opentelemetry-instrument to inject auto-instrumentation you can do so programmatically with the code above. Please note that some instrumentations may require the initialize() method to be called before the library they instrument is imported.

References

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

tapm_instrumentation-0.55.15.tar.gz (30.6 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

tapm_instrumentation-0.55.15-py3-none-any.whl (33.4 kB view details)

Uploaded Python 3

File details

Details for the file tapm_instrumentation-0.55.15.tar.gz.

File metadata

  • Download URL: tapm_instrumentation-0.55.15.tar.gz
  • Upload date:
  • Size: 30.6 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.12.2

File hashes

Hashes for tapm_instrumentation-0.55.15.tar.gz
Algorithm Hash digest
SHA256 6b49bdb3ce78cb2036e03c7c0de95687651a4a7400e9675e477c1487584455eb
MD5 3c940d6428856303369e993c3b1b4667
BLAKE2b-256 b6ad825c8b17972fadc2c2e76b1b8c40a97c22c8c213f49dbc07d8236cfb4387

See more details on using hashes here.

File details

Details for the file tapm_instrumentation-0.55.15-py3-none-any.whl.

File metadata

File hashes

Hashes for tapm_instrumentation-0.55.15-py3-none-any.whl
Algorithm Hash digest
SHA256 f3b49e72fbff47c278ee2390b806206973f0f8d1f7fec57ff62b4459352b7d8d
MD5 ff2b9344821796725936e3b37be29422
BLAKE2b-256 f71c58130d78de020b653556405b3419cd4de0ded1ff6a61d3a48ca928620e9b

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page