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 and processor info, marked
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
> better understand their
Thanks for the proposal Piotr. I like it a lot since it will help people to
better understand their system. I would also be in favour of adding them to
the system metrics. I think o.a.f.runtime.metrics.util.MetricUtils is the
right place to start. Given the small dependency footprint and the
compat
+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?
>
>
>> On Oct 4, 2017, at
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:
> - User, System, IOWait,
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 a