Where is my configuration wrong?

Grafana Configuration
1

Hello,
I’m a newbie in Grafana and Prometheus. I’m having some issues that I don’t know if it’s related to my configuration or something else. I did not make any changes to the Grafana configuration file and I just changed the Prometheus configuration file as follows:

# 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'

    # Override the global default and scrape targets from this job every 5 seconds.
    scrape_interval: 5s
    scrape_timeout: 5s

  - job_name: "Local_Linux"
    scrape_interval: 10s
    static_configs:
      - targets: ["localhost:9100"]

  - job_name: "Windows_10"
    scrape_interval: 10s
    static_configs:
      - targets: ["192.168.1.3:9182"]

  - job_name: "Windows_2"
    scrape_interval: 10s
    static_configs:
      - targets: ["192.168.1.3:9182"]

    # metrics_path defaults to '/metrics'
    # scheme defaults to 'http'.

#    static_configs:
#      - targets: ['localhost:9090']

  - job_name: node
    # If prometheus-node-exporter is installed, grab stats about the local
    # machine by default.
    static_configs:
      - targets: ['localhost:9100']

As you can see, I have only defined two jobs with different names and the same IP address 192.168.1.3.
These servers have been added to the dashboard:

History-4
History-41586×237 27.2 KB

When I click on the IP address in theInstance section, the server information disappears from the dashboard:

Error-1
Error-11583×580 29.5 KB

Which part of the configuration is this problem related to?

Thank you.

1 Like
2

Hi,
Is this a bug? Have others encountered this problem?

Cheers.

3

Hi,
When I click on the IP address in the instance, the value of the JOB field changes to ${__cell_4} and after this the information disappears!
Is there anyone else having this problem?

4

I take a look at the Grafana log:

logger=context userId=1 orgId=1 uname=admin t=2025-01-05T00:55:12.484588575-05:00 level=info msg="Request Completed" method=GET path=/api/live/ws status=400 remote_addr=[::1] time_ms=6 duration=6.548702ms size=12 referer= handler=/api/live/ws status_source=server

Why remote_addr=[::1]? Could this be a problem?