Re: [Observium] alert repeat?
I found an option to do ignore until ok on the interface settings. But it is really unrealistic to do this manually for hundreds of ports. Any easier way to achieve this? I do want to monitor ports status, but I don¹t want to get a flood of alerts every 24 hours. Thanks a lot.
On 10/22/14, 6:40 PM, "Zhenhui Liang" ZhenhuiLiang@eharmony.com wrote:
Hi,
We have some switches with thousands of ports. I know, we don¹t have administrative down for unused ports. So I set up port down alerts for all ports, so that the initial alert of the down ports, I just ignore so I know those are ports already down. So the theory is that for any following alerts, I will look into them.
But I found out observium will send out the massive port down alerts exactly in 24 hours frequency. How do I disable the persistent alerting? I want observium only alert me once for an event period.
Thanks a lot.
‹Zhenhui _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
It looks like to be in the alert_table table.
mysql> select * from alert_table where ignore_until_ok!='0’;
I might just directly turn that bit to 1 for all ports currently in down state.
On 10/22/14, 6:49 PM, "Zhenhui Liang" ZhenhuiLiang@eharmony.com wrote:
I found an option to do ignore until ok on the interface settings. But it is really unrealistic to do this manually for hundreds of ports. Any easier way to achieve this? I do want to monitor ports status, but I don¹t want to get a flood of alerts every 24 hours. Thanks a lot.
On 10/22/14, 6:40 PM, "Zhenhui Liang" ZhenhuiLiang@eharmony.com wrote:
Hi,
We have some switches with thousands of ports. I know, we don¹t have administrative down for unused ports. So I set up port down alerts for all ports, so that the initial alert of the down ports, I just ignore so I know those are ports already down. So the theory is that for any following alerts, I will look into them.
But I found out observium will send out the massive port down alerts exactly in 24 hours frequency. How do I disable the persistent alerting? I want observium only alert me once for an event period.
Thanks a lot.
‹Zhenhui _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
This seems like a poor workaround IMO as you will forever be needing to modify SQL tables as ports change state to and from "unused" or you add new devices. Do you not put a suitable description in your unused interfaces that you could use as an additional check in your alert? ie "ifName notmatch AVAILABLE" AND "ifOperStatus eq down".
On Thu, Oct 23, 2014 at 1:13 PM, Zhenhui Liang ZhenhuiLiang@eharmony.com wrote:
It looks like to be in the alert_table table.
mysql> select * from alert_table where ignore_until_ok!='0’;
I might just directly turn that bit to 1 for all ports currently in down state.
On 10/22/14, 6:49 PM, "Zhenhui Liang" ZhenhuiLiang@eharmony.com wrote:
I found an option to do ignore until ok on the interface settings. But it is really unrealistic to do this manually for hundreds of ports. Any easier way to achieve this? I do want to monitor ports status, but I don¹t want to get a flood of alerts every 24 hours. Thanks a lot.
On 10/22/14, 6:40 PM, "Zhenhui Liang" ZhenhuiLiang@eharmony.com wrote:
Hi,
We have some switches with thousands of ports. I know, we don¹t have administrative down for unused ports. So I set up port down alerts for all ports, so that the initial alert of the down ports, I just ignore so I know those are ports already down. So the theory is that for any following alerts, I will look into them.
But I found out observium will send out the massive port down alerts exactly in 24 hours frequency. How do I disable the persistent alerting? I want observium only alert me once for an event period.
Thanks a lot.
‹Zhenhui _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
That is a longer term fix. We already have thousands of ports not having any configure, or retired port which used to be valid yet nobody cared to admin down them.
I agree with you though it is best to be fixed on the configure. But unfortunately, we take over the existing configurations which is already a mess… reality…
From: Ben Steele <ben@bensteele.orgmailto:ben@bensteele.org> Reply-To: Observium Network Observation System <observium@observium.orgmailto:observium@observium.org> Date: Wednesday, October 22, 2014 at 7:53 PM To: Observium Network Observation System <observium@observium.orgmailto:observium@observium.org> Subject: Re: [Observium] alert repeat?
This seems like a poor workaround IMO as you will forever be needing to modify SQL tables as ports change state to and from "unused" or you add new devices. Do you not put a suitable description in your unused interfaces that you could use as an additional check in your alert? ie "ifName notmatch AVAILABLE" AND "ifOperStatus eq down".
On Thu, Oct 23, 2014 at 1:13 PM, Zhenhui Liang <ZhenhuiLiang@eharmony.commailto:ZhenhuiLiang@eharmony.com> wrote: It looks like to be in the alert_table table.
mysql> select * from alert_table where ignore_until_ok!='0’;
I might just directly turn that bit to 1 for all ports currently in down state.
On 10/22/14, 6:49 PM, "Zhenhui Liang" <ZhenhuiLiang@eharmony.commailto:ZhenhuiLiang@eharmony.com> wrote:
I found an option to do ignore until ok on the interface settings. But it is really unrealistic to do this manually for hundreds of ports. Any easier way to achieve this? I do want to monitor ports status, but I don¹t want to get a flood of alerts every 24 hours. Thanks a lot.
On 10/22/14, 6:40 PM, "Zhenhui Liang" <ZhenhuiLiang@eharmony.commailto:ZhenhuiLiang@eharmony.com> wrote:
Hi,
We have some switches with thousands of ports. I know, we don¹t have administrative down for unused ports. So I set up port down alerts for all ports, so that the initial alert of the down ports, I just ignore so I know those are ports already down. So the theory is that for any following alerts, I will look into them.
But I found out observium will send out the massive port down alerts exactly in 24 hours frequency. How do I disable the persistent alerting? I want observium only alert me once for an event period.
Thanks a lot.
‹Zhenhui _______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
If you're team is that lazy - why not just let the alerts fire and set an outlook rule... an outlook rule is one place you can filter what alerts you see... without making anyone do anything over the next 10 years for a "long term" fix.
-----Original Message----- From: observium [mailto:observium-bounces@observium.org] On Behalf Of Zhenhui Liang Sent: Wednesday, October 22, 2014 11:42 PM To: Observium Network Observation System Subject: Re: [Observium] alert repeat?
That is a longer term fix. We already have thousands of ports not having any configure, or retired port which used to be valid yet nobody cared to admin down them.
I agree with you though it is best to be fixed on the configure. But unfortunately, we take over the existing configurations which is already a mess… reality…
From: Ben Steele <ben@bensteele.orgmailto:ben@bensteele.org> Reply-To: Observium Network Observation System <observium@observium.orgmailto:observium@observium.org> Date: Wednesday, October 22, 2014 at 7:53 PM To: Observium Network Observation System <observium@observium.orgmailto:observium@observium.org> Subject: Re: [Observium] alert repeat?
This seems like a poor workaround IMO as you will forever be needing to modify SQL tables as ports change state to and from "unused" or you add new devices. Do you not put a suitable description in your unused interfaces that you could use as an additional check in your alert? ie "ifName notmatch AVAILABLE" AND "ifOperStatus eq down".
On Thu, Oct 23, 2014 at 1:13 PM, Zhenhui Liang <ZhenhuiLiang@eharmony.commailto:ZhenhuiLiang@eharmony.com> wrote: It looks like to be in the alert_table table.
mysql> select * from alert_table where ignore_until_ok!='0’;
I might just directly turn that bit to 1 for all ports currently in down state.
On 10/22/14, 6:49 PM, "Zhenhui Liang" <ZhenhuiLiang@eharmony.commailto:ZhenhuiLiang@eharmony.com> wrote:
I found an option to do ignore until ok on the interface settings. But it is really unrealistic to do this manually for hundreds of ports. Any easier way to achieve this? I do want to monitor ports status, but I don¹t want to get a flood of alerts every 24 hours. Thanks a lot.
On 10/22/14, 6:40 PM, "Zhenhui Liang" <ZhenhuiLiang@eharmony.commailto:ZhenhuiLiang@eharmony.com> wrote:
Hi,
We have some switches with thousands of ports. I know, we don¹t have administrative down for unused ports. So I set up port down alerts for all ports, so that the initial alert of the down ports, I just ignore so I know those are ports already down. So the theory is that for any following alerts, I will look into them.
But I found out observium will send out the massive port down alerts exactly in 24 hours frequency. How do I disable the persistent alerting? I want observium only alert me once for an event period.
Thanks a lot.
‹Zhenhui _______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
don’t get me wrong, they will be changed. But for any “production switch”, you need “change management approval process” to touch. Mean time there are requirement to “set up the alerts now, we can’t afford to miss another down link on the core switch any more!”
On 10/22/14, 8:45 PM, "Joseph L. Brunner" joe@affirmedsystems.com wrote:
If you're team is that lazy - why not just let the alerts fire and set an outlook rule... an outlook rule is one place you can filter what alerts you see... without making anyone do anything over the next 10 years for a "long term" fix.
-----Original Message----- From: observium [mailto:observium-bounces@observium.org] On Behalf Of Zhenhui Liang Sent: Wednesday, October 22, 2014 11:42 PM To: Observium Network Observation System Subject: Re: [Observium] alert repeat?
That is a longer term fix. We already have thousands of ports not having any configure, or retired port which used to be valid yet nobody cared to admin down them.
I agree with you though it is best to be fixed on the configure. But unfortunately, we take over the existing configurations which is already a mess… reality…
From: Ben Steele <ben@bensteele.orgmailto:ben@bensteele.org> Reply-To: Observium Network Observation System <observium@observium.orgmailto:observium@observium.org> Date: Wednesday, October 22, 2014 at 7:53 PM To: Observium Network Observation System <observium@observium.orgmailto:observium@observium.org> Subject: Re: [Observium] alert repeat?
This seems like a poor workaround IMO as you will forever be needing to modify SQL tables as ports change state to and from "unused" or you add new devices. Do you not put a suitable description in your unused interfaces that you could use as an additional check in your alert? ie "ifName notmatch AVAILABLE" AND "ifOperStatus eq down".
On Thu, Oct 23, 2014 at 1:13 PM, Zhenhui Liang <ZhenhuiLiang@eharmony.commailto:ZhenhuiLiang@eharmony.com> wrote: It looks like to be in the alert_table table.
mysql> select * from alert_table where ignore_until_ok!='0’;
I might just directly turn that bit to 1 for all ports currently in down state.
On 10/22/14, 6:49 PM, "Zhenhui Liang" <ZhenhuiLiang@eharmony.commailto:ZhenhuiLiang@eharmony.com> wrote:
I found an option to do ignore until ok on the interface settings. But it is really unrealistic to do this manually for hundreds of ports. Any easier way to achieve this? I do want to monitor ports status, but I don¹t want to get a flood of alerts every 24 hours. Thanks a lot.
On 10/22/14, 6:40 PM, "Zhenhui Liang" <ZhenhuiLiang@eharmony.commailto:ZhenhuiLiang@eharmony.com> wrote:
Hi,
We have some switches with thousands of ports. I know, we don¹t have administrative down for unused ports. So I set up port down alerts for all ports, so that the initial alert of the down ports, I just ignore so I know those are ports already down. So the theory is that for any following alerts, I will look into them.
But I found out observium will send out the massive port down alerts exactly in 24 hours frequency. How do I disable the persistent alerting? I want observium only alert me once for an event period.
Thanks a lot.
‹Zhenhui _______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Hi all,
Adam has swiss cheese memory, there is an alert interval setting:
$config['alerts']['interval'] = 86400; // How frequently to re-send a notification for a continuing alert condition // In seconds. Default is 1 day.
Tom
On 10/23/2014 06:01 AM, Zhenhui Liang wrote:
don’t get me wrong, they will be changed. But for any “production switch”, you need “change management approval process” to touch. Mean time there are requirement to “set up the alerts now, we can’t afford to miss another down link on the core switch any more!”
On 10/22/14, 8:45 PM, "Joseph L. Brunner" joe@affirmedsystems.com wrote:
If you're team is that lazy - why not just let the alerts fire and set an outlook rule... an outlook rule is one place you can filter what alerts you see... without making anyone do anything over the next 10 years for a "long term" fix.
-----Original Message----- From: observium [mailto:observium-bounces@observium.org] On Behalf Of Zhenhui Liang Sent: Wednesday, October 22, 2014 11:42 PM To: Observium Network Observation System Subject: Re: [Observium] alert repeat?
That is a longer term fix. We already have thousands of ports not having any configure, or retired port which used to be valid yet nobody cared to admin down them.
I agree with you though it is best to be fixed on the configure. But unfortunately, we take over the existing configurations which is already a mess… reality…
From: Ben Steele <ben@bensteele.orgmailto:ben@bensteele.org> Reply-To: Observium Network Observation System <observium@observium.orgmailto:observium@observium.org> Date: Wednesday, October 22, 2014 at 7:53 PM To: Observium Network Observation System <observium@observium.orgmailto:observium@observium.org> Subject: Re: [Observium] alert repeat?
This seems like a poor workaround IMO as you will forever be needing to modify SQL tables as ports change state to and from "unused" or you add new devices. Do you not put a suitable description in your unused interfaces that you could use as an additional check in your alert? ie "ifName notmatch AVAILABLE" AND "ifOperStatus eq down".
On Thu, Oct 23, 2014 at 1:13 PM, Zhenhui Liang <ZhenhuiLiang@eharmony.commailto:ZhenhuiLiang@eharmony.com> wrote: It looks like to be in the alert_table table.
mysql> select * from alert_table where ignore_until_ok!='0’;
I might just directly turn that bit to 1 for all ports currently in down state.
On 10/22/14, 6:49 PM, "Zhenhui Liang" <ZhenhuiLiang@eharmony.commailto:ZhenhuiLiang@eharmony.com> wrote:
I found an option to do ignore until ok on the interface settings. But it is really unrealistic to do this manually for hundreds of ports. Any easier way to achieve this? I do want to monitor ports status, but I don¹t want to get a flood of alerts every 24 hours. Thanks a lot.
On 10/22/14, 6:40 PM, "Zhenhui Liang" <ZhenhuiLiang@eharmony.commailto:ZhenhuiLiang@eharmony.com> wrote:
Hi,
We have some switches with thousands of ports. I know, we don¹t have administrative down for unused ports. So I set up port down alerts for all ports, so that the initial alert of the down ports, I just ignore so I know those are ports already down. So the theory is that for any following alerts, I will look into them.
But I found out observium will send out the massive port down alerts exactly in 24 hours frequency. How do I disable the persistent alerting? I want observium only alert me once for an event period.
Thanks a lot.
‹Zhenhui _______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
------ Original Message ------ From: "Tom Laermans" tom.laermans@powersource.cx To: "Observium Network Observation System" observium@observium.org Sent: 10/23/2014 4:04:51 AM Subject: Re: [Observium] alert repeat?
Hi all,
Adam has swiss cheese memory, there is an alert interval setting:
$config['alerts']['interval'] = 86400; // How frequently to re-send a notification for a continuing alert condition // In seconds. Default is 1 day.
Tom
On 10/23/2014 06:01 AM, Zhenhui Liang wrote:
don’t get me wrong, they will be changed. But for any “production switch”, you need “change management approval process” to touch. Mean time there are requirement to “set up the alerts now, we can’t afford to miss another down link on the core switch any more!”
On 10/22/14, 8:45 PM, "Joseph L. Brunner" joe@affirmedsystems.com wrote:
If you're team is that lazy - why not just let the alerts fire and set an outlook rule... an outlook rule is one place you can filter what alerts you see... without making anyone do anything over the next 10 years for a "long term" fix.
-----Original Message----- From: observium [mailto:observium-bounces@observium.org] On Behalf Of Zhenhui Liang Sent: Wednesday, October 22, 2014 11:42 PM To: Observium Network Observation System Subject: Re: [Observium] alert repeat?
That is a longer term fix. We already have thousands of ports not having any configure, or retired port which used to be valid yet nobody cared to admin down them.
I agree with you though it is best to be fixed on the configure. But unfortunately, we take over the existing configurations which is already a mess… reality…
From: Ben Steele <ben@bensteele.orgmailto:ben@bensteele.org> Reply-To: Observium Network Observation System <observium@observium.orgmailto:observium@observium.org> Date: Wednesday, October 22, 2014 at 7:53 PM To: Observium Network Observation System <observium@observium.orgmailto:observium@observium.org> Subject: Re: [Observium] alert repeat?
This seems like a poor workaround IMO as you will forever be needing to modify SQL tables as ports change state to and from "unused" or you add new devices. Do you not put a suitable description in your unused interfaces that you could use as an additional check in your alert? ie "ifName notmatch AVAILABLE" AND "ifOperStatus eq down".
On Thu, Oct 23, 2014 at 1:13 PM, Zhenhui Liang <ZhenhuiLiang@eharmony.commailto:ZhenhuiLiang@eharmony.com> wrote: It looks like to be in the alert_table table.
mysql> select * from alert_table where ignore_until_ok!='0’;
I might just directly turn that bit to 1 for all ports currently in down state.
On 10/22/14, 6:49 PM, "Zhenhui Liang" <ZhenhuiLiang@eharmony.commailto:ZhenhuiLiang@eharmony.com> wrote:
I found an option to do ignore until ok on the interface settings. But it is really unrealistic to do this manually for hundreds of ports. Any easier way to achieve this? I do want to monitor ports status, but I don¹t want to get a flood of alerts every 24 hours. Thanks a lot.
On 10/22/14, 6:40 PM, "Zhenhui Liang" <ZhenhuiLiang@eharmony.commailto:ZhenhuiLiang@eharmony.com> wrote:
Hi,
We have some switches with thousands of ports. I know, we don¹t have administrative down for unused ports. So I set up port down alerts for all ports, so that the initial alert of the down ports, I just ignore so I know those are ports already down. So the theory is that for any following alerts, I will look into them.
But I found out observium will send out the massive port down alerts exactly in 24 hours frequency. How do I disable the persistent alerting? I want observium only alert me once for an event period.
Thanks a lot.
‹Zhenhui _______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
------ Original Message ------ From: "Zhenhui Liang" ZhenhuiLiang@eharmony.com To: "Observium Network Observation System" observium@observium.org Sent: 10/22/2014 11:01:37 PM Subject: Re: [Observium] alert repeat?
don’t get me wrong, they will be changed. But for any “production switch”, you need “change management approval process” to touch. Mean time there are requirement to “set up the alerts now, we can’t afford to miss another down link on the core switch any more!”
Sounds like good justification to short-circuit the change management process.
"sorry, we can't have reliable alerts until all the unused ports are shut down"
adam.
participants (5)
-
Adam Armstrong -
Ben Steele -
Joseph L. Brunner -
Tom Laermans -
Zhenhui Liang