Open flands opened 2 weeks ago
The dashboard does behave as it is designed. Only some of the services emit custom application metrics, and what you see are several of those custom metrics displayed. Do note that not all custom app metrics are on that dashboard.
I want to add infra metrics, but these are collected from the orchestration/infra layer and not the application layer. We have discussed it a couple of times in SIG meetings, and though we all want infra metrics for each component, doing it in a way that is packaged within the confines of the demo has proven to be the challenge.
Anything against adding docker_stats
receiver in the otelcol-config?
That would give us a couple of container metrics when running locally.
Then in the values.yaml
for helm we could add k8s related stuff.
The configs would differ from docker to k8s, but I guess this is expected anyways.
Anything against adding docker_stats receiver in the otelcol-config?
+1. I think it would make sense to create an issue just for container
related metrics. I was thinking of adding the container
filelog operator in the k8s deployment too.
@rogercoll: https://github.com/open-telemetry/opentelemetry-demo/pull/1650 WDYT?
Bug Report
Which version of the demo you are using? 1.10.0
Symptom
The Application metrics panels in the Grafana Demo Dashboard are not service specific like other panels on the dashboard. This is confusing and also results in missing observability
What is the expected behavior?
What is the actual behavior?
Reproduce
Start version 1.10, open Grafana, go to Dashboard > Demo > Demo Application, and scroll down to the Application Metrics panel.
Additional Context
Beyond demonstrating the stable capabilities of OTel components, the demo application should also demonstrate that you can achieve observability. The Grafana Demo dashboard doesn't achieve this today.
Not a regression - this problem has existed since 1.7.0 and likely earlier.