Replies: 2 comments 1 reply
-
Thank you a lot for pointing to this issue. I really appreciate it. Unfortunately I didn't follow these updates for awhile. I will update project as soon as possible. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
Thank you so much for the excellent demo system and the Grafana Dashboard with metrics.
I created a new application and wanted to use the dashboard. But it turned out that it doesn't show values.
I figured out that your application uses the "OpenTelemetry.Exporter.Prometheus.AspNetCore" Version="1.4.0-rc.1". This version of the package publishes instruments with names like
process_cpu_time_s
.But the package was updated in August with the following PR: open-telemetry/opentelemetry-dotnet#4753. It changes names to something like
process_cpu_time_seconds_total
. So, the dashboard doesn't work with new names.I'd really appreciate it if you had a chance to update your application with the latest OTEL Nuget packages and improve the dashboard.
P.S. I use a different architecture solution in my demo application. It pushes metrics to OTEL Collector. Then, Prometheus scrapes values from the collector. It looks a bit flexible because it is unnecessary to configure Prometheus to scrape metrics from all application instances. it is enough to scrape from the collector.
You can find my example here.
The docker-compose file for such approach is here.
My example is based on the following example.
The collector publishes metrics with names like
process_cpu_time
. So, the example above has own dashboard which works with the names.Best regards
Beta Was this translation helpful? Give feedback.
All reactions