Collect data from the Icinga 2 API #109
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tbauriedel
force-pushed
the
feature/expand-icinga-collection
branch
from
c079e83 to
bcc1d25
Compare
martialblog
reviewed
Dec 21, 2023
tbauriedel
force-pushed
the
feature/expand-icinga-collection
branch
from
33822d5 to
95bc293
Compare
tbauriedel
force-pushed
the
feature/expand-icinga-collection
branch
from
677c5c1 to
338e245
Compare
martialblog
reviewed
Dec 22, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With that it will be possible to collect 'advanced data' for the module Icinga 2.
As always, we work according to the motto "we take what we get".
The API requests are not only for the local machine. With
--icinga2-api-endpointsyou can define every Icinga 2 endpoint you want to collect data from.For the authentication you will need to deploy a global API user. Easiest way would be to create an user in a global zone like 'director-global' and deploy.
User and password are also provided by arguments. We don't save the credentials. They are only stored inside the runtime variables.
For the moment only data from
/v1/statuswill be collected. However, the code is built in such a way that more can be added as required.