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.03k stars 578 forks source link

Deprecate CompatLogger #6032

Closed Crunsher closed 6 years ago

Crunsher commented 6 years ago

I don't see why we still need to carry this old baggage around

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 a dependency for the Livestatus "historical" tables. If you we can drop that too, it should be gone easily. Or we cut-off the straw and provide a lightweight Livestatus only, without any historical table support.

yoshi314 commented 6 years ago

i use it to load data into thruk's mysql cache for availability reporting, since availability reports via livestatus produce invalid data when using thruk + icinga2 (there are bugs for that).

dnsmichi commented 6 years ago

I had a chat at an OSMC hackathon about this, and I truly recommend to use the existing IDO resource, especially when you already have MySQL for such a cache. Parsing logs into a database cache isn't what I would consider reliably working nor what I would want to support.

@Crunsher @gunnarbeutner I'm all for deprecating it. This will raise awareness.

dnsmichi commented 6 years ago 
[2018-05-09 17:36:30 +0200] warning/CompatLogger: The CompatLogger feature is DEPRECATED and will be removed in Icinga v2.10.
Context:
    (0) Activating object 'compatlog' of type 'CompatLogger'
Tontonitch commented 6 years ago

Hello, Just for your information, I still use the compatlog feature. Indeed, due to the lack of a basic availability report feature in icingaweb2, I was requested to put back the icinga classicui, only for those reports. Of course, without compatlog it won't work anymore.

dnsmichi commented 6 years ago

Deprecation means that we won't fix any bugs for these features. Removal is planned but not fixed yet. Still we are currently working on a new backend, reporting and what not - that's where the future is, and if you happen to miss a legacy feature, I'd advise to hold off with upgrading to e.g. 2.11 then.

Tontonitch commented 6 years ago

@dnsmichi I perfectly understand your point of view and that the icinga2 and related projects should move forward. And yes I will certainly stay in 2.10 waiting for some news about a reporting feature.