Converged APM UI documentation #20889
Conversation
✅ Deploy Preview for docs-website-netlify ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Hi @alanwest 👋 Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days. We will automatically generate a preview of your request, and will comment with a link when the preview is ready (usually 10 to 20 minutes). |
|
|
||
| OpenTelemetry data is comprised of metrics, spans, and logs. The APM experience | ||
| primarily leverages metric data because OpenTelemetry metrics provides an | ||
| accurate representation of the throughput, response time, and error rate of |
There was a problem hiding this comment.
Throughput, response time, and error rate are the golden signals, but we use metrics in all places we due to better accuracy.
| OpenTelemetry’s semantic conventions. Refer to the [APM Service Metrics](#apm-service-metrics) | ||
| section for how this name is derived. | ||
|
|
||
| ##### Unknown transaction name |
There was a problem hiding this comment.
Should this be a more general section, since this advice applies to any metric which includes unknown?
|
|
||
| The Logs page provides tools for identifying problems and analyzing a service's logs. See [Use logs UI](/docs/logs/ui-data/use-logs-ui/) for more information. | ||
| The queries assume data is produced by the [OpenTelemetry Go runtime instrumentation library](https://github.com/open-telemetry/opentelemetry-go-contrib/tree/main/instrumentation/runtime). | ||
| Note, there are currently no semantic conventions for Go runtime metrics. |
There was a problem hiding this comment.
Ignore. Not ready for merging.