-
-
Notifications
You must be signed in to change notification settings - Fork 588
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]: Victoria Metrics #6185
Comments
Not going to work within our ecosystem. we heavily rely on prometheus operator. That was already hell to get solid, not going to redo it. |
Their clustered deployment can work fine too, without operator and without need of crds. |
The issue here is the fact we actually use the operator even for metrics scraping. It's kinda the industry standard to do it that way. So you can add this, it just wouldn't get integrated into anything. |
I see what you mean. I had totally "skipped" the scraping of the cluster. As my use case is very different (receiving metrics from external hosts) aka acting as a "storage" server. I'll see in due time how this is gonna be added. |
Yeah, for external scraping it's a fine addition :) |
We've decided to not-accept issues for chart requests anymore, because the vast majority of the issue tracker if flooded with them and we don't (and never have) actually plan to do anything with chart requests as maintainers. Please join the discord to continue discussing chart requests :) |
This issue is locked to prevent necro-posting on closed issues. Please create a new issue or contact staff on discord of the problem persists |
Short description of the app
VM is a prometheus drop in replacement, which according to benchmarks is far more lightweight and fast.
It also has an operator, which we can investigate.
The documentation feels a bit more polished than prometheus.
Sources
https://github.com/VictoriaMetrics/VictoriaMetrics/releases
I've read and agree with the following
The text was updated successfully, but these errors were encountered: