-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate Kayenta with VictoriaMetrics TSDB as a Data Source #6930
Labels
Comments
maxkushnir
changed the title
Kayenta support for Victoriametrics datastore
Integrate Kayenta with VictoriaMetrics TSDB as a Data Source
Mar 1, 2024
This issue hasn't been updated in 45 days, so we are tagging it as 'stale'. If you want to remove this label, comment:
|
This issue is tagged as 'stale' and hasn't been updated in 45 days, so we are tagging it as 'to-be-closed'. It will be closed in 45 days unless updates are made. If you want to remove this label, comment:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.svc.cluster.local:8481/-/healthy
prometheus.svc.cluster.local:9090/-/healthy
Query Endpoints:
victoriametrics.svc.cluster.local:8481/select/0/prometheus/api/v1/query_range
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:
The text was updated successfully, but these errors were encountered: