Fix pod metrics in Lens for Prometheus as they display incorrect value which 2 x times bigger then actual value

[dragoangel]

What would you like to be added: Could you add an option that will allow passing custom query parameters for metrics requests?

Why is this needed: This is required for configuring aspects of monitoring, for example, pass timeout parameter to Prometheus. Also, not having the option to set query parameters when Lens is pointed to solutions like Thanos and Prometheus HA leading to displaying metrics wrongly. Lens will show duplicated data from HA, f.e.: pod CPU and RAM usage will be multiplied by the count of replicas in HA. To display data correctly and not fail on partial_response: dedup=1&partial_response=1 would help, but Lens does not accept query parameters in PROMETHEUS SERVICE ADDRESS unfortunately and does not have a separate field to add them.

Environment you are Lens application on:

• Kubernetes distribution: Rancher
• Metrics Prometheus type: Prometheus Operator
• Metrics Prometheus service: Thanos Query Frontend that query Prometheus in HA
• Desktop OS: Any