-
Notifications
You must be signed in to change notification settings - Fork 217
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
Add support for VictoriaMetrics metrics storage backend #289
Comments
Hi, it looks interesting, I wasn't familiar with the project. If it supports the Influx line protocol, then it should be supported by k6 already, no? We're trying to limit the amount of output backends k6 supports directly, in favor of generic protocols that are supported by more than one service, so it's unlikely support for this will be part of k6 core. That said, it could be easily used as an output extension. |
Yes - it should work OK on data ingestion side. As for data querying side, then the output extension for VictoriaMetrics looks like a way to go. |
I see that VictoriaMetrics also supports statsd metrics, which k6 is capable of outputting, and supports Prometheus remote_write, which we plan to add in k6 (grafana/k6#1761). So, given that we currently have 2 ways to send data to it, and we plan to have a 3rd one in the near future, I'll move this issue to the docs repo - I don't think we need a 4th way to send data to it, but should document the ones we already have... 😅 |
@valyala, we'd love a pull request adding information on how to use it with VictoriaMetrics! 👍🏽 |
A useful feature. |
Feature Description
It would be great to add support for VictoriaMetrics as metrics storage backends for k6.
VictoriaMetrics supports data ingestion via Influx line protocol (see these docs). It supports PromQL-based query language - MetricsQL, which is better suited for typical monitoring tasks and graph building than InfluxQL or Flux. See this PromQL tutorial for details. VictoriaMetrics is compatible with Prometheus datasource in Grafana - see these docs.
The text was updated successfully, but these errors were encountered: