yep, seems to be about that for each 24 hour period for the last week atleast
but can’t exclude that its not my scripts failing, but i haven’t have problems with these particular ones, but i haven’t fully checked them… just seemed weird
maybe it is just the zfs compression
NAME PROPERTY VALUE SOURCE
bitpool/storjlogs type filesystem -
bitpool/storjlogs creation Thu Jun 3 15:46 2021 -
bitpool/storjlogs used 3.72G -
bitpool/storjlogs available 5.88T -
bitpool/storjlogs referenced 3.72G -
bitpool/storjlogs compressratio 4.67x -
bitpool/storjlogs mounted yes -
seems like a no the zfs compression is much higher than just 2x
which leads me back to … weird.
scanned through my logs and i can’t see any gaps over a 24 hour period
Currently I am using these 3 calls to count the audit, error and fatal cases, and alerting via Discord. That’s really working amazingly, I’ll share what I’ve done later some day.
Technical question meanwhile: I want to group and count the subsequent causes of the error messages in order to include it in the notification.
I want to immediately see, what’s going wrong and how fast I need to respond. E.g. “ERROR: satellite ping timeout (#1). Is there an easy way to do so? (Linux bash + docker; # = count)