Alert Checks on Observium reports device down when they are actually not
Hi Team,
I have setup the following Alert on my Observium device. See attachment (Alert_DeviceDown).
I sometimes get the alerts that the device is down . See attachment (Devices_Down).
However, the devices were actually not down. So most likely it is the Server on which Observium is install, do not get a ping response from the switch(device we monitoring). I ran MTR tests between the Observium server and switch in question, I don't see any packet losses, but I do see average RTT of 0.2 ms and worst RTT as 3.8 ms. So, is it possible when Observium does not get a ping response from the switch in the desirable amount of time, it marks it DOWN. How this desirable amount is calculated. Is there way we can edit this? Or is there any other recommended way for monitoring the devices?
Thanks!
Regards Renuka
******************************************************************************** This e-mail is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this e-mail message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is prohibited. If you have received this e-mail in error, please notify the sender and destroy all copies of the transmittal.
Thank you University of Chicago Medicine and Biological Sciences ********************************************************************************
Hi,
You can set the timeout (500ms - 2s) in the config file or via the web configuration, and the number of retries as well.
Tom
On 2016-03-03 18:09, Arya, Renuka [MED] wrote:
Hi Team,
I have setup the following Alert on my Observium device. See attachment (Alert_DeviceDown).
I sometimes get the alerts that the device is down . See attachment (Devices_Down).
However, the devices were actually not down. So most likely it is the Server on which Observium is install, do not get a ping response from the switch(device we monitoring). I ran MTR tests between the Observium server and switch in question, I don't see any packet losses, but I do see average RTT of 0.2 ms and worst RTT as 3.8 ms. So, is it possible when Observium does not get a ping response from the switch in the desirable amount of time, it marks it DOWN. How this desirable amount is calculated. Is there way we can edit this? Or is there any other recommended way for monitoring the devices?
Thanks!
Regards Renuka
This e-mail is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this e-mail message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is prohibited. If you have received this e-mail in error, please notify the sender and destroy all copies of the transmittal.
Thank you University of Chicago Medicine and Biological Sciences
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Thanks Tom!
Where do we configure it via web? And what are the default values?
Thanks!
Regards Renuka ________________________________ From: observium [observium-bounces@observium.org] on behalf of Tom Laermans [tom.laermans@powersource.cx] Sent: Thursday, March 03, 2016 11:40 AM To: Observium Network Observation System Subject: Re: [Observium] Alert Checks on Observium reports device down when they are actually not
Hi,
You can set the timeout (500ms - 2s) in the config file or via the web configuration, and the number of retries as well.
Tom
On 2016-03-03 18:09, Arya, Renuka [MED] wrote:
Hi Team,
I have setup the following Alert on my Observium device. See attachment (Alert_DeviceDown).
I sometimes get the alerts that the device is down . See attachment (Devices_Down).
However, the devices were actually not down. So most likely it is the Server on which Observium is install, do not get a ping response from the switch(device we monitoring). I ran MTR tests between the Observium server and switch in question, I don't see any packet losses, but I do see average RTT of 0.2 ms and worst RTT as 3.8 ms. So, is it possible when Observium does not get a ping response from the switch in the desirable amount of time, it marks it DOWN. How this desirable amount is calculated. Is there way we can edit this? Or is there any other recommended way for monitoring the devices?
Thanks!
Regards Renuka
******************************************************************************** This e-mail is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this e-mail message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is prohibited. If you have received this e-mail in error, please notify the sender and destroy all copies of the transmittal.
Thank you University of Chicago Medicine and Biological Sciences ********************************************************************************
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
******************************************************************************** This e-mail is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this e-mail message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is prohibited. If you have received this e-mail in error, please notify the sender and destroy all copies of the transmittal.
Thank you University of Chicago Medicine and Biological Sciences ********************************************************************************
Hi All,
Any word on this? Where can I make these changes from the web and check the existing settings? I think retries can be set from the "delay" parameter in the alert section, where can we set the timeout via web? Please advice!
Regards Renuka ________________________________ From: Arya, Renuka [MED] Sent: Thursday, March 03, 2016 11:43 AM To: Observium Network Observation System Subject: RE: [Observium] Alert Checks on Observium reports device down when they are actually not
Thanks Tom!
Where do we configure it via web? And what are the default values?
Thanks!
Regards Renuka ________________________________ From: observium [observium-bounces@observium.org] on behalf of Tom Laermans [tom.laermans@powersource.cx] Sent: Thursday, March 03, 2016 11:40 AM To: Observium Network Observation System Subject: Re: [Observium] Alert Checks on Observium reports device down when they are actually not
Hi,
You can set the timeout (500ms - 2s) in the config file or via the web configuration, and the number of retries as well.
Tom
On 2016-03-03 18:09, Arya, Renuka [MED] wrote:
Hi Team,
I have setup the following Alert on my Observium device. See attachment (Alert_DeviceDown).
I sometimes get the alerts that the device is down . See attachment (Devices_Down).
However, the devices were actually not down. So most likely it is the Server on which Observium is install, do not get a ping response from the switch(device we monitoring). I ran MTR tests between the Observium server and switch in question, I don't see any packet losses, but I do see average RTT of 0.2 ms and worst RTT as 3.8 ms. So, is it possible when Observium does not get a ping response from the switch in the desirable amount of time, it marks it DOWN. How this desirable amount is calculated. Is there way we can edit this? Or is there any other recommended way for monitoring the devices?
Thanks!
Regards Renuka
******************************************************************************** This e-mail is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this e-mail message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is prohibited. If you have received this e-mail in error, please notify the sender and destroy all copies of the transmittal.
Thank you University of Chicago Medicine and Biological Sciences ********************************************************************************
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
******************************************************************************** This e-mail is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this e-mail message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is prohibited. If you have received this e-mail in error, please notify the sender and destroy all copies of the transmittal.
Thank you University of Chicago Medicine and Biological Sciences ********************************************************************************
Hi,
I've checked and I don't see this configuration fields in the web section (at lease in the CE edition).
You should go and edit the config.php
Regards,
Pau
2016-03-07 17:28 GMT+01:00 Arya, Renuka [MED] < rarya@medicine.bsd.uchicago.edu>:
Hi All,
Any word on this? Where can I make these changes from the web and check the existing settings? I think retries can be set from the "delay" parameter in the alert section, where can we set the timeout via web? Please advice!
Regards Renuka ________________________________ From: Arya, Renuka [MED] Sent: Thursday, March 03, 2016 11:43 AM To: Observium Network Observation System Subject: RE: [Observium] Alert Checks on Observium reports device down when they are actually not
Thanks Tom!
Where do we configure it via web? And what are the default values?
Thanks!
Regards Renuka ________________________________ From: observium [observium-bounces@observium.org] on behalf of Tom Laermans [tom.laermans@powersource.cx] Sent: Thursday, March 03, 2016 11:40 AM To: Observium Network Observation System Subject: Re: [Observium] Alert Checks on Observium reports device down when they are actually not
Hi,
You can set the timeout (500ms - 2s) in the config file or via the web configuration, and the number of retries as well.
Tom
On 2016-03-03 18:09, Arya, Renuka [MED] wrote:
Hi Team,
I have setup the following Alert on my Observium device. See attachment (Alert_DeviceDown).
I sometimes get the alerts that the device is down . See attachment (Devices_Down).
However, the devices were actually not down. So most likely it is the Server on which Observium is install, do not get a ping response from the switch(device we monitoring). I ran MTR tests between the Observium server and switch in question, I don't see any packet losses, but I do see average RTT of 0.2 ms and worst RTT as 3.8 ms. So, is it possible when Observium does not get a ping response from the switch in the desirable amount of time, it marks it DOWN. How this desirable amount is calculated. Is there way we can edit this? Or is there any other recommended way for monitoring the devices?
Thanks!
Regards Renuka
This e-mail is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this e-mail message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is prohibited. If you have received this e-mail in error, please notify the sender and destroy all copies of the transmittal.
Thank you University of Chicago Medicine and Biological Sciences
observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
This e-mail is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this e-mail message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is prohibited. If you have received this e-mail in error, please notify the sender and destroy all copies of the transmittal.
Thank you University of Chicago Medicine and Biological Sciences
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Hi Pau,
I think this will help. See attachment! Just configured, haven't tested.
Thanks!
Regards Renuka ________________________________ From: observium [observium-bounces@observium.org] on behalf of KA PDE [kapde.cat@gmail.com] Sent: Monday, March 07, 2016 11:46 AM To: Observium Network Observation System Subject: Re: [Observium] Alert Checks on Observium reports device down when they are actually not
Hi,
I've checked and I don't see this configuration fields in the web section (at lease in the CE edition).
You should go and edit the config.php
Regards,
Pau
2016-03-07 17:28 GMT+01:00 Arya, Renuka [MED] <rarya@medicine.bsd.uchicago.edumailto:rarya@medicine.bsd.uchicago.edu>: Hi All,
Any word on this? Where can I make these changes from the web and check the existing settings? I think retries can be set from the "delay" parameter in the alert section, where can we set the timeout via web? Please advice!
Regards Renuka ________________________________ From: Arya, Renuka [MED] Sent: Thursday, March 03, 2016 11:43 AM To: Observium Network Observation System Subject: RE: [Observium] Alert Checks on Observium reports device down when they are actually not
Thanks Tom!
Where do we configure it via web? And what are the default values?
Thanks!
Regards Renuka ________________________________ From: observium [observium-bounces@observium.orgmailto:observium-bounces@observium.org] on behalf of Tom Laermans [tom.laermans@powersource.cxmailto:tom.laermans@powersource.cx] Sent: Thursday, March 03, 2016 11:40 AM To: Observium Network Observation System Subject: Re: [Observium] Alert Checks on Observium reports device down when they are actually not
Hi,
You can set the timeout (500ms - 2s) in the config file or via the web configuration, and the number of retries as well.
Tom
On 2016-03-03 18:09, Arya, Renuka [MED] wrote:
Hi Team,
I have setup the following Alert on my Observium device. See attachment (Alert_DeviceDown).
I sometimes get the alerts that the device is down . See attachment (Devices_Down).
However, the devices were actually not down. So most likely it is the Server on which Observium is install, do not get a ping response from the switch(device we monitoring). I ran MTR tests between the Observium server and switch in question, I don't see any packet losses, but I do see average RTT of 0.2 ms and worst RTT as 3.8 ms. So, is it possible when Observium does not get a ping response from the switch in the desirable amount of time, it marks it DOWN. How this desirable amount is calculated. Is there way we can edit this? Or is there any other recommended way for monitoring the devices?
Thanks!
Regards Renuka
******************************************************************************** This e-mail is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this e-mail message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is prohibited. If you have received this e-mail in error, please notify the sender and destroy all copies of the transmittal.
Thank you University of Chicago Medicine and Biological Sciences ********************************************************************************
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org<mailto:observium@observium.orgmailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
******************************************************************************** This e-mail is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this e-mail message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is prohibited. If you have received this e-mail in error, please notify the sender and destroy all copies of the transmittal.
Thank you University of Chicago Medicine and Biological Sciences ******************************************************************************** _______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
******************************************************************************** This e-mail is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this e-mail message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is prohibited. If you have received this e-mail in error, please notify the sender and destroy all copies of the transmittal.
Thank you University of Chicago Medicine and Biological Sciences ********************************************************************************
What are you trying to accomplish with that alert?
Adam.
Sent from BlueMail
On Mar 9, 2016, 01:14, at 01:14, "Arya, Renuka [MED]" rarya@medicine.bsd.uchicago.edu wrote:
Hi Pau,
I think this will help. See attachment! Just configured, haven't tested.
Thanks!
Regards Renuka ________________________________ From: observium [observium-bounces@observium.org] on behalf of KA PDE [kapde.cat@gmail.com] Sent: Monday, March 07, 2016 11:46 AM To: Observium Network Observation System Subject: Re: [Observium] Alert Checks on Observium reports device down when they are actually not
Hi,
I've checked and I don't see this configuration fields in the web section (at lease in the CE edition).
You should go and edit the config.php
Regards,
Pau
2016-03-07 17:28 GMT+01:00 Arya, Renuka [MED] <rarya@medicine.bsd.uchicago.edumailto:rarya@medicine.bsd.uchicago.edu>: Hi All,
Any word on this? Where can I make these changes from the web and check the existing settings? I think retries can be set from the "delay" parameter in the alert section, where can we set the timeout via web? Please advice!
Regards Renuka ________________________________ From: Arya, Renuka [MED] Sent: Thursday, March 03, 2016 11:43 AM To: Observium Network Observation System Subject: RE: [Observium] Alert Checks on Observium reports device down when they are actually not
Thanks Tom!
Where do we configure it via web? And what are the default values?
Thanks!
Regards Renuka ________________________________ From: observium [observium-bounces@observium.orgmailto:observium-bounces@observium.org] on behalf of Tom Laermans [tom.laermans@powersource.cxmailto:tom.laermans@powersource.cx] Sent: Thursday, March 03, 2016 11:40 AM To: Observium Network Observation System Subject: Re: [Observium] Alert Checks on Observium reports device down when they are actually not
Hi,
You can set the timeout (500ms - 2s) in the config file or via the web configuration, and the number of retries as well.
Tom
On 2016-03-03 18:09, Arya, Renuka [MED] wrote:
Hi Team,
I have setup the following Alert on my Observium device. See attachment (Alert_DeviceDown).
I sometimes get the alerts that the device is down . See attachment (Devices_Down).
However, the devices were actually not down. So most likely it is the Server on which Observium is install, do not get a ping response from the switch(device we monitoring). I ran MTR tests between the Observium server and switch in question, I don't see any packet losses, but I do see average RTT of 0.2 ms and worst RTT as 3.8 ms. So, is it possible when Observium does not get a ping response from the switch in the desirable amount of time, it marks it DOWN. How this desirable amount is calculated. Is there way we can edit this? Or is there any other recommended way for monitoring the devices?
Thanks!
Regards Renuka
This e-mail is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this e-mail message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is prohibited. If you have received this e-mail in error, please notify the sender and destroy all copies of the transmittal.
Thank you University of Chicago Medicine and Biological Sciences
observium mailing list observium@observium.orgmailto:observium@observium.org<mailto:observium@observium.orgmailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
This e-mail is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this e-mail message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is prohibited. If you have received this e-mail in error, please notify the sender and destroy all copies of the transmittal.
Thank you University of Chicago Medicine and Biological Sciences
observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
This e-mail is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this e-mail message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is prohibited. If you have received this e-mail in error, please notify the sender and destroy all copies of the transmittal.
Thank you University of Chicago Medicine and Biological Sciences
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
That's a very weird alert configuration that will never fire...
On 08/03/2016 18:46, Arya, Renuka [MED] wrote:
Hi Pau,
I think this will help. See attachment! Just configured, haven't tested.
Thanks!
Regards Renuka ________________________________ From: observium [observium-bounces@observium.org] on behalf of KA PDE [kapde.cat@gmail.com] Sent: Monday, March 07, 2016 11:46 AM To: Observium Network Observation System Subject: Re: [Observium] Alert Checks on Observium reports device down when they are actually not
Hi,
I've checked and I don't see this configuration fields in the web section (at lease in the CE edition).
You should go and edit the config.php
Regards,
Pau
2016-03-07 17:28 GMT+01:00 Arya, Renuka [MED] <rarya@medicine.bsd.uchicago.edumailto:rarya@medicine.bsd.uchicago.edu>: Hi All,
Any word on this? Where can I make these changes from the web and check the existing settings? I think retries can be set from the "delay" parameter in the alert section, where can we set the timeout via web? Please advice!
Regards Renuka ________________________________ From: Arya, Renuka [MED] Sent: Thursday, March 03, 2016 11:43 AM To: Observium Network Observation System Subject: RE: [Observium] Alert Checks on Observium reports device down when they are actually not
Thanks Tom!
Where do we configure it via web? And what are the default values?
Thanks!
Regards Renuka ________________________________ From: observium [observium-bounces@observium.orgmailto:observium-bounces@observium.org] on behalf of Tom Laermans [tom.laermans@powersource.cxmailto:tom.laermans@powersource.cx] Sent: Thursday, March 03, 2016 11:40 AM To: Observium Network Observation System Subject: Re: [Observium] Alert Checks on Observium reports device down when they are actually not
Hi,
You can set the timeout (500ms - 2s) in the config file or via the web configuration, and the number of retries as well.
Tom
On 2016-03-03 18:09, Arya, Renuka [MED] wrote:
Hi Team,
I have setup the following Alert on my Observium device. See attachment (Alert_DeviceDown).
I sometimes get the alerts that the device is down . See attachment (Devices_Down).
However, the devices were actually not down. So most likely it is the Server on which Observium is install, do not get a ping response from the switch(device we monitoring). I ran MTR tests between the Observium server and switch in question, I don't see any packet losses, but I do see average RTT of 0.2 ms and worst RTT as 3.8 ms. So, is it possible when Observium does not get a ping response from the switch in the desirable amount of time, it marks it DOWN. How this desirable amount is calculated. Is there way we can edit this? Or is there any other recommended way for monitoring the devices?
Thanks!
Regards Renuka
This e-mail is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this e-mail message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is prohibited. If you have received this e-mail in error, please notify the sender and destroy all copies of the transmittal.
Thank you University of Chicago Medicine and Biological Sciences
observium mailing list observium@observium.orgmailto:observium@observium.org<mailto:observium@observium.orgmailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
This e-mail is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this e-mail message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is prohibited. If you have received this e-mail in error, please notify the sender and destroy all copies of the transmittal.
Thank you University of Chicago Medicine and Biological Sciences
observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
This e-mail is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this e-mail message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is prohibited. If you have received this e-mail in error, please notify the sender and destroy all copies of the transmittal.
Thank you University of Chicago Medicine and Biological Sciences
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Yeah, realized, it won't work.
I just want that rather using the default values of ping/snmp to determine the device it down it use the value I supply, such that if snmp > 100 ms & ping test > 100ms declare the device is down. So may should get rid of the first condition and keep the ping/snmp condition.
device_status equals 0 device_snmp &amp;amp;gt; xx ms device_ping &amp;amp;gt; xx ms ________________________________ From: observium [observium-bounces@observium.org] on behalf of Tom Laermans [tom.laermans@powersource.cx] Sent: Thursday, March 10, 2016 2:14 PM To: Observium Network Observation System Subject: Re: [Observium] Alert Checks on Observium reports device down when they are actually not
That's a very weird alert configuration that will never fire...
On 08/03/2016 18:46, Arya, Renuka [MED] wrote:
Hi Pau,
I think this will help. See attachment! Just configured, haven't tested.
Thanks!
Regards Renuka ________________________________ From: observium [observium-bounces@observium.orgmailto:observium-bounces@observium.org] on behalf of KA PDE [kapde.cat@gmail.commailto:kapde.cat@gmail.com] Sent: Monday, March 07, 2016 11:46 AM To: Observium Network Observation System Subject: Re: [Observium] Alert Checks on Observium reports device down when they are actually not
Hi,
I've checked and I don't see this configuration fields in the web section (at lease in the CE edition).
You should go and edit the config.php
Regards,
Pau
2016-03-07 17:28 GMT+01:00 Arya, Renuka [MED] <rarya@medicine.bsd.uchicago.edumailto:rarya@medicine.bsd.uchicago.edumailto:rarya@medicine.bsd.uchicago.edumailto:rarya@medicine.bsd.uchicago.edu>: Hi All,
Any word on this? Where can I make these changes from the web and check the existing settings? I think retries can be set from the "delay" parameter in the alert section, where can we set the timeout via web? Please advice!
Regards Renuka ________________________________ From: Arya, Renuka [MED] Sent: Thursday, March 03, 2016 11:43 AM To: Observium Network Observation System Subject: RE: [Observium] Alert Checks on Observium reports device down when they are actually not
Thanks Tom!
Where do we configure it via web? And what are the default values?
Thanks!
Regards Renuka ________________________________ From: observium [observium-bounces@observium.orgmailto:observium-bounces@observium.orgmailto:observium-bounces@observium.orgmailto:observium-bounces@observium.org] on behalf of Tom Laermans [tom.laermans@powersource.cxmailto:tom.laermans@powersource.cxmailto:tom.laermans@powersource.cxmailto:tom.laermans@powersource.cx] Sent: Thursday, March 03, 2016 11:40 AM To: Observium Network Observation System Subject: Re: [Observium] Alert Checks on Observium reports device down when they are actually not
Hi,
You can set the timeout (500ms - 2s) in the config file or via the web configuration, and the number of retries as well.
Tom
On 2016-03-03 18:09, Arya, Renuka [MED] wrote:
Hi Team,
I have setup the following Alert on my Observium device. See attachment (Alert_DeviceDown).
I sometimes get the alerts that the device is down . See attachment (Devices_Down).
However, the devices were actually not down. So most likely it is the Server on which Observium is install, do not get a ping response from the switch(device we monitoring). I ran MTR tests between the Observium server and switch in question, I don't see any packet losses, but I do see average RTT of 0.2 ms and worst RTT as 3.8 ms. So, is it possible when Observium does not get a ping response from the switch in the desirable amount of time, it marks it DOWN. How this desirable amount is calculated. Is there way we can edit this? Or is there any other recommended way for monitoring the devices?
Thanks!
Regards Renuka
******************************************************************************** This e-mail is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this e-mail message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is prohibited. If you have received this e-mail in error, please notify the sender and destroy all copies of the transmittal.
Thank you University of Chicago Medicine and Biological Sciences ********************************************************************************
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.orgmailto:observium@observium.orgmailto:observium@observium.org<mailto:observium@observium.orgmailto:observium@observium.orgmailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
******************************************************************************** This e-mail is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this e-mail message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is prohibited. If you have received this e-mail in error, please notify the sender and destroy all copies of the transmittal.
Thank you University of Chicago Medicine and Biological Sciences ******************************************************************************** _______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.orgmailto:observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
******************************************************************************** This e-mail is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this e-mail message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is prohibited. If you have received this e-mail in error, please notify the sender and destroy all copies of the transmittal.
Thank you University of Chicago Medicine and Biological Sciences ********************************************************************************
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
******************************************************************************** This e-mail is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this e-mail message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is prohibited. If you have received this e-mail in error, please notify the sender and destroy all copies of the transmittal.
Thank you University of Chicago Medicine and Biological Sciences ********************************************************************************
participants (4)
-
Adam Armstrong -
Arya, Renuka [MED] -
KA PDE -
Tom Laermans