Migration from Livestatus to Rest API

Icinga 2
,
1

Currently I’ve Icinga2 2.11.11 and using Livestatus. Planning on migrating to Rest API.

Has anyone out there done such migration and can share the experience especially on large scale Icinga2 implementation? Any gotchas?

Thanks

2

Hi @monigacom,
Well, it depends :slight_smile: What kind of applications (other than IcingaWeb2) are accessing the livestatus-API?

3

We have an inhouse built app and Thurk using Livestatus. We will prefer it rather than migrating to Rest API if it doesn’t get deprecated/removed. These apps are favored by many users and they prefer them.

Thanks

4

Well, livestatus will probably be available for some time, but it is deprecated and will probably not receive that much (if any) attention regarding problems and bugs.
So a migration is inevitable in the long term IMHO.

You would have to adapt your own app to the REST API and probably move away from Thrunk (or convince/pay the Thruk developers to adapt it :slight_smile: )

5

Hello,

Isn’t LiveStatus also used by the NagVis module? If yes, how can we have the NagVis module migrated to the REST API?

Thank you,

Jean

6

Actually Nagvis works with IcingaDB (although the changes are not in a release yet.

1 Like