Integrate Kayenta with VictoriaMetrics TSDB as a Data Source

[maxkushnir]

Objective:
We aim to incorporate VictoriaMetrics TSDB as a data source in Kayenta, replacing the current dependency on Prometheus.

Current State:
Currently, Kayenta only supports the PrometheusRemoteService interface. However, there are discrepancies in the query paths between Prometheus and VictoriaMetrics, as outlined below:

Health Endpoints:

• VictoriaMetrics: victoriametrics.svc.cluster.local:8481/-/healthy
• Prometheus: prometheus.svc.cluster.local:9090/-/healthy

Query Endpoints:

• VictoriaMetrics: victoriametrics.svc.cluster.local:8481/select/0/prometheus/api/v1/query_range
• Prometheus: prometheus.svc.cluster.local:9090/api/v1/query_range

Examples:
For further reference, the API docs for VictoriaMetrics with examples of query endpoints can be found here.

Request:
We kindly request the addition of an additional interface specifically tailored for VictoriaMetrics within Kayenta. This would allow users to seamlessly select the desired interface based on their requirements.

Additional Information:

• Having support for VictoriaMetrics would enhance the flexibility and compatibility of Kayenta.
• The incorporation of VictoriaMetrics aligns with the growing adoption of this TSDB within our infrastructure.

[spinnakerbot]

This issue hasn't been updated in 45 days, so we are tagging it as 'stale'. If you want to remove this label, comment:

@spinnakerbot remove-label stale