And for more info, here's from my prometheus.yml file:
# A scrape configuration containing exactly one endpoint to scrape:
# Here it's Prometheus itself.
scrape_configs:
# The job name is added as a label `job=<job_name>` to any timeseries
scraped from this config.
- job_name: 'prometheus'
static_configs:
- targets: ['localhost:10090']
On Thursday, February 11, 2021 at 4:57:44 PM UTC-5 Corey Abma wrote:
> Yes, I can confirm there's still an explicit scrape job. It even
> auto-fills in the graphing query console. I even get this from going to
> /metrics (see screenshot).
>
> [image: prometheus metrics results.png]
>
> On Thursday, February 11, 2021 at 4:53:40 PM UTC-5 Christian Hoffmann
> wrote:
>
>> Hi,
>>
>> On 2021-02-11 20:43, Corey Abma wrote:
>> > I recently updated my Prometheus to v2.24.1. I noticed that if I go to
>> > my endpoint localhost:10090/metrics, I can see Prometheus metrics (such
>> > as prometheus_target_interval_length_seconds) being published just
>> fine.
>> > However, if I go to the graphing console and type in that exact same
>> > metric, I get no results.
>> >
>> > Is anyone else experiencing this issue?
>>
>> Can you confirm that your config still contains a job to scrape these
>> metrics?
>>
>> Even for Prometheus' own metrics, an explicit scrape job is needed.
>>
>> You explicitly mention that you've updated. Do you suspect that this has
>> been different before? Is there a chance that your config was modified
>> during the update?
>>
>> Kind regards,
>> Christian
>>
>
--
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 on the web visit
https://groups.google.com/d/msgid/prometheus-users/ab567f49-8ff4-415c-8c57-28e8de884a27n%40googlegroups.com.
