You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-monitor/app/opentelemetry-enable.md
+13-26Lines changed: 13 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -339,7 +339,7 @@ You might want to update the [Cloud Role Name](app-map.md#understand-the-cloud-r
339
339
340
340
### [.NET](#tab/net)
341
341
342
-
Set the Cloud Role Name and the Cloud Role Instance via [Resource](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/resource/sdk.md#resource-sdk) attributes.
342
+
Set the Cloud Role Name and the Cloud Role Instance via [Resource](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/resource/sdk.md#resource-sdk) attributes. Cloud Role Name uses `service.namespace` and `service.name` attributes, although it falls back to `service.name` if `service.namespace` isn't set. Cloud Role Instance uses the `service.instance.id` attribute value. For information on standard attributes for resources, see [Resource Semantic Conventions](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/resource/semantic_conventions/README.md).
343
343
344
344
```csharp
345
345
// Setting role name and role instance
@@ -369,7 +369,7 @@ To set the cloud role instance, see [cloud role instance](java-standalone-config
369
369
370
370
### [Node.js](#tab/nodejs)
371
371
372
-
Set the Cloud Role Name and the Cloud Role Instance via [Resource](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/resource/sdk.md#resource-sdk) attributes.
372
+
Set the Cloud Role Name and the Cloud Role Instance via [Resource](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/resource/sdk.md#resource-sdk) attributes. Cloud Role Name uses `service.namespace` and `service.name` attributes, although it falls back to `service.name` if `service.namespace` isn't set. Cloud Role Instance uses the `service.instance.id` attribute value. For information on standard attributes for resources, see [Resource Semantic Conventions](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/resource/semantic_conventions/README.md).
373
373
374
374
```javascript
375
375
...
@@ -401,7 +401,7 @@ const meterProvider = new MeterProvider({
401
401
402
402
### [Python](#tab/python)
403
403
404
-
Set the Cloud Role Name and the Cloud Role Instance via [Resource](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/resource/sdk.md#resource-sdk) attributes.
404
+
Set the Cloud Role Name and the Cloud Role Instance via [Resource](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/resource/sdk.md#resource-sdk) attributes. Cloud Role Name uses `service.namespace` and `service.name` attributes, although it falls back to `service.name` if `service.namespace` isn't set. Cloud Role Instance uses the `service.instance.id` attribute value. For information on standard attributes for resources, see [Resource Semantic Conventions](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/resource/semantic_conventions/README.md).
405
405
406
406
```python
407
407
...
@@ -1210,6 +1210,8 @@ with tracer.start_as_current_span("hello", record_exception=False) as span:
1210
1210
---
1211
1211
1212
1212
### Add Custom Spans
1213
+
1214
+
You may want to add a custom span when there's a dependency request that's not already collected by an instrumentation library or an application process that you wish to model as a span on the end-to-end transaction view.
1213
1215
1214
1216
#### [.NET](#tab/net)
1215
1217
@@ -1445,9 +1447,9 @@ This section explains how to modify telemetry.
1445
1447
1446
1448
These attributes might include adding a custom property to your telemetry. You might also use attributes to set optional fields in the Application Insights schema, like Client IP.
1447
1449
1448
-
#### Add a custom property to a Trace
1450
+
#### Add a custom property to a Span
1449
1451
1450
-
Any [attributes](#add-span-attributes) you add to spans are exported as custom properties. They populate the _customDimensions_ field in the requests or the dependencies tables in Application Insights.
1452
+
Any [attributes](#add-span-attributes) you add to spans are exported as custom properties. They populate the _customDimensions_ field in the requests, dependencies, traces, or exceptions table.
1451
1453
1452
1454
##### [.NET](#tab/net)
1453
1455
@@ -1779,7 +1781,7 @@ You might use the following ways to filter out telemetry before it leaves your a
1779
1781
1780
1782
#### [Java](#tab/java)
1781
1783
1782
-
See [samplingoverrides](java-standalone-config.md#sampling-overrides-preview) and [Telemetryprocessors](java-standalone-telemetry-processors.md).
1784
+
See [samplingoverrides](java-standalone-config.md#sampling-overrides-preview) and [telemetryprocessors](java-standalone-telemetry-processors.md).
1783
1785
1784
1786
#### [Node.js](#tab/nodejs)
1785
1787
@@ -1900,7 +1902,7 @@ Use the add [custom property example](#add-a-custom-property-to-a-trace), but re
0 commit comments