Re: [prometheus-users] Re: not able to see metrics from query browser even though end point is up and showing metrics through curl

I don't really understand what you're trying to say. Does your exporter include timestamps for each metric? These are optional. It's almost always best not to include them unless you are *really* sure you know what you're doing. Notice that none of the standard exporters, like

Re: [prometheus-users] Re: not able to see metrics from query browser even though end point is up and showing metrics through curl

up metric showing value 1 and alos targets it is showing up as well. is there nay time mismatch between prometheus server and exporter? if yes,, how could we disable it. On Sunday, June 28, 2020 at 6:44:57 AM UTC-5 b.ca...@pobox.com wrote: > tcpdump -i eth0 -nn -s0 -A host x.x.x.x and tcp port

Re: [prometheus-users] Re: not able to see metrics from query browser even though end point is up and showing metrics through curl

Hi Brian Candler wrote: "up" missing - scraping not configured. "up" has value 0 - unable to communicate or data is bad. "up" has value 1 - maybe partial scrape Check logs at prometheus and exporter; check traffic between prometheus and exporter with tcpdump. Can you show a sample tcpdump

[prometheus-users] Re: not able to see metrics from query browser even though end point is up and showing metrics through curl

Then you're probably not scraping it, or the custom exporter is returning invalid data. Check the value of the "up" metric in query browser for the given job and instance, i.e. up{job="foo",instance="bar"} "up" missing - scraping not configured. "up" has value 0 - unable to communicate or data