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

[RFE] include pidstat data in sa data files #111

Open
pschiffe opened this issue Mar 31, 2016 · 4 comments
Open

[RFE] include pidstat data in sa data files #111

pschiffe opened this issue Mar 31, 2016 · 4 comments

Comments

@pschiffe
Copy link
Contributor

It would be useful to have historical pidstat data, to investigate which process misbehaved last night.

@sysstat
Copy link
Owner

sysstat commented Apr 1, 2016

Yes I can understand that having historical pidstat data can help troubleshoot problems.
But hey, I consider the idea to include those data in sa data files to be frightening...! Please tell me, you were just kidding?

@pschiffe
Copy link
Contributor Author

pschiffe commented Apr 1, 2016

Yeah, I thought you wouldn't like it from the techn. point of view. :-) I put it here because I think it's a really good feature to have. Maybe if it would be optional, off by default.. I don't know.. I don't want to scare you, so feel free to close this if you don't like it. (but I'm already thinking about optimizations like store the process name with params only once in data file, and then, it's again only just numbers.. ^^)

@akhiljalagam
Copy link

presently, I am using telegraf -> influxdb -> grafana for historical metrics data. but still pidstat is simple compared to grafana system. it's good to have sysstat/pidstat historical metrics.

@MrPippin66
Copy link

Including "pidstat" data in "sar" data is a data management problem. But I have to cast my vote to have the option of gathering this data for 'sar' reporting as well. It would really help to have the option after the fact to see what processes were consuming CPU resources during a given interval.

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

No branches or pull requests

4 participants