Skip to content

[Feature][0.12.0-Beta] Enhance Load Average Display, Charting & Alert Grouping#960

Merged
henrygd merged 7 commits intohenrygd:svenvg93-feat/load_averagefrom
svenvg93:feat/load_average
Jul 16, 2025
Merged

[Feature][0.12.0-Beta] Enhance Load Average Display, Charting & Alert Grouping#960
henrygd merged 7 commits intohenrygd:svenvg93-feat/load_averagefrom
svenvg93:feat/load_average

Conversation

@svenvg93
Copy link
Collaborator

@svenvg93 svenvg93 commented Jul 13, 2025

Summary

This PR enhances the recently added Load Averages feature by improving visibility, usability, and alert consolidation.

What’s Changed

System Table

  • Added the 1-minute load average alongside the existing 5- and 15-minute values.
    • We use the core count to calculate the bar.
  • Consolidated all three load averages into a single column, with a hover tooltip to reveal the 1m, 5m, and 15m figures.
Load averages in system table with tooltip

Historical Chart

  • Introduced a chart to track load average trends over time, giving users deeper insight into system performance.
Load average history chart

Alerts

  • Included the 1-minute load average in alert notifications for quicker spike detection.
  • Grouped all Load Average alerts into a single collapsible section to reduce dashboard clutter.
Collapsible load average alerts

Please review and let me know if any tweaks are needed!

@svenvg93 svenvg93 changed the title [Feature][0.120-Beta2] Enhance Load Average Display, Charting & Alert Grouping [Feature][0.12.0-Beta] Enhance Load Average Display, Charting & Alert Grouping Jul 13, 2025
@henrygd
Copy link
Owner

henrygd commented Jul 14, 2025

Thanks, the chart looks great.

I like the concept for load avg in the table, but increasing the row height decreases the number of systems in view, so I'd like keep things on one line.

We could show them inline like 0.53, 1.23, 0.86 since that's how they're usually presented (in the uptime command for example). The drawback is sorting. I'm not sure we can have three separate sort states. But we could just add them together and sort by total value.

I also want to add a setting to choose between displaying raw values or normalizing by cores. Then maybe an indicator dot like the one next to the agent version based on the normalized value.

What do you think?

@svenvg93
Copy link
Collaborator Author

svenvg93 commented Jul 14, 2025

I see what you mean, next to each other would be better in terms of space.
Quick adjustment;

Schermopname.2025-07-14.om.22.10.43.mov

The dots change based on the normalized value. Let me know if you like it, then I will commit it.

For the sorting; to simplify things, we can disable sorting for this column. The CPU Load column already reflects the load and is sortable.

@henrygd
Copy link
Owner

henrygd commented Jul 16, 2025

Thanks, that looks good. I'll also tweak it a bit after you commit to see what works.

Maybe we get rid of the slashes and just use a space in between like htop. And maybe even use a single dot indicator based on the highest value, just to shrink it a bit.

Initially I was on board with grouping the load average alerts, but on further reflection I think we should leave them at top level. What bothers me is having to click an extra time, which could be annoying if you want to go through the systems to check if a particular load average alert is active.

I know the dialog is getting pretty big, so I'll probably switch it to a sheet / sidebar component at some point. Besides that we're good to go 👍

@svenvg93
Copy link
Collaborator Author

svenvg93 commented Jul 16, 2025

I changed the alerts back to be ungrouped. Should be ready to go now!

I had some ideas for the alert dialog, I will post them in an discussion when I have something usefull to pitch 😉

@henrygd henrygd changed the base branch from main to svenvg93-feat/load_average July 16, 2025 20:02
@henrygd henrygd merged commit 7cdd090 into henrygd:svenvg93-feat/load_average Jul 16, 2025
1 check passed
@svenvg93 svenvg93 deleted the feat/load_average branch July 16, 2025 20:05
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