Microsoft Opentelemetry exporter for Azure Monitor — Azure SDK for Python 2.0.0 documentation

The exporter for Azure Monitor allows you to export tracing data utilizing the OpenTelemetry SDK and send telemetry data to Azure Monitor for applications written in Python.

Source code | Package (PyPi) | API reference documentation | Product documentation | Samples | Changelog

Getting started¶

Install the package¶

Install the Microsoft Opentelemetry exporter for Azure Monitor with pip:

pip install microsoft-opentelemetry-exporter-azuremonitor --pre

Prerequisites:¶

To use this package, you must have:

Authenticate the client¶

Interaction with Azure monitor exporter starts with an instance of the AzureMonitorSpanExporter class. You will need a connection_string to instantiate the object. Please find the samples linked below for demonstration as to how to authenticate using a connection string.

Create Exporter from connection string¶

from microsoft.opentelemetry.exporter.azuremonitor import AzureMonitorSpanExporterexporter = AzureMonitorSpanExporter( connection_string = os.environ["APPLICATIONINSIGHTS_CONNECTION_STRING "])

Key concepts¶

Some of the key concepts for the Azure monitor exporter include:

• Opentelemetry: Opentelemetry is a set of libraries used to collect and export telemetry data (metrics, logs, and traces) for analysis in order to understand your software’s performance and behavior.

• Instrumentation: The ability to call the opentelemetry API directly by any application is facilitated by instrumentaton. A library that enables OpenTelemetry observability for another library is called an Instrumentation Library.

• Trace: Trace refers to distributed tracing. It can be thought of as a directed acyclic graph (DAG) of Spans, where the edges between Spans are defined as parent/child relationship.

• Tracer Provider: Provides a Tracer for use by the given instrumentation library.

• Span Processor: A span processor allows hooks for SDK’s Span start and end method invocations. Follow the link for more information.

• Sampling: Sampling is a mechanism to control the noise and overhead introduced by OpenTelemetry by reducing the number of samples of traces collected and sent to the backend.

• AzureMonitorSpanExporter: This is the class that is initialized to send tracing related telemetry to Azure Monitor.

• Exporter Options: Options to configure Azure exporters. Includes connection_string, instrumentation_key, proxies, timeout etc.

For more information about these resources, see What is Azure Monitor?.

Examples¶

The following sections provide several code snippets covering some of the most common tasks, including:

Export Hello World Trace¶

import osfrom opentelemetry import tracefrom opentelemetry.sdk.trace import TracerProviderfrom opentelemetry.sdk.trace.export import BatchExportSpanProcessorfrom microsoft.opentelemetry.exporter.azuremonitor import AzureMonitorSpanExporterexporter = AzureMonitorSpanExporter( connection_string = os.environ["APPLICATIONINSIGHTS_CONNECTION_STRING "])trace.set_tracer_provider(TracerProvider())tracer = trace.get_tracer(__name__)span_processor = BatchExportSpanProcessor(exporter)trace.get_tracer_provider().add_span_processor(span_processor)with tracer.start_as_current_span("hello"): print("Hello, World!")

Modifying Traces¶

• You can pass a callback function to the exporter to process telemetry before it is exported.

• Your callback function can return False if you do not want this envelope exported.

• Your callback function must accept an envelope data type as its parameter.

• You can see the schema for Azure Monitor data types in the envelopes here.

• The AzureMonitorSpanExporter handles Data data types.

from microsoft.opentelemetry.exporter.azuremonitor import AzureMonitorSpanExporterfrom opentelemetry import tracefrom opentelemetry.sdk.trace import TracerProviderfrom opentelemetry.sdk.trace.export import BatchExportSpanProcessor# Callback function to add os_type: linux to span propertiesdef callback_function(envelope): envelope.data.baseData.properties['os_type'] = 'linux' return Trueexporter = AzureMonitorSpanExporter( connection_string='InstrumentationKey=<your-ikey-here>')# This line will modify telemetryexporter.add_telemetry_processor(callback_function)trace.set_tracer_provider(TracerProvider())tracer = trace.get_tracer(__name__)span_processor = BatchExportSpanProcessor(exporter)trace.get_tracer_provider().add_span_processor(span_processor)with tracer.start_as_current_span('hello'): print('Hello World!')

Instrumentation with requests library¶

OpenTelemetry also supports several instrumentations which allows to instrument with third party libraries.

This example shows how to instrument with the requests library.

• Install the requests integration package using pip install opentelemetry-instrumentation-requests.

import osimport requestsfrom opentelemetry import tracefrom opentelemetry.instrumentation.requests import RequestsInstrumentorfrom opentelemetry.sdk.trace import TracerProviderfrom opentelemetry.sdk.trace.export import BatchExportSpanProcessorfrom microsoft.opentelemetry.exporter.azuremonitor import AzureMonitorSpanExportertrace.set_tracer_provider(TracerProvider())tracer = trace.get_tracer(__name__)# This line causes your calls made with the requests library to be tracked.RequestsInstrumentor().instrument()span_processor = BatchExportSpanProcessor( AzureMonitorSpanExporter( connection_string = os.environ["APPLICATIONINSIGHTS_CONNECTION_STRING "] ))trace.get_tracer_provider().add_span_processor(span_processor)RequestsInstrumentor().instrument()# This request will be tracedresponse = requests.get(url="")

Troubleshooting¶

The exporter raises exceptions defined in Azure Core.

Next steps¶

More sample code¶

Please find further examples in the samples directory demonstrating common scenarios.

Additional documentation¶

For more extensive documentation on the Azure Monitor service, see the Azure Monitor documentation on docs.microsoft.com.

For detailed overview of Opentelemetry, visit their overview page.

Contributing¶

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit .

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Indices and tables¶

Developer Documentation