I’m reaching out to get some guidance or insights to troubleshoot an issue 
I’ve encountered with the Prometheus GUI (Prometheus v2.51).

I have Prometheus targets instrumented with Java (using 
https://github.com/prometheus/client_java/releases/tag/v1.3.5). When 
scraping these targets, the metrics are collected successfully, and I can 
query them via PromQL. However, when I type these metric names into the 
Prometheus GUI’s query box, the metric types (e.g., counter, gauge) for 
some of these metrics do not appear on the right side of the 
auto-completion list as expected. For other metrics from the same targets, 
the types show up fine, so it seems inconsistent.

Here’s what I’ve checked so far:

   - The /metrics endpoints of the targets include # TYPE lines for all 
   metrics (e.g., # TYPE http_requests_total counter), and they look 
   correctly formatted.
   - The Prometheus server scrapes these endpoints without errors (scrape 
   status is "up" in the targets page).
   - When I query the metric type using the API endpoint 
   /api/v1/metadata?metric=<metric_name> for the affected metrics, I get an 
   empty result ({}), which suggests the type metadata isn’t being stored 
   in its cache or recognized by Prometheus for these metrics.
   
Has anyone else run into this behavior? Could it be related to the client 
library, the Prometheus server version? 

I’d appreciate any pointers on troubleshooting this

-- 
You received this message because you are subscribed to the Google Groups 
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to prometheus-users+unsubscr...@googlegroups.com.
To view this discussion visit 
https://groups.google.com/d/msgid/prometheus-users/1bde8dd6-7709-4087-a4ee-4abea9067d3an%40googlegroups.com.

Reply via email to