Metrics dashboard not available

NethServer Version: latest udates
Module: latest updates

Anybody else having issues accessing the default metric dahsboard please?

I updated metrics on 2 nodes earlier to 1.2.5 and it’s fine on both nodes I have it enabled on.

1 Like

Does it help to disable/reenable the Grafana dashboard in the UI?

Does it work in another browser? (cache issues)

Let’s check the configuration:

api-cli run module/metrics1/get-configuration

[root@srv01 ~]# api-cli run module/metrics1/get-configuration

{“grafana_path”: “grafana”, “mail_from”: “alertmanager@xxx.com”, “mail_to”: [“support@xxx.com”], “prometheus_path”: “”}


-2026-03-31T16:07:12+02:00 [1:metrics1:agent@metrics1] task/module/metrics1/a1d0a9d5-f9cc-4173-9f34-bd24fe82ac61: get-configuration/20read is starting
2026-03-31T16:07:13+02:00 [1:metrics1:agent@metrics1] task/module/metrics1/a1d0a9d5-f9cc-4173-9f34-bd24fe82ac61: action “get-configuration” status is “completed” (0) at step validate-output.json

No, I disabled and enabled is several times

No, different browser same issue

The dashboard link (hhtps://xxx.com/grafana) leads to

Not Found

The requested URL was not found on this server.


Apache/2.4.58 (Ubuntu) Server at xxx.com Port 80

Maybe xxx.com points to some webapp? I suspect the apache of the lamp app.

Does it work using the node IP?

Grafana should be reachable at

https://<node_fqdn_or_ip>/grafana

EDIT:

Find webapps using xxx.com in traefik:

grep -iR xxx.com /home/traefik1/.config/state/configs/
1 Like

You are on to something. I will check laten when I can access. Thx!

1 Like

It is, thanks for that. I installed LAMP and deployed vvveb, the node FQDN is srv01.xxx.xom and the LAMP deployment FQDN is xxx.com (set by the LAPM instance config).

So I wonder how the dashboard link works, for before LAMP deployment I could reach it.

The link just takes the hostname/IP from the browser, see ns8-core/core/ui/src/views/settings/SettingsMetrics.vue at 695043a8a9311906803dfd815cae84e95686d816 · NethServer/ns8-core · GitHub
So if you are accessing the cluster admin via xxx.com/cluster-admin, the dashboard link to Grafana dashboard is xxx.com/grafana

1 Like

Actually, that is exactly the problem. I can access /cluster-admin, but not /grafana

It could well be I misused DNS A record to point to xxx.com, whilst the node FQDN is node.xxx.com

1 Like