Neophyte
Ok, so you need it to run on the collector. If you're not running it in the collector debug now, how are you running it? Groovy installed on your laptop? Are there custom libraries you've installed on your laptop that you're importing into the script? If so, you'd need to install those jar files on the collector. Mike_Aracic could probably point you to docs on how to do that.
NeophyteYeah, that's the problem, we added the script using the LM Collector GUI, associated it to that server, the script shows up as valid but not associated to run on any host. We are new to LM and still learning how it works. If we could execute it, the rest I think we can figure out.
I did try to pre-test the script with Groovy on the Collector server, but while LM affirms that it can run Groovy scripts, that executable is not available system wide, not in the user environment. I'm hesitant to add another install of Groovy because I don't want to risk a library clash with LM itself. The sqlnet client and LDAP binaries have all been tested on the server and connect fine to any valid database name.
If we can just get the script to run and raise some errors, we'd have something the move forward with..
If your new datasource isn't applying to any devices, you might consider checking the AppliesTo expression. But have you considered how your instances will get created? Discovery? Batchscript vs. script?
NeophyteIn Nagios this was very simple, when we built new Oracle RAC DBs for the clients, we just added the DB name to the server config in Nagios and called our check-oracle.sh script with it. The script returns 0 or 1 plus the output from the connect attempt. This showed up in Nagios as up / down and if down the message Oracle Sqlnet returned - (commonly No listener found , if the DBA started the DB and forgot to start the listener). Our Oracle LDAP manages the connection string, and the port is open to the Nagios servers. I'd just like to replicate that functionality. Very easy.