Apply Config in UI vs. API

[scomdco]

If there is any difference, what is the difference between how an Apply Configuration is applied on the backend when executed through the UI, versus submitted through an API call?

To give more details on what i mean by both scenarios,

UI - by executing an Apply Config through this method,

1.png

API Call - When sending an add or delete host API call by appending the applyconfig=1 parameter at the end

2.png

i feel like when applyconfig=1 is appended to an add/delete API call, i see the result of it through the UI significantly faster than when manually applying the config, but i need to confirm if this is just in my head, or if there really is a difference. Thanks for reading my silly question up to this point.

[jbrunkow]

Definitely not a silly question!

I do not believe that there is any difference between Apply[ing] Configuration in the Nagios XI graphic interface and triggering it through the API; it should be effectively the same.

I suppose that you could stage a test to determine which is faster if you found a way to trigger the Apply Configuration through the graphic interface at exactly the same time, and then monitor the results. Something like the example command below would show you whether the service has been restarted and at what time.

Code: Select all

ps -ef | grep /bin/nagios