Wrong Alerts from Alterting function in NLS 1.4.4
Re: Wrong Alerts from Alterting function in NLS 1.4.4
Thanks for the update. Did you also open a ticket or were you going to just test the check attempts option first?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: Wrong Alerts from Alterting function in NLS 1.4.4
Hi,
I will go for the ckeck attempts option first.
As mcapra stated I also assume that the issue is related to a "bug" in NLS (elastissearch or whatever...) and it doesn't seem to be solveable whithin short time. But we use the NLS Alerting for our production systems and it must be reliable. So I will try to fix it with the check attempts as an intermediate solution. For longterm we are working on a more reliable C# service which will be able to receive alarm from our applications and trigger the passive check (to be run with mono directly on Nagios XI).
I will go for the ckeck attempts option first.
As mcapra stated I also assume that the issue is related to a "bug" in NLS (elastissearch or whatever...) and it doesn't seem to be solveable whithin short time. But we use the NLS Alerting for our production systems and it must be reliable. So I will try to fix it with the check attempts as an intermediate solution. For longterm we are working on a more reliable C# service which will be able to receive alarm from our applications and trigger the passive check (to be run with mono directly on Nagios XI).
Re: Wrong Alerts from Alterting function in NLS 1.4.4
Thanks for the update. Please keep us posted.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.