tmcdonald or abrist,
how many nagiosfusion-servers I need to pelace my current solution? Now I have 1 Master-server in Head-office and 4 Slave-servers in regions.
Nagios distributed monitoring
Re: Nagios distributed monitoring
How many total hosts and services do you have across those machines? Really since Fusion is only displaying data and not running checks it should not matter and 1 Fusion machine will suffice, but if you have a crazy amount (like 1 million objects) it might get sluggish.whitest wrote:tmcdonald or abrist,
how many nagiosfusion-servers I need to pelace my current solution? Now I have 1 Master-server in Head-office and 4 Slave-servers in regions.
Former Nagios employee
Re: Nagios distributed monitoring
Luckly there are not crazy amount =)
It wiil be 7-8 regions. 2-3k services on each.
So, I need I Fushion as Central desktop and 7-8 Nagios Cores in regions?
It wiil be 7-8 regions. 2-3k services on each.
So, I need I Fushion as Central desktop and 7-8 Nagios Cores in regions?
Re: Nagios distributed monitoring
But with this setup you would loose the feature of the central configuration.
You have to maintain 7-8 nagios instances + nagiosfusion. Is this the road you want to hit?
You have to maintain 7-8 nagios instances + nagiosfusion. Is this the road you want to hit?
Re: Nagios distributed monitoring
Indeed. Mod_gearman currently is the only solid way to really run real distributed checks with 1 central config management server. Otherwise, you will need to maintain multiple separate configurations. Though, with enough forethought, a tool like puppet/chef and some clever scripting could make the management of multiple configs a breeze.klajosh2 wrote:But with this setup you would loose the feature of the central configuration.
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
Re: Nagios distributed monitoring
My client wanted to have sepatare nagios for each region for active checks, notifies and dashboard (for local stuff). Central Nagios checks services only in head-office and recieves check-results from all region-nagioses. Central Nagios displays all network view for stuff in head-office.klajosh2 wrote:But with this setup you would loose the feature of the central configuration.
You have to maintain 7-8 nagios instances + nagiosfusion. Is this the road you want to hit?
I used scripting with Rsync and Passwordless SSH (in /etc/init.d/nagios) to acheive central configuration. Config files has been organized accordingly.
-
- Skynet Drone
- Posts: 2620
- Joined: Wed Feb 11, 2015 1:56 pm
Re: Nagios distributed monitoring
Going back to the original point of contention - I'd argue that mod_gearman is perfectly stable. We have many clients running gearman workers that are processing as many checks as your entire environment put together. It has proven pretty reliable for us. If you're experiencing mod_gearman crashes I suggest troubleshooting there and resolving that. As abrist said though - Fusion may be an even more appropriate solution for you depending on your use case.
Re: Nagios distributed monitoring
Does mod_gearman support Nagios 4.0 - Nagios 4.1 properly ?jdalrymple wrote:Going back to the original point of contention - I'd argue that mod_gearman is perfectly stable. We have many clients running gearman workers that are processing as many checks as your entire environment put together. It has proven pretty reliable for us. If you're experiencing mod_gearman crashes I suggest troubleshooting there and resolving that. As abrist said though - Fusion may be an even more appropriate solution for you depending on your use case.
I realy many times experienced orhanted checks in mod_gearman =(
-
- Skynet Drone
- Posts: 2620
- Joined: Wed Feb 11, 2015 1:56 pm
Re: Nagios distributed monitoring
Yes - but it's version dependent. Described here.
Re: Nagios distributed monitoring
Maybe this worth another thread: What is the best way to debug mod_gearman? I am asking because when crash comes I am usually not sitting in front of the server checking log files.jdalrymple wrote:Going back to the original point of contention - I'd argue that mod_gearman is perfectly stable. We have many clients running gearman workers that are processing as many checks as your entire environment put together. It has proven pretty reliable for us. If you're experiencing mod_gearman crashes I suggest troubleshooting there and resolving that. As abrist said though - Fusion may be an even more appropriate solution for you depending on your use case.
What I noticed - what is very strange actually - is that I do not see orphaned checks just checks are not executed. only thing helps is to restart main nagios process and gearmand service.
After this checks are starting. I am using nagios core 3.5.1 and gearmand 0.33.
klajosh