I learned myself in the past with MRTG, Cacti, serverstats and now with Munin. All based on RRDtool solution.
I agree with :
It makes it easy to determine “what’s different today” when a performance problem crops up. It makes it easy to see how you’re doing capacity-wise on any resources.
I have not any experience with collectd but it may be a good other answer.
Some exemples
Watching time that is going on ; Monitor the passage of time
@fred1m, Glad to know that you are planning to work on this app. I see no objections to adding this app as long as there is at least one developer willing to maintain it.
Before you start, one consideration though: inspired your post, I began looking what other ways are available to provide this performance data. I found out about Cockpit’s integration of Performance Co-Pilot project.
Seems to provide the basic necessary monitoring by default (CPU, memory, disk and network).
Integrated into FreedomBox’s choice of web administrator tool, that is, Cockpit.
Live updates of data.
Has historic value storage.
Very easy to setup. I just did apt install cockpit-pcp and everything just worked.
No special authentication and web setup needed (it is part of Cockpit).
Has zoom in and zoom out with selection on the graph for time period. Maximum range I saw was only a week and not entire year you have shown me. This is still very useful I think.
Not as powerful as munin or other dedicated tools. This should be okay, however.
If this looks good, we can introduce a ‘Performance’ app in ‘System’ and install this package as part of that. Then redirect users to Cockpit web interface. This would be very straightforward to do. Let me know what you think. If you like it, you can pick up this task.
Metrics works well with in containers but with some Olimex SBC I observe that data from pcp may be not foundas in this issue or are not well dated as above.
My guess is that we may need to find a workaround the lack of good clock at early boot time and/or maybe a JS problem in cockpit code (unfortunately I still need to learn to debug with Firefox ).
By the way, doing tests to try understanding, it seems that disabling Performance App may not suspend cron pcp associated tasks, if I notice correctly this may be a kind of bug.