Page 1 of 1

Graph issue ncpa

Posted: Wed Nov 25, 2020 10:21 am
by progressive.nagiosXI
Hi Support Team,

we added server in monitoring via NCPA agent and also change host availability check through 5693.

everything working fine, but the graph for host availability not generate.

CPU/memory/disk graph --> ok

Note:- Device(host/IP) is freshly added not added before.

And this problem is for all host graphs where the host checks via TCP 5693.

Thanks

Re: Graph issue ncpa

Posted: Mon Nov 30, 2020 8:04 am
by progressive.nagiosXI
Hi Nagios Support ,

issue resolved after graph XML delete

Please let us know is there any way to add TCP 5693 directly in the NCPA wizard in place of ping.

ie: host check through TCP 5693 in place of ping/ICMP by default in device addition through the wizard.

Because our Azure Clients ping disabled for server monitoring.only NCPA port 5693 open.

problem steps are for each device
1.add a device through NCPA wizard (by default take hostcheck ping)
2.change host check from ping to tcp5693 (ping is disabled)
3.delete graph XML otherwise it's not created.

Thanks

Re: Graph issue ncpa

Posted: Mon Nov 30, 2020 10:12 am
by dchurch
progressive.nagiosXI wrote:Please let us know is there any way to add TCP 5693 directly in the NCPA wizard in place of ping.
There's the TCP/UDP Port wizard to do just that. It'll send a SYN packet to make sure the port is responding.

You can change an existing host's check command to be "check_xi_service_tcp" with ARG1=-p 5693 and it'll replace the PING-ability check with a SYN response check on that port.

Re: Graph issue ncpa

Posted: Mon Nov 30, 2020 10:55 am
by progressive.nagiosXI
Hi dchurch,

Please understand my query.

here's the TCP/UDP Port wizard to do just that. It'll send an SYN packet to make sure the port is responding. >> this does not cover CPU, Memory via NCPA >> this is extra manual activity after server add

my query is when we add server via Linux/Window NCPA wizard and do apply configuration then the default behavior is host availability checked via ping.

we want to change this default behavior to TCP check, so that host availability checked via TCP without any manual change.

Thanks

Re: Graph issue ncpa

Posted: Mon Nov 30, 2020 2:08 pm
by dchurch
The host check that's ultimately done is determined by a combination of factors:
  • The host check defined directly in the host configuration (see the host page in the CCM).
  • The host template assigned to the host itself.
  • Host templates assigned to the host group the host is in.
#1 is assigned when the configuration wizard finishes. Whatever the configuration wizard puts there will supersede everything unless you clear it out.

#2 comes from the host template the wizard is using. In the NCPA host case, that's xiwizard_ncpa_host, which uses xiwizard_generic_host, where the ping check is coming from. This mostly only provides a fallback for if the host check is empty.

You can affect #3 by changing what host group new hosts are put in (among other things) by adding a Configuration Wizard template and applying it on Step 1 of the wizard. You can generate one by going thru the wizard and opting to save as a template. Configuration Wizard templates hold the config values for steps 3-5 of the wizard.

Recommendation

1. Create a Host Template. Call it TCP/5693 host check. It should be check_tcp with ARG1=5693
2. Modify the xiwizard_ncpa_host host template's "Manage Templates" list to be TCP/5693 host check instead of xiwizard_generic_host.
3. Apply configuration.

This should not only modify the host check for all existing NCPA hosts, but new ones as well.

Another possible route

Another route you can do is to add these NCPA hosts to a host group and apply the host check that way. Unfortunately, I wasn't able to get this working 100% or it would have been my first recommendation.

1. Create a host group. Call it TCP/5693 hosts.
2. Create a Host Template. Call it TCP/5693 host check. When you're creating it, add it to the host group TCP/5693 hosts by clicking "Manage Host Groups" and clicking it over to the right column.
It should be check_tcp with ARG1=5693
3. Apply configuration.
4. Take a host thru the configuration wizard, then on Step 3-5, make sure it gets put in the TCP/5693 hosts Host Group.
5. On the last step, click Save Template. Call it "TCP/5693 Host"

Now, with every host you bring thru the wizard, use the "Finish With Template" button or the gear dropdown near the page title to apply this host group.