Lens: rancher prometheus monitoring integration

[borgez]

What would you like to be added:
rancher monitoring integration

Why is this needed:
lens not autodiscover rancher metrics

Environment you are Lens application on:

• Kubernetes distribution: Rancher
• Desktop OS: Windows

[piersdd]

+1

[gigo1980]

+1

[dorellang]

Any workaround to get this working?

[df-cgdm]

+1

[meanevo]

+1

Change Prometheus service address to cattle-prometheus/access-prometheus:80 may provides you some information (incomplete).

[nrccua-bryancusatis]

+1

[steebchen]

I can confirm using cattle-prometheus/access-prometheus:80 provides some information:

The main cluster master/worker cpu/memory dashboard does not work

and neither does the nodes overview:

However, individual selections of single resources (pods, deployments, replicasets, daemonsets, statefulsets) works:

The individual selection of nodes just shows requests & limits but not the actual usage.

---

This is already super amazing though. I love this tool! I think a "rancher" preset would probably make sense in the future :)

[steebchen]

Actually, it depends what default you choose - there seem to be difference between "Helm" and "Prometheus Operator", there are some things not working with one and some other things are not working with the other. I'd be happy to provide exact results what works with what if this would be needed.

[windworship]

+1

[maxisam]

@steebchen I can confirm it works on v2 as well

for V2 it is
cattle-monitoring-system/rancher-monitoring-prometheus:9090

It is kinda weird that it doesn't show all information for V2, because it seems to me v2 is pretty much just like a pre-installed Prometheus. I wonder if we need to add lens specific metric

https://github.com/lensapp/lens/blob/master/extensions/metrics-cluster-feature/resources/02-configmap.yml.hb