Skip to content

Conversation

@valyala
Copy link
Contributor

@valyala valyala commented Oct 26, 2025

Thank you for taking the time to work on a PR for Awesome-Sysadmin!

To ensure your PR is dealt with swiftly please check the following:

  • Your additions are Free software
  • Software you are submitting is not your own, unless you have a healthy ecosystem with a few contributors (which aren't your sock puppet accounts).
  • Submit one item per pull request. This eases reviewing and speeds up inclusion.
  • Format your submission as follows, where Demo and Clients are optional.
    Do not add a duplicate Source code link if it is the same as the main link.
    Keep the short description under 80 characters and use sentence case
    for it, even if the project's webpage or readme uses another capitalisation.
    Demo links should only be used for interactive demos, i.e. not video demonstrations.
    - [Name](http://homepage/) - Short description, under 250 characters, sentence case. ([Demo](http://url.to/demo), [Source Code](http://url.of/source/code), [Clients](https://url.to/list/of/related/clients-or-apps)) `License` `Language`
  • Additions are inserted preserving alphabetical order.
  • Additions are not already listed at awesome-selfhosted
  • The Language tag is the main server-side requirement for the software. Don't include frameworks or specific dialects.
  • You have searched the repository for any relevant issues or PRs, including closed ones.
  • Any category you are creating has the minimum requirement of 3 items.
  • Any software project you are adding to the list is actively maintained.
  • The pull request title is informative, unlike "Update README.md".
    Suggested titles: "Add aaa to bbb" for adding software aaa to section bbb,
    "Remove aaa from bbb" for removing, "Fix license for aaa", etc.

Please take some time to answer the following questions as best you can:

  • Why is it awesome?

vmagent needs 10x less RAM than Prometheus in agent mode for collecting and forwarding the same amounts of metrics. It also uses 4x less network bandwidth for sending the collected metrics to the remote storage.

VictoriaMetrics needs up to 5x less RAM than Prometheus and up to 4x less disk space for storing the same metrics.

  • Have you used it? For how long?

Yes, for 7 years.

  • Is this in a personal or professional setup?

Professional setup.

  • How many devices/users/services/... do you manage with it?

Thousands of hosts and tens of thousands of applications.

  • Biggest pros/cons compared to other solutions?

Pros: vmagent and VictoriaMetrics are very resource-efficient.

Cons: I don't know :)

  • Any other comments about your use case, things you've found excellent, limitations you've encountered... ?

Copy link
Collaborator

@nodiscc nodiscc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am currently setting it up as well.
Not much to say. It just works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants