Re: System resource logger

2017-10-11 Thread Piotr Nowojski
I have decided to drop this static logged once part. Those are static informations, that user can obtain in some more conventional way. For now I have left cpu, memory, swap and network interfaces stats. Piotrek > On 5 Oct 2017, at 18:45, Bowen Li wrote: > > System

Re: System resource logger

2017-10-05 Thread Bowen Li
System and processor info, marked as 'logged once' in gist shared by Piotr, should still be logged instead of registered as metrics, right? On Thu, Oct 5, 2017 at 2:38 AM, Till Rohrmann wrote: > Thanks for the proposal Piotr. I like it a lot since it will help people to >

Re: System resource logger

2017-10-05 Thread Piotr Nowojski
+1 thanks for pointing this out. It makes sense to just expand those system metrics (I was not aware of them). > On Oct 4, 2017, at 6:07 PM, Greg Hogan wrote: > > What if we added these as system metrics and added a way to write metrics to > a (separate?) log file? > >

Re: System resource logger

2017-10-04 Thread Greg Hogan
What if we added these as system metrics and added a way to write metrics to a (separate?) log file? > On Oct 4, 2017, at 10:13 AM, Piotr Nowojski wrote: > > Hi, > > Lately I was debugging some weird test failures on Travis and I needed to > look into metrics like:

System resource logger

2017-10-04 Thread Piotr Nowojski
Hi, Lately I was debugging some weird test failures on Travis and I needed to look into metrics like: - User, System, IOWait, IRQ CPU usages (based on CPU ticks since previous check) - System wide memory consumption (including making sure that swap was disabled) - network usage - etc… Without