Page 1 of 1
Status.dat
Posted: Tue Mar 21, 2017 10:01 am
by jalzurix
Hi,
I'm searching for status.dat specif information. I'm working with Nagios 4.0.8 and Nagios BPI, and I see that there is more info in status.dat that we see in Nagios BPI.
Could I find information abaout each specific?
The current_event_id identifies each alert and a new one is created each time and alert happens?
Thank you very much,
Re: Status.dat
Posted: Tue Mar 21, 2017 1:02 pm
by mcapra
Here's the full documentation for the NDOUtils database model:
https://assets.nagios.com/downloads/nag ... _Model.pdf
Not every single field present in status.dat is documented in there, but the majority of them are.
The current_event_id identifies each alert and a new one is created each time and alert happens?
That's the gist of it, yeah.
Re: Status.dat
Posted: Wed Mar 22, 2017 2:35 am
by jalzurix
mcapra wrote:Here's the full documentation for the NDOUtils database model:
https://assets.nagios.com/downloads/nag ... _Model.pdf
Not every single field present in status.dat is documented in there, but the majority of them are.
The current_event_id identifies each alert and a new one is created each time and alert happens?
That's the gist of it, yeah.
Thanks mcapra. The fact is that I'm developing some changes for de Nagios BPM and I need to identify each alert. I saw
current_event_id and I was thinking it may be useful for that.
I need to create a register in a third part application and I have to be sure that I create only one for each alert. Do you know how could I identify each alert in Status.dat file?
Re: Status.dat
Posted: Wed Mar 22, 2017 3:35 pm
by dwhitfield
Since you are talking about development, I should warn you that big changes are likely to come to status.dat Nagios Core 5.0. Now, I do not have a timeline for when Core 5.0 will be out, so I don't want to dissuade you too much, but it is something to think about.
As far as getting this done now, I think you'll want to look at the following:
A globally unique number associated with the host's current problem state. Every time a host (or service) transitions from an UP or OK state to a problem state, a global problem ID number is incremented by one (1). This macro will be non-zero if the host is currently a non-UP state. State transitions between non-UP states (e.g. DOWN to UNREACHABLE) do not cause this problem id to increase. If the host is currently in an UP state, this macro will be set to zero (0). Combined with event handlers, this macro could be used to automatically open trouble tickets when hosts first enter a problem state.
more info at:
https://assets.nagios.com/downloads/nag ... olist.html