Error 404 Grafana Mimir

Grafana
1

Dears,

I’m trying to test Grafana Mimir for potential use in monitoring some servers and services in the future.

My test environment consists of the following:

  1. Instance1: A Vagrant virtual machine with Prometheus and Grafana Mimir installed.
  2. Instance2: A Vagrant virtual machine running node_exporter. Prometheus installed on Machine 1 collects data from it.
  3. Instance3: A Vagrant virtual machine running Telegraf, which sends data to the Prometheus installed on Machine 1.

The problem:

Everything seems to be working okay. When I access Prometheus via http://Instance1:9090, I can query it normally. When I access the others instances (on port 9100 and 9273), I can see the metrics collected for Prometheus. However, when I try to access Grafana Mimir at http://Instance1:9009/prometheus, I receive a “404 page not found” error.

  • My configuration:

On Instance1

Prometheus:

[…]
scrape_configs:

  • job_name: “prometheus”
    static_configs:
    • targets: [“localhost:9090”]
  • job_name: ‘node_exporter’
    file_sd_configs:
    • files:
      • node_exporter/nodes.json
        scrape_interval: 5s
  • job_name: ‘telegraf’
    static_configs:
    • targets: [‘intancia3:9273’]
      remote_write:
  • url: My_IP_Here:9009/api/v1/push

Grafana Mimir:

multitenancy_enabled: false

blocks_storage:
backend: filesystem
bucket_store:
sync_dir: /tmp/mimir/tsdb-sync
filesystem:
dir: /tmp/mimir/data/tsdb
tsdb:
dir: /tmp/mimir/tsdb

compactor:
data_dir: /tmp/mimir/compactor
sharding_ring:
kvstore:
store: memberlist

distributor:
ring:
instance_addr: 127.0.0.1
kvstore:
store: memberlist

ingester:
ring:
instance_addr: 127.0.0.1
kvstore:
store: memberlist
replication_factor: 1

ruler_storage:
backend: filesystem
filesystem:
dir: /tmp/mimir/rules

server:
http_listen_port: 9009
log_level: error

store_gateway:
sharding_ring:
replication_factor: 1

Of course, I plan to apply a more suitable configuration in production, but for initial tests, all I wanted was to see Grafana Mimir working so that I could then expand the testing.

What might be wrong in this case? Could someone help me ?

Thanks.

1 Like
2

I have kind of the same problem, but with mimir-distributed (installed with helm chart).
Any solution out there?

1 Like
3

Hi
did you tried to set the header ‘X-Scope-OrgID’ on datasource configuration ?
In conf file:

On UI:
image

1 Like
4

Yes
I did it
I think it solved the problem
Thanks for help