Instrumentation quality

The Instrumentation Quality page reports on the completeness of your instrumentation and recommends steps to improve it and get more value out of Application Observability.

Access the report by selecting the Quality report tab for a service. If there are issues, the tab shows a number that indicates how many there are.

The example screenshot shows a summary of the instrumentation and progress to complete instrumentation. The report highlights specific issues with links to this documentation for instructions to resolve.

Add the missing service.namespace attribute

Application Observability uses the service.namespace attribute to filter and group by a service’s namespace.

To address this issue, edit these attributes in your instrumentation setup.

Don’t use slashes in the service name or namespace attributes

Don’t use slashes (/) in the service.name or service.namespace attributes. People often use slashes to namespace services. The OpenTelemetry specification has a specific namespace attribute. If you use the namespace attribute correctly you can benefit from advanced group and filter features in Application Observability.

To address this issue, edit these attributes in your instrumentation setup.

Add missing Kubernetes attributes

If you use Kubernetes, include the k8s.cluster.name, k8s.namespace.name, and k8s.pod.name Kubernetes resource attributes to link Application and Kubernetes Observability and gain additional insights and easier workflows between the two products.

The easiest way to address this issue is to use the recommended Grafana Kubernetes Monitoring Helm chart.

Alternatively for advanced use cases, manually set up Grafana Alloy or an OpenTelemetry Collector with the k8sattributeprocessor activated.