You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be helpful if macmon pipe included a timestamp in its JSON output. Right now, the output provides various system metrics like CPU temperature, memory usage, and power consumption, but there's no way to know exactly when each data point was recorded. Adding a timestamp would make it easier to correlate these metrics with other logs or time-based analysis.
I'd like to see something added like:
"timestamp": "2025-02-10T18:02:23.000Z"
to each JSON object.
This could helps with log correlation and time-series analysis and makes it easier to debug performance issues by seeing when events happened.
Thank you for considering my request! I'm not skilled at coding, but I am happy to help in any way I can.
The text was updated successfully, but these errors were encountered:
Hi @cwawak. I can add a timestamp field to the json object. In general, metrics are executed at the same time when you receive them in pipe mode. Like power metrics are collected in multiple samples during the interval period and ram / etc just before sending the message to pipe.
It would be helpful if
macmon pipe
included a timestamp in its JSON output. Right now, the output provides various system metrics like CPU temperature, memory usage, and power consumption, but there's no way to know exactly when each data point was recorded. Adding a timestamp would make it easier to correlate these metrics with other logs or time-based analysis.I'd like to see something added like:
"timestamp": "2025-02-10T18:02:23.000Z"
to each JSON object.
This could helps with log correlation and time-series analysis and makes it easier to debug performance issues by seeing when events happened.
Thank you for considering my request! I'm not skilled at coding, but I am happy to help in any way I can.
The text was updated successfully, but these errors were encountered: