Thanks Brian for your reply... I see no error on collector log or on prometheus log... only from the TARGET (error) page on Prometheus.
I got 7 SQL endpoint.. and I isolate the one with the err. I see directly from the DB query that 2 row have NULL values? Could be this? Now I try with a REPLACE NULL value directly on the query.... but your advise... "If you save the scrape output, you can validate it with "promtool check metrics", it's a good point of view. I'll be back Thanks, ALEN Il giorno martedì 21 giugno 2022 alle 11:47:23 UTC+2 Brian Candler ha scritto: > Where *exactly* do you see that error? > > What do you see if you scrape your collector directly using curl? > > If you save the scrape output, you can validate it with "promtool check > metrics" > > On Tuesday, 21 June 2022 at 10:14:24 UTC+1 [email protected] wrote: > >> Hi all, I got this strange error... >> I don't see any error on my collector (it run from 6 month). >> I've just downloaded on my docker app, last version of Prometheus... >> but it's the same. >> >> The strange think is that my metric page give me output of data.. >> So I'm a little bit confused... could be a collector error? Or a >> prometheus internal err? >> >> >> - expected value after metric, got "MNAME" >> >> THANKS; Alen >> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/cf22edad-fe02-4bf1-becb-3ff9842afaa7n%40googlegroups.com.
