Skip to content

Commit a166ce3

Browse files
ggailey777BigMorty
andauthored
Apply suggestions from code review
Co-authored-by: Mike Morton <[email protected]>
1 parent fa24211 commit a166ce3

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/azure-functions/opentelemetry-howto.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ zone_pivot_groups: programming-languages-set-functions
1313

1414
[!INCLUDE [functions-opentelemetry-preview-note](../../includes/functions-opentelemetry-preview-note.md)]
1515

16-
This article shows you how to configure your function app to generate log and trace data in an OpenTelemetry format. Azure Functions generates telemetry data on your function executions from both the Functions host process and the language-specific worker process in which your function code runs. By default, this telemetry data is sent to Application Insights using the Application Insights SDK. However, you can also choose to export this data using OpenTelemetry semantics. While you can still use an OpenTelemetry format to send your data to Application Insights, you can now also export the same data to any other OpenTelemetry-compliant endpoint.
16+
This article shows you how to configure your function app to export log and trace data in an OpenTelemetry format. Azure Functions generates telemetry data on your function executions from both the Functions host process and the language-specific worker process in which your function code runs. By default, this telemetry data is sent to Application Insights using the Application Insights SDK. However, you can choose to export this data using OpenTelemetry semantics. While you can still use an OpenTelemetry format to send your data to Application Insights, you can now also export the same data to any other OpenTelemetry-compliant endpoint.
1717

1818
> [!TIP]
1919
> Because this article is targeted at your development language of choice, remember to choose the correct language at the top of the article.
@@ -66,9 +66,9 @@ Create specific application settings in your function app based on the OpenTelem
6666

6767
### [OTLP Exporter](#tab/otlp-export)
6868

69-
**`OTEL_EXPORTER_OTLP_ENDPOINT`**: the connection string for an OTLP exporter endpoint.
69+
**`OTEL_EXPORTER_OTLP_ENDPOINT`**: an OTLP exporter endpoint URL.
7070

71-
**`OTEL_EXPORTER_OTLP_HEADERS`**: (Optional) list of headers to apply to all outgoing data.
71+
**`OTEL_EXPORTER_OTLP_HEADERS`**: (Optional) list of headers to apply to all outgoing data. This is used by many endpoints to pass an API key.
7272

7373
If your endpoint requires you to set other environment variables, you need to also add them to your application settings. For more information, see the [OTLP Exporter Configuration documentation](https://opentelemetry.io/docs/languages/sdk-configuration/otlp-exporter/).
7474

0 commit comments

Comments
 (0)