Best practice recommendation on Service reuse
Posted: Tue Feb 07, 2017 1:54 pm
I have about 300 servers and Nagios Core 4.2.4
At one point I did have a small number of services, and utilized groups. The problem I ran in to is that a vast majority of these servers desire different thresholds. So having say 90% use of "/app" for Warning and 95% for Critical, doesnt apply to all servers. It became easier for me to just have a unique service for each "/app" check (I use ncpa) for each host, each stored in their own separate hostname.cfg file. I know this is large and cumbersome, but otherwise, individual tweaking of a specific host was a hassle.
Can you please provide some SME best practice recommendation? Am I doing this wrong? Making life harder on myself? Is there a way to define one service for "/app" monitoring for example, but yet specify unique thresholds for each host?
At one point I did have a small number of services, and utilized groups. The problem I ran in to is that a vast majority of these servers desire different thresholds. So having say 90% use of "/app" for Warning and 95% for Critical, doesnt apply to all servers. It became easier for me to just have a unique service for each "/app" check (I use ncpa) for each host, each stored in their own separate hostname.cfg file. I know this is large and cumbersome, but otherwise, individual tweaking of a specific host was a hassle.
Can you please provide some SME best practice recommendation? Am I doing this wrong? Making life harder on myself? Is there a way to define one service for "/app" monitoring for example, but yet specify unique thresholds for each host?