Thomas,
Can you explain in what fashion you want to modify robinhood startup? I
am not sure to understand.
I was planning to adjust it to handle each file system individually but
after reading the script I saw you already have it set up with that
flexibility. I implemented the check_mk fix b
On 07/14/15 17:47, Jesse Stroik wrote:
> Thomas,
>
> What we'd like to do is set up a reliable check_mk alert. We now rely
> on robinhood for managing certain aspects of our file systems. If it
> is down overnight that's significant.
>
> We'd been monitoring the changelogs but given the batching,
Thomas,
What we'd like to do is set up a reliable check_mk alert. We now rely on
robinhood for managing certain aspects of our file systems. If it is
down overnight that's significant.
We'd been monitoring the changelogs but given the batching, it's not
sufficiently responsive and it feels l
Hi Scott,
The information reported by "rbh-report -a" is not updated in real-time:
it is updated at regular interval (specified by "log::stats_interval"
config parameter).
Moreover, regarding you file creation test, there can be a delay between
the creation action and the time robinhood actual
Hello,
We have been trying to monitor robinhood by looking at the 'Last read
record time' in 'rbh-report -a' activity status.
Assuming our filesystems are sometimes just not doing anything, part of
this check first creates a new file on the filesystem.
I've found that this often shows no ch
