infra/ansible
4
5
Fork 5
Code Issues 6 Pull Requests 3 Activity

Monitoring: Icinga2 #46

New Issue
Open
opened 2021-05-06 22:05:07 +02:00 by moepman · 4 comments
moepman commented 2021-05-06 22:05:07 +02:00
Owner
Copy Link

Monitoring should be implemented using Icinga2.

As central component there should be a server running icinga2 as well as icingaweb2.

Monitoring should be implemented using Icinga2. As central component there should be a server running icinga2 as well as icingaweb2.
moepman added this to the 2021 Q2 milestone 2021-05-06 22:05:07 +02:00
moepman added the
enhancement
 label 2021-05-06 22:05:07 +02:00
moepman commented 2021-05-06 22:06:33 +02:00
Author
Owner
Copy Link

First progress in c93b864f03. Still needs some cleanup and either additional steps within ansible or documentation of further steps (API enable/user, Setup token).

First progress in c93b864f0388984238dd45836571c40e048a7564. Still needs some cleanup and either additional steps within ansible or documentation of further steps (API enable/user, Setup token).
noby commented 2021-05-14 01:01:24 +02:00
Contributor
Copy Link

Do you plan to use icinga-director as well? Or would it be possible to use the icinga agent to monitor e.g. on pizza several metrics with notification mails towards me?

Do you plan to use icinga-director as well? Or would it be possible to use the icinga agent to monitor e.g. on pizza several metrics with notification mails towards me?
moepman commented 2021-05-14 19:01:16 +02:00
Author
Owner
Copy Link

It is not clear yet wether icinga director will be used. I want most services to create their own icinga config snippets using ansible and delegate_to statements.

It is not clear yet wether icinga director will be used. I want most services to create their own icinga config snippets using ansible and delegate_to statements.
moepman modified the milestone from 2021 Q2 to (deleted) 2021-07-27 09:38:01 +02:00
moepman modified the milestone from 2021 Q4 to 2021 Q4 2021-09-29 21:39:14 +02:00
moepman modified the milestone from 2021 Q4 to 2022 Q3 2022-01-19 19:35:15 +01:00
moepman modified the milestone from 2022 Q3 to 2024 Q1 2023-11-14 17:08:02 +01:00
moepman removed this from the 2024 Q1 milestone 2024-04-17 18:08:55 +02:00
moepman commented 2024-10-29 00:29:00 +01:00
Author
Owner
Copy Link

This is mostly implemented as of df069ad - however a satellite is still needed since - at least for the initial setup - the agent needs to be able to connect to the master

This is mostly implemented as of df069ad - however a satellite is still needed since - at least for the initial setup - the agent needs to be able to connect to the master
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
bug

   
duplicate

   
enhancement

   
help wanted

   
invalid

   
question

   
security

   
wontfix
No Label
bug
duplicate
enhancement
help wanted
invalid
question
security
wontfix
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: infra/ansible#46
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?