Page 1 of 1

Newly created services not being impacted by SNMP traps

Posted: Thu Sep 09, 2021 10:53 am
by nevillestyles
Hello,

We have configured the auto-configuration of unconfigured objects so new services are created when we receive SNMP traps from hosts. This is working perfectly.

However we have one issue with this. If we receive a trap from a host which we've not received a trap from before, the service is created but it is not impacted by the trap; the Status remains in a Pending state. If the same trap is subsequently sent from the host, the service is correctly impacted according to the settings in the SNMP Trap Interface.

Is there a way we can config Nagios XI to set the status of the service immediately after creation when the initial trap is received?

Regards,
Neville

Re: Newly created services not being impacted by SNMP traps

Posted: Fri Sep 10, 2021 9:21 am
by pbroste
Hello @nevillestyles

Thanks for reaching out, in Unconfigured Objects we have the option to auto configure and is found:
  • Configure > Unconfigured Objects > [Auto Configure Settings] > Enable Auto Import/Apply Configuration > [Update Settings]
Thanks,
Perry

Re: Newly created services not being impacted by SNMP traps

Posted: Fri Sep 10, 2021 9:31 am
by nevillestyles
Thanks Perry,

We have that setting configured. The auto creation of the hosts/services when an SNMP trap is received is working well.

But we have an issue when a new host sends a trap to XI. Let's say we have an SNMP trap which will set the status of the SNMP Trap service to Critical. If this is sent by a new host, the host and SNMP Trap service are automatically created but the service remains in a Pending state; it's not been impacted by the SNMP trap. If the host sends in a second, identical trap, the SNMP Trap service state changes to Critical as expected.

It feels like, behind the scenes, Nagios XI completes the processing of the SNMP trap before the service is created.

Is there any way we can change our configuration so that following the automatic creation of an SNMP Trap service, the service status is impacted, without waiting for a second trap to come in?

Regards,
Neville

Re: Newly created services not being impacted by SNMP traps

Posted: Mon Sep 13, 2021 1:00 pm
by pbroste
Hello @nevillestyles

Unfortunately, we do not currently have an option for that or a workaround. I went ahead a filed a feature request on your behalf.

Filed under the following subject so you can reference. "SNMPtrap auto-configured from unconfigured objects send alert"

Please keep in mind that the decision to implement the enhancement is at the discretion of our development team.

Thanks,
Perry

Re: Newly created services not being impacted by SNMP traps

Posted: Tue Sep 14, 2021 4:26 am
by nevillestyles
Thank you very much for the confirmation Perry. We’ll keep our fingers crossed for the feature request!

Re: Newly created services not being impacted by SNMP traps

Posted: Tue Sep 14, 2021 1:20 pm
by pbroste
Hello @nevillestyles

I will go ahead and lock this, please refer to Nagios XI Change Log for updates.

Thanks,
Perry