sjain2014 wrote:I have configured get_rdp_info service in one host by CLI in /usr/local/nagios/etc/services (host service file name ws-windows.tel.co.in)
You must add services to Nagios XI through CCM. When you add them via the CLI they are not managed by CCM and will more than likely be deleted by CCM through an Apply Configuration.
Simply copy an existing service in CCM that is similar and then change the check command to check_nrpe and $ARG1$ to get_rdp_info
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
That is not currently an option with Box293's plugin. I think his plugin may just be looking at the counter for active sessions (which does not include the logged in user name). You may wish to ask him for a feature request through email at: [email protected]
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.
abrist wrote:That is not currently an option with Box293's plugin. I think his plugin may just be looking at the counter for active sessions (which does not include the logged in user name). You may wish to ask him for a feature request through email at: [email protected]
Correct.
However, if you have a look in the plugin code, it uses a program called qwinsta to determine # of sessions, which does contain user information. You could modify the plugin so it displays the usernames as part of the output.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Trying to get same configuration to work for me.
Copied php to templates, copied vbs, added lines, followed instructions in general except for trying to use GUI for Service creation (XI)
Check (GUI or CLI) does not produce any results: "No handler for that command" instead.
Please help to get this one working unless there is a better way to check for RDP sessions
dlukinski wrote:Check (GUI or CLI) does not produce any results: "No handler for that command" instead.
This means you don't have your external script properly defined in your nsc.ini/nsclient.ini - post the contents of that file for further troubleshooting. It might also be handy for us to see the output of dir /s "c:\Program Files\NSClient++\*vbs"