Skip to content

Commit 36edce3

Browse files
small adjustments
1 parent 8e40cb9 commit 36edce3

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/container-apps/opentelemetry-agents.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -197,7 +197,7 @@ You can control how an agent behaves based off data type and endpoint-related op
197197

198198
| Option | Example |
199199
|---|---|
200-
| Each data type (for instance: logs, metrics, and traces), is individually configured. | |
200+
| Select a data type. | You can configure logs, metrics, and/or traces individually. |
201201
| Enable or disable any data type. | You can choose to send only traces and no other data. |
202202
| Send one data type to multiple endpoints. | You can send logs to both DataDog and an OTLP-configured endpoint. |
203203
| Send different data types to different locations. | You can send traces to an OTLP endpoint and metrics to DataDog. |
@@ -327,7 +327,7 @@ These variables are only necessary if you're using both the managed OpenTelemetr
327327

328328
## OpenTelemetry agent costs
329329

330-
Customers are billed for the underlying compute of the agent. For details about billing, see [billing.md].
330+
Customers are billed for the underlying compute of the agent. For details about billing, see [./billing.md].
331331

332332
See the destination service for their billing structure and terms. For example, if you send data to both Azure Application Insights and Datadog, you're responsible for the charges applied by both services.
333333

0 commit comments

Comments
 (0)