An [Azure Application Insights] exporter implementation for [OpenTelemetry Rust].
Disclaimer: This is not an official Microsoft product.
Configure the exporter:
```rust use opentelemetry::{global, sdk};
fn inittracer() { let instrumentationkey = "...".tostring(); let exporter = opentelemetryapplicationinsights::Exporter::new(instrumentationkey); let provider = sdk::Provider::builder() .withsimpleexporter(exporter) .build(); global::set_provider(provider); } ```
Then follow the documentation of [opentelemetry] to create spans and events.
OpenTelemetry and Application Insights are using different terminology. This crate tries it's best to map OpenTelemetry fields to their correct Application Insights pendant.
The OpenTelemetry SpanKind determines the Application Insights telemetry type:
| OpenTelemetry SpanKind | Application Insights telemetry type |
| -------------------------------- | ----------------------------------- |
| CLIENT, PRODUCER, INTERNAL | Dependency |
| SERVER, CONSUMER | Request |
The Span's list of Events are converted to Trace telemetry.
The Span's status determines the Success field of a Dependency or Request. Success is true if
the status is OK; otherwise false.
For INTERNAL Spans the Dependency Type is always "InProc" and Success is true.
The following of the Span's attributes map to special fields in Application Insights (the mapping tries to follow the OpenTelemetry semantic conventions for [trace] and [resource]).
| OpenTelemetry attribute key | Application Insights field |
| ------------------------------------------- | ------------------------------ |
| enduser.id | Context: Authenticated user id |
| service.namespace + service.name | Context: Cloud role |
| service.instance.id | Context: Cloud role instance |
| http.url | Dependency Data |
| db.statement | Dependency Data |
| http.host | Dependency Target |
| net.peer.name + net.peer.port | Dependency Target |
| net.peer.ip + net.peer.port | Dependency Target |
| db.name | Dependency Target |
| http.status_code | Dependency Result code |
| db.system | Dependency Type |
| messaging.system | Dependency Type |
| rpc.system | Dependency Type |
| "HTTP" if any http. attribute exists | Dependency Type |
| "DB" if any db. attribute exists | Dependency Type |
| http.url | Request Url |
| http.scheme + http.host + http.target | Request Url |
| http.client_ip | Request Source |
| net.peer.ip | Request Source |
| http.status_code | Request Response code |
All other attributes are be directly converted to custom properties.
For Requests the attributes http.method and http.route override the Name.
Huge thanks goes to [Denis Molokanov] for the amazing [appinsights] crate. Check it out if you want a more direct integration with Application Insights.
The only official documentation I could find is this one. Follow the links to see the data model and endpoint description.
Can I send telemetry to the Application Insights portal?
We recommend you use our SDKs and use the [SDK API]. There are variants of the SDK for various [platforms]. These SDKs handle buffering, compression, throttling, retries, and so on. However, the [ingestion schema] and [endpoint protocol] are public.
-- https://docs.microsoft.com/en-us/azure/azure-monitor/faq#can-i-send-telemetry-to-the-application-insights-portal