Service scaling

Hi all,
I’ll give my best to try and explain what I am trying to achieve.
We have some servers, where not all checks are relevant to us. So we want to “group” or “scale” our services by using host tags, e.g. minimal, standard, extended, custom.
Minimal shall only include a ping check, the checks for CPU load, memory consumption and file system usage
Normal will contain all checks from minimal, plus network bandwidth, disk IO and mount options
Extended will then contain even more
And custom will be for customers wanting to have specific services monitored.

Depending on which host tag is set, the host will receive a certain “monitoring set”.

This is just merely an example, but I guess one might understand what I’m trying to achieve.

Why am I doing this? We are currently monitoring too many services, a lot of them are not relevant to us or our customers. Also: If a customer wants extensive monitoring, they will have to pay more. Additionally a neat side effect: We will reduce stress on our monitoring server.

I think I might only need a nudge in the right direction!

Do you think my plan is realizable?

Cheers

Hi,
you can use the rule “Disabled services” and select the option “Negate”:

Karl

1 Like

Hi @kdeutsch,
seems like valid way to do, but I’m worried about the list of disabled services becoming quite long. Is there no way to prevent the discovery one step earlier?
I already have 35 rows of disabled services, without having implemented your suggestion. I’m worried about the performance impact and also the cluttering of the configuration. Maybe I’m just “over-worrying”?
Cheers

Hi,
a step before that would be to use the “Disabled checks” rule.

Karl

I see, this might be what I’m looking for. Great!
Thank you very much @kdeutsch.

Cheers!

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.