Probe Configuration

Overview

The Probes Configuration panel allows you to assign a group of scripts to an asset that can run on a set interval. These scripts will allow for data collection from many types of devices. The protocols can be API, SNMP or custom CLI scripts. SNMP v3 is also supported.

The return data from the Probes can then be injected into the system for correlation or can be stored in the database to allow for analysis on the Dashboard/Reporting server.

For PRI and SIP Trunk probes for Cisco Voice Gateways, reference:

Arbitrator Cisco PRI and SIP Probe Configuration for instructions.

Add a Probe Group

To create a new Probe Group:

1. Click the Probe icon from the Menu bar.

2. Click the “Plus” icon within the Groups pane in the bottom left corner.

3. Enter the “Group” name and press Enter.

4. Click the “Save” icon in the upper right corner.

Clone a Probe Group

To clone an existing Probe Group:

1. Click the Probe icon from the Menu bar.

2. Select a Probe group to clone from.

3. Click the “C” icon within the Groups pane in the bottom left corner.

4. The cloned “Group” name shows: <source group name> clone. Modify this name to the required name.

5. Click the “Save” icon to save the added Probe.

6. The probes contained in this new group can also be modified. Refer to the steps to add, clone and modify probes.

Create a Probe

To create a new Probe:

1. Click the group in which you wish to create a new Probe.

2. Click the Plus icon within the Probes panel.

3. Enter the name and description of the Probe.

4. De-select the check icon from the field titled “Custom”. This field is utilized when putting a custom probe in place versus utilizing the ones within the system.

5. Select the Probe Category from the drop-down list. This will populate the scripts available in that category within the drop-down menu titled “Select Script”.

6. Select a script from the script drop-down list.

7. Enter any additional information required by the selected script, such as the hostname, IP, etc.

8. Click the “Check” icon to close the probe in the far right of the Probe panel.

9. Click the “Save” icon to save the added Probe.

Clone a Probe

Since devices such as CUCM and Unity Connection require dedicated probes, it is useful to clone (create a copy) and modify an existing probe for this purpose.

To clone a probe:

1. Click the probe from which you wish to clone.

   Note

   Insights also provides a list of templates that can be cloned for the specific purpose.

2. Click the Clone probe icon (C) at the bottom of the Probes panel.

3. The clone is created, displaying with naming format, <source probe name> clone. Modify this name to the required name, and update any other required properties.

   Note

   For a CUCM probe, this typically includes Cucm Ip Address.

4. Click the Done icon (blue check mark to the right of the clone’s properties panel).

5. Click Save to add the new probe created from the clone.

Create a Custom Probe

To create a new Probe:

1. Click the group in which you wish to create a new Probe.

2. Click the Plus icon within the Probes panel.

3. Enter the name and description of the Probe.

4. Select and click the check icon from the field titled “Custom”. This field is utilized when putting a custom probe in place versus utilizing the ones within the system.

5. Enter the path and script that you wish to run.

6. Click the “Check” icon to close the probe in the far right of the Probe panel.

7. Click the “Save” icon to save the added Probe.

Delete a Probe Group

To delete a Probe Group:

1. Click the check box next to the group name you wish to delete.

2. Click the Minus icon within the Probe Group panel in the bottom left.

3. Click the “Save” icon to save the changes.

Delete a Probe

To delete a Probe:

1. Click the check box next to the Probe name you wish to delete.

2. Click the Minus icon within the Probe panel in the bottom right.

3. Click the “Save” icon to save the changes.

Export and Import a Profile

Important

This import/export is special. Since we do not have a Profile main screen, the import/export profiles are in Probe Configuration; the same as the legacy push button (right next import/export buttons).

Within the PROBE CONFIGURATION section, you can export and import the profiles that you exported from another system.

A new system log table insights_system_log has also been added to log user actions and a user can create a dashboard to view these actions.

See the:

Log Search

Export a Profile

1. Click the Down arrow button at the bottom of the PROBE CONFIGURATION panel.

   Since this is a probe configuration, we cannot select individual profiles, so it will export all profiles in the system.

2. The Export CSV dialog opens. Enter a CSV file name (You do not have to add the .csv file extension) and click Export.

3. The Export finished dialog shows when the export file has been created. Click Download to save the CSV file to your selected download location.

Import a Profile

1. Click the Up arrow button at the bottom of the PROBE CONFIGURATION panel.

2. A pop-up box will appear asking you choose your file.

3. Click the Choose file button and select the exported CSV file that you have saved to your computer.

4. Click the Import button.

Profile CSV Format

The following columns are in an exported CSV file:

"Row Action","Asset Name","IP Address","Customer Name",
"Site Name","Probe Group Name","Credential 1 Name",
"Credential 2 Name","Frequency (s)",Enable

Note

• The "Row Action" column is used when importing and if it contains “delete”, then the row will be deleted upon import.

• “Probe Group Name” must be unique.

• Combination: “IP Address”,”Customer Name”,”Site Name” must to be unique.

• “Asset Name” is used as a reference of the asset.

• When importing and if an asset and a probe group are found, then a profile will be updated/inserted. If not, nothing to import.

Assign a Probe to an Asset

A probe group assigned to an asset can be modified using a profile CSV file import by specifying the related “Asset Name” and “Probe Group Name” in the CSV file.

For example, consider an asset “Local System” that has 3 profiles:

We can assign probe “Cisco CUCM Version” to asset “Local System” as a CSV file import:

After importing, the profile is added to the probe group.