On Site Monitoring
-
So I've been mulling over the idea of setting up monitoring on site at client's businesses. I was thinking of using something like an Intel NUC because its small and it can be kept out of the way. I'd just set up nagios to monitor whatever needed to be watched.
My question is, am I opening myself up to being blamed for every single thing that goes wrong? I figured it would be nice because I could know when things happen almost immediately. However I don't want to be responsible (blamed) for things going wrong and not knowing about them ( Sally's excel keeps crashing, why didn't you fix it).
How do you handle this type of stuff?
-
If you explain clearly what the monitor is for, and what it can't do to your client they should never blame you for it.
have you had similar experiences with this client?
-
@DustinB3403 said:
If you explain clearly what the monitor is for, and what it can't do to your client they should never blame you for it.
have you had similar experiences with this client?
I didn't have any certain one in mind. This was just a general concern.
-
@johnhooks said:
So I've been mulling over the idea of setting up monitoring on site at client's businesses. I was thinking of using something like an Intel NUC because its small and it can be kept out of the way. I'd just set up nagios to monitor whatever needed to be watched.
My question is, am I opening myself up to being blamed for every single thing that goes wrong? I figured it would be nice because I could know when things happen almost immediately. However I don't want to be responsible (blamed) for things going wrong and not knowing about them ( Sally's excel jeeps crashing, why didn't you fix it).
How do you handle this type of stuff?
One way to keep the liability off of you is to have a clearly defined list of things that are being monitored, have the point of contact sign off on this monitoring.
-
If you do IT, you are open to randomly being blamed for everything that fails. Welcome to working in the department of "magic and mysteries."
-
@coliver said:
@johnhooks said:
So I've been mulling over the idea of setting up monitoring on site at client's businesses. I was thinking of using something like an Intel NUC because its small and it can be kept out of the way. I'd just set up nagios to monitor whatever needed to be watched.
My question is, am I opening myself up to being blamed for every single thing that goes wrong? I figured it would be nice because I could know when things happen almost immediately. However I don't want to be responsible (blamed) for things going wrong and not knowing about them ( Sally's excel jeeps crashing, why didn't you fix it).
How do you handle this type of stuff?
One way to keep the liability off of you is to have a clearly defined list of things that are being monitored, have the point of contact sign off on this monitoring.
That's a good point. That will definitely be a part of this.
-
@scottalanmiller said:
If you do IT, you are open to randomly being blamed for everything that fails. Welcome to working in the department of "magic and mysteries."
Sometimes I get nervous about legal issues. Just for the fact that common sense cases have been lost, but maybe I just worry too much
-
@johnhooks It never hurts to CYA in any case! A little bit of paranoia can be a good thing.
-
Yes, even though it will not cause issues, you should still document and get approval for monitoring.
-
Having a generic monitoring agreement that you always have at the ready might be valuable.
