We have nearly 400+ robots installed with multiple probes .How to export the probes that are installed in each robots..
I will try and offer multiple suggestions since your question isn't really clear.
First, if you just want to see what probes are installed on what robots you can run the following SQL query
select * from cm_nimbus_probe
If you'd like to actually pull the configurations from each robot and store them, you could use controller probe callback text_file_get from LUA or another SDK supported language.
I think there may be a problem with your link URL. Trying to follow it results in an error from the web server.
My fault, that is to a private Community. I will try and provide a public facing post shortly.
Hi Issac, I constantly use the Ctrl+F tool or the Find Tool. Just run a search against "Probes" and you got your full list. When the find is done, select all, r-click then Edit, Copy to clip board and then past into Excel. Remove the columns you don't need then create a nice table. Once you get use to this you can make a perfect table in < 5 minutes.
You can do a find on all Robots, then Probes, etc...
Wrote some LUA to do that :-), even with "fetch" of the running config of every probe, I think I posted it years ago in the old forum :->
Here is a LUA script that uses probe_config_get to store each section->key->value into the NIS or another database, it could easily be modified to copy the entire configuration.
uim/audit.lua at master · BryanKMorrow/uim · GitHub
Thanks All !! I am not familiar with scripts if there is a detailed doc i would be easy to perform .
This is a custom java probe I have written to help alleviate some probe configuration issues. Attached is the probe package itself (just drag to the archive), an information document and a basic .jrxml file that can be imported into Unified Reports. This will be an ongoing development process so please provide your feedback here in this thread with issues and feature requests and I will do my best to address them in future versions.
This probe will archive every probe configuration in your Nimsoft environment on a customizable interval and automatically do configuration differentials between the current and previous configurations. This will allow a Nimsoft administrator to track configuration changes in their environment automatically.
On startup the probe will talk to the data_engine at the path you specified to detect if you have the required database tables and if not it will create them in the Nimsoft database for you. These two tables are PCA_CFG and PCA_CHANGES.
This table contains a record of each probe configuration. It stores the hub, robot, probe, probe version, filesystem path to configuration file, complete configuration file in a column, a record id and archive date.
This table contains a record of each probe configuration change. It stores the hub, robot, probe, configuration section, configuration key, previous and current configuration value, previous and current archive date and previous and current record ids.
HOW IT WORKS
The probe uses the native callbacks provided in many probes to get the probe configurations.
This probe should work with MSSQL, MSSQL with Windows Authentication and MYSQL.
Retrieving data ...