Skip to content
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

Closed
2 tasks done
stavros-k opened this issue Jan 10, 2023 · 7 comments
Closed
2 tasks done

[Add]: Victoria Metrics #6185

stavros-k opened this issue Jan 10, 2023 · 7 comments
Labels
New-App Categorises a PR or issue that references a new App.
Milestone

Comments

@stavros-k
Copy link
Member

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

  • I've checked all open and closed issues and my request is not there.
  • I've checked all open and closed pull requests and my request is not there.
@stavros-k stavros-k added the New-App Categorises a PR or issue that references a new App. label Jan 10, 2023
@stavros-k stavros-k added this to the TrueCharts 2023-Q2 milestone Jan 10, 2023
@stavros-k stavros-k self-assigned this Jan 10, 2023
@Ornias1993
Copy link
Member

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.

@stavros-k
Copy link
Member Author

stavros-k commented Jan 10, 2023

Their clustered deployment can work fine too, without operator and without need of crds.
Tho it will need the use of subchart for the storage node for example (so replicas can be scaled independently on each component). I'm willing to take a stub on it later this year

@Ornias1993
Copy link
Member

Their clustered deployment can work fine too, without operator and without need of crds. Tho it will need the use of subchart for the storage node for example (so replicas can be scaled independently on each component). I'm willing to take a stub on it later this year

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.

@stavros-k
Copy link
Member Author

Their clustered deployment can work fine too, without operator and without need of crds. Tho it will need the use of subchart for the storage node for example (so replicas can be scaled independently on each component). I'm willing to take a stub on it later this year

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.

@Ornias1993
Copy link
Member

Yeah, for external scraping it's a fine addition :)

@Ornias1993
Copy link
Member

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 :)

@Ornias1993 Ornias1993 closed this as not planned Won't fix, can't repro, duplicate, stale May 15, 2023
@truecharts-admin
Copy link
Collaborator

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

@truecharts truecharts locked and limited conversation to collaborators May 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
New-App Categorises a PR or issue that references a new App.
Projects
None yet
Development

No branches or pull requests

3 participants