Business Objects Server

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
brettmlawrence
Posts: 31
Joined: Tue Oct 27, 2015 11:48 am

Business Objects Server

Post by brettmlawrence »

We are having an issue here with random Business Object reports not running when scheduled and it has been suggested that I look into a way for Nagios to monitor the Windows Process that kicks off on the server when the scheduled reports are run. It is hypothesized by the BO team that when a processes run duration exceeds a certain time the remaining reports do not get kicked off.

Has anyone tried to monitor something like this? Is there an add-on that someone can suggest? Any help would be great.
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: Business Objects Server

Post by rkennedy »

You could monitor the process or service using a particular time period (perhaps an hour after it starts, when it shouldn't be running any further?), and then it will only alert at the time it's assigned. Would that be what you're looking to accomplish?
Former Nagios Employee
brettmlawrence
Posts: 31
Joined: Tue Oct 27, 2015 11:48 am

Re: Business Objects Server

Post by brettmlawrence »

There will be an unknown number of instances of this service running at any point. Is there any way to monitor using a PowerShell script? I have a script that is almost complete that will only return the service if its been running for the predetermined amount of time.
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: Business Objects Server

Post by rkennedy »

Yes, just about anything written in PowerShell can be used as a plugin with the help of NSClient++. See this doc - https://assets.nagios.com/downloads/nag ... ios-XI.pdf

Here's an outline of what will need to be done -
1. Install NSClient++ on the client machine which will run the PS script. Turn on NRPE, and NT protocols, and add the Nagios server under the 'allowed hosts' part.
2. Ensure that the PS script is exiting on a 0, 1, or 2. This is how Nagios will know what the 'status' is. (0 = OK, 1 = WARNING, 2 = CRITICAL)
3. Save it in the C:\Program Files\NSClient++\scripts directory. (could be x86 depending on your architecture)
3. Define a command in nsclient.ini under the [/settings/external scripts/scripts] section, similar to this -

Code: Select all

windows_command=cmd /c echo scripts\\yourscript.ps1 $ARG1$; exit($lastexitcode) | powershell.exe -command -
4. Restart the NSClient++ windows service. (nscp)
5. Set up a check using check_nrpe in Nagios, and call to the defined command above. In the example I used, I would use something like /usr/local/nagios/libexec/check_nrpe -H my.win.client.ip -c windows_command
Former Nagios Employee
Locked