You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If searchlight is able to orchestrate configuration through the Director, then it'd be possible to use it against a central Icinga instance without having to host it inside of Kubernetes.
This would make managing configuration such as notification and accesses much easier if there's an instance of Icinga already running, as there'd only be one system where such changes would have to be applied.
Another example of a module for orchestration configuration is the PuppetDB source.
The text was updated successfully, but these errors were encountered:
Being able to set up Searchlight as a full Icinga satellite would probably also solve the issue, as we already have a large monitoring setup with hardware notification methods attached, and don't want to have cluster monitoring in a separate environment.
Using the director as a check source was mainly though of as a possible way to maybe expedite the implementation of something along those lines.
If searchlight is able to orchestrate configuration through the Director, then it'd be possible to use it against a central Icinga instance without having to host it inside of Kubernetes.
This would make managing configuration such as notification and accesses much easier if there's an instance of Icinga already running, as there'd only be one system where such changes would have to be applied.
Another example of a module for orchestration configuration is the PuppetDB source.
The text was updated successfully, but these errors were encountered: