Metrics (Grafana) not backed up, FQDN change, confusing naming

Support
,
1

Hi,

  1. I noticed that Metrics (aka Grafana installed by default, not as a seperate module) is seletable as an app in the logs, but is not selectable as an app in backup.
  2. Metrics is now reachable by default on https://FQDN/grafana, and it seems that this is an easy target for attackers (logs are flooded with login attempts. Obviously the standard name ‘grafana’ gives away the existence of it and being part of the main FQDN, not easy to manage by security measures. Can the FQDN for ‘Metrics’ be set just like all other apps?
  3. The naming convention of Metrics and Grafana is (to me at least) confusing. There is ‘Metrics, ‘Grafana aka as Metrics’ and there is te Grafana app. If one installs the Grafana app, sysadmins may find it confusing when referring to ‘Grafana’, which one?

ps. And I wonder why do we need a Grafana app now we have Metrics aka Grafana by default?

TIA

2
  1. Yes, it seems there’s no backup. Maybe because it’s usually working on the leader and shouldn’t be restored elsewhere?

From the docs:

Metrics and alerts are not preserved when the leader node is switched.

  1. You can change the grafana path, see Metrics and alerts — NS8 documentation
api-cli run module/metrics1/configure-module --data '{"prometheus_path": "prometheus", "grafana_path": "your_wanted_grafana_path"}'
  1. I think it’s due to the fact that the Grafana app exists for a long time but metrics was introduced as a new feature much later. Metrics focuses on monitoring of the NS8 so maybe the Grafana app is still nice to monitor other things. It’s also explained in the docs.
2 Likes
3

So basically a good old fashioned ‘RTFM’ reminder :wink:

Thanks!

2 Likes