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

Generate HTML down to node+plugin granularity rather than just node #1586

Open
ToxicFrog opened this issue Oct 27, 2023 · 0 comments
Open

Generate HTML down to node+plugin granularity rather than just node #1586

ToxicFrog opened this issue Oct 27, 2023 · 0 comments

Comments

@ToxicFrog
Copy link
Contributor

Is your feature request related to a problem? Please describe.

At the moment, the most granular pages munin-cron generates are a whole category (showing all plugins in that category across all systems) or a whole node (showing all plugins associated with that node). If you have a node with a lot of graphs -- which is easy to accomplish -- and graph_strategy cgi, the latter pages in particular can take a long time to load; and if you're trying to view a plugin quite far down the page, you may be waiting a while.

Describe the solution you'd like
In the Overview page, clicking on the node name should take you to the page containing all graphs for that node, as it does now, but clicking on a plugin name should take you to a page containing only the graphs generated by that plugin on that node, rather than just jumping you to a specific offset in the whole-node page.

Describe alternatives you've considered

  • graph_strategy cron -- this makes the pages load instantly, but munin-cron much slower, and it's wasteful since most of the graphs are never viewed.
  • generating my own more granular HTML after munin-cron runs, and patching the HTML already generated -- this would work, but it would be kind of a pain, and it would be nice to have this built in; also potential race conditions if I'm viewing the page while this script is running
  • browsing by category rather than node -- the mapping of categories to plugins is often very messy and unintuitive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant