How to edit "service sets" Icinga2 through conf files

SeyoungKim · June 4, 2024, 1:54am

Before you ask a question, you can check the troubleshooting documentation first, maybe you can find an answer here.

Please describe your problem as detailed as possible and don’t forget to use a meaningful title
We also have a markdown formatting guide to help you make your topics more readable!

Give as much information as you can, e.g.

System information:
Platform: Ubuntu
Platform version: 20.04.4 LTS (Focal Fossa)
Kernel: Linux
Kernel version: 5.4.0-177-generic
Architecture: x86_64

Build information:
Compiler: GNU 9.3.0
Build host: runner-hh8q3bz2-project-298-concurrent-0
OpenSSL version: OpenSSL 1.1.1f 31 Mar 2020

I would like to know if there is any way to edit the “service set” using config files. I need to add a thousand services in the services set, if there is a config file related to the “service set” it must be easier for me to complete than clicking all of the services through the web.

Thank you.

rivad · June 4, 2024, 8:02am

Hi Seyoung Kim

“Service set” and “clicking all of the services through the web” sounds like you’re using the director.
In this case you can use the baskets feature of the director.
It uses a JSON file to export and import so you can export the beginning of your work, edit it, and upload the result.

For inspiration, I can recommend a look at the tooling of the Linuxfabrik.

github.com

Linuxfabrik/monitoring-plugins/blob/main/CONTRIBUTING.rst#icinga-director-basket-config

Linuxfabrik's Check Plugin Developer Guidelines
===============================================

Monitoring of an Application
----------------------------

Monitoring an application can be complex and produce a wide variety of data. In order to standardize the handling of threshold values on the command line, to reduce the number of command line parameters and their interdependencies and to enable independent and thus extended designs of the Grafana panels, each topic should be dealt with in a separate check (following the Linux mantra: "one tool, one task").

Avoid an extensive check that covers a wide variety of aspects:

* ``myapp --action threading --warning 1500 --critical 2000``
* ``myapp --action memory-usage --warning 80 --critical 90``
* ``myapp --action deployment-status`` (warning and critical command line options not supported)

Better write three separate checks:

* ``myapp-threading --warning 1500 --critical 2000``
* ``myapp-memory-usage --warning 80 --critical 90``
* ``myapp-deployment-status``

This file has been truncated. show original

lorenz · June 5, 2024, 9:38am

Also, “a thousand” make me a bit suspicious (if the number is not heavily exaggerated). Are the services you want to create really “different” or just targeting different hosts?