search

Icinga / icinga2

The core of our monitoring platform with a powerful configuration language and REST API.
https://icinga.com/docs/icinga2/latest
GNU General Public License v2.0
2.01k stars 577 forks source link

Deprecate StatusDataWriter #6033

Closed Crunsher closed 6 years ago

Crunsher commented 6 years ago

We don't even support the classic ui anymore

gunnarbeutner commented 6 years ago

I'm all for this. Let's see what @dnsmichi thinks about it.

dnsmichi commented 6 years ago

That's the logical next step after kicking out the Classic UI, 👍 from me.

JeKa0111 commented 5 years ago

With the deprecation of StatusDataWriter, may I ask what will replace status.dat? Currently, I have a script that reads that file to check if there are active downtime. So I was hoping to update my script before we migrate to 2.10.3. Thank you very much!

dgoetz commented 5 years ago

Such a question would be better asked in the community channels because more people will read it there and perhaps have similar scripts. But to answer your question there is a similar file with the icinga2.state (typically in /var/lib/icinga2) which is json(-like). An example how to handle it you can find at https://gist.github.com/lazyfrosch/f05b5cbfe8a05d4a1cee93db2c0028c0 But I would prefer the API or Database instead of any internal file. The API will gives you nice json and filter capabilies, the Database will also change in the future with IcingaDB replacing IDO so I would not base on it for now.

dnsmichi commented 5 years ago

That's an internal core file and not meant for user's access. Use the REST API to fetch runtime data from the core daemon. The state file also is subject to change in the future, with changed update frequency from now 5 minutes.