Weird dates on logs being email to me from <no-reply@netdata.cloud>

Why am i getting years like “Warning for 292 y” and “Critical for 292 y”? Some of the warnings have valid dates and others are crazy, like:
lowest_entropy
Mon Jan 01 0001, 00:00:00 +0000

Warning for 292 y
disk_space_usage
Mon Jan 01 0001, 00:00:00 +0000

Warning for 292 y
web_log_last_collected_secs
Mon Jan 01 0001, 00:00:00 +0000

Critical for 292 y
load_average_1
Mon Jan 01 0001, 00:00:00 +0000

Warning for 292 y
ram_usage
Mon Jan 01 0001, 00:00:00 +0000

Warning for 292 y
10min_cpu_usage
Mon Jan 01 0001, 00:00:00 +0000

Warning for 292 y
disk_space_usage
Mon Jan 01 0001, 00:00:00 +0000

Warning for 292 y
disk_space_usage
Mon Jan 01 0001, 00:00:00 +0000

Warning for 292 y
disk_space_usage
Mon Jan 01 0001, 00:00:00 +0000

Hello @johnstonf,

Most likely it has to do with old/stale alarms in the Cloud.
Could you please verify if these alarms also appear in the agent’s dashboard?

It would also help if you could provide us your war room name to investigate Cloud’s data integrity specifically for your case.

1 Like

My war room namd is FJ
Thanks!

I’m experiencing the same problem. An old alarm named web_log_last_collected_secs is showing but this alarm does not show in the web agent. Netdata Cloud