.. _arbitrator-configuration:
Configuration
=================
.. _SP23|New config screen added to allow customer ndx file retention times. Default is 6 months.:
.. _SP23|New PRI and SIP Trunk probes for Cisco Voice Gateways. Please reference Arbitrator Cisco PRI and SIP Probe Configuration for instructions.:
.. _SP25|Webex API support added (Requires Dashboard SP66 Release for visualization).:
.. _22.1|VOSS-934:
.. _22.1|EKB-12298:
.. _22.2|EKB-13343:
.. _23.1|EKB-13157:
.. _23.1|EKB-15145:
.. _23.1|VOSS-986:
.. _23.1|VOSS-1153:
.. _23.2|EKB-14142:
.. _23.2|EKB-16510:
The menu bar at the top of the screen provides options to navigate to each
of the configuration sections. Each will be covered in its own section of
this guide.
* :ref:`arbitrator-policy-configuration`
* :ref:`arbitrator-asset-configuration`
* :ref:`arbitrator-probe-configuration`
* :ref:`arbitrator-controls`
* :ref:`arbitrator-response-procedure-configuration`
* :ref:`arbitrator-credential-configuration`
* :ref:`arbitrator-customer-configuration`
* :ref:`arbitrator-access-control`
* :ref:`arbitrator-import-export`
* :ref:`arbitrator-archive-management`
* :ref:`arbitrator-log-management`
* :ref:`arbitrator-tools`
|
.. image:: /src/images/assurance-correlation-image7.png
|
.. _arbitrator-policy-configuration:
Policy Configuration
--------------------------
Polices are a modular groupings of correlation rules, actions and response
procedures that define how to respond to certain situations that happen on
the monitored systems. Policies are usually system and manufacturer
specific but can contain custom scripts for actions and response
procedures. Each policy will also contain several correlation rules that
are designed to create Alerts based on the best practices of that
particular system manufacturer. These alerts can apply to:
* Business Processes
* Infrastructure
* Security
* Applications
* Unified Communications
* Network behavior
* Metrics and Threshold Violations
|
.. image:: /src/images/assurance-correlation-image3.png
|
Correlation Rules
.................
A Correlation rule extracts data from the various sources and then defines
the parameters for Alert creation within a Policy. It may contain 1 or
more Correlation Definitions along with specific actions and Response
Procedures. Each correlation rule consists of the following parameters:
.. tabularcolumns:: |p{4.5cm}|p{10.5cm}|
+--------------+------------------------------------------------------------------+
| Parameter | Description |
+==============+==================================================================+
| Name | Descriptive name for the correlation rule which will be |
| | displayed within an Alert and viewed in Alert Analyzer. |
+--------------+------------------------------------------------------------------+
| | Enter a complete description of the problem that created the |
| Description | alert along with any specific remediation steps that should |
| | be taken to resolve the problem. |
+--------------+------------------------------------------------------------------+
| | Simple: Select if the rule is to analyze a single log and as |
| | a result of the rule, you want to execute an action. |
| | |
| | Compound: Select if the rule is to correlate more than one |
| | log, the results of another correlated event or multi-tiered |
| | rules. A compound rule can be one or more simple rules that |
| | feed into one primary rule, or it can come directly from the |
| | source. |
| Type | |
| | Unique: Same as Simple but as a definition will be the only one. |
+--------------+------------------------------------------------------------------+
| Threshold | Selects how many times this rule is to match before an |
| | action occurs. |
+--------------+------------------------------------------------------------------+
| Window | Select the time window for the rule to match before an |
| | action occurs. |
+--------------+------------------------------------------------------------------+
.. tabularcolumns:: |p{4.5cm}|p{10.5cm}|
+-------------------+------------------------------------------------------------------+
| Parameter | Description |
+===================+==================================================================+
| Severity | Indicates what is to appear in the Status field on the Alert |
| | Viewer monitor. |
| | |
| | Select the severity for this rule: |
| | |
| | * Informational |
| | * Minor |
| | * Major |
| | * Critical |
+-------------------+------------------------------------------------------------------+
| Action | Choose the action that is to occur for this rule, based on |
| | the selection in the Severity field |
| | |
| | * Respond - If the condition is met, set a marker and send |
| | an alert. |
| | * Track - If the condition is met, track the event, but do |
| | not post it to the Alert Analyzer. |
| | * Track/Respond - If the condition is met, send an alert |
| | and continue to monitor. |
| | * Respond on Expire – If the condition is met, wait to |
| | send an alert until the window time has expired. If you want |
| | the policy/rule to only alert after an application does not |
| | respond, based on the setting (for example, to ping 9 times |
| | in 10 minutes), choose **Track and Respond**. For the |
| | example in this case, the alert triggers as soon as it sees 9 |
| | ping failures. This setting (Respond on Expire) does not |
| | track. |
| | * Submit - Submit the results of a correlation event back |
| | into the Correlation Engine so that the behavior can be |
| | analyzed and re- correlated. |
| | * Submit/Respond - Submit this alert back into the |
| | Correlation |
| | |
| | Engine so that the event can be analyzed and re-correlated. |
| | Then set a marker and send an alert. |
+-------------------+------------------------------------------------------------------+
| | For any rule that is satisfied, an Incident Response |
| | Procedure occurs and an event is posted to the Alert |
| Response | Analyzer. Select the Response Procedure from the drop-down |
| Procedure | menu to execute when conditions have been met. |
+-------------------+------------------------------------------------------------------+
| Definition Output | Selects a single Correlation Definition's extracted |
| | value to be displayed with the Alert. |
+-------------------+------------------------------------------------------------------+
| Enabled | Toggle to enable/disable the rule |
+-------------------+------------------------------------------------------------------+
| | Toggle to enable/disable whether the rule will include |
| Inherit Output | the results of the filter attached to the policy |
| | module. |
+-------------------+------------------------------------------------------------------+
| | Toggle to halt processing of logs to any other rules |
| | within the policy if the rule matches. This will |
| Halt Processing | highlight the Policy in Green to indicate that this |
| | function is in use. |
+-------------------+------------------------------------------------------------------+
| Correlation | Click the wrench icon where you can define one or more |
| Definitions | definitions match and or extract the required data from |
| | a log or event. See Correlation Definitions. |
+-------------------+------------------------------------------------------------------+
| Output Order | Sets the preferred order to output the extracted data |
| | from the Correlation Definitions. |
+-------------------+------------------------------------------------------------------+
| Done | Click the Done box when the rule is complete |
+-------------------+------------------------------------------------------------------+
| Save | Be sure to click the Save button so your rule (or |
| | changes) are saved and committed. |
+-------------------+------------------------------------------------------------------+
|
.. image:: /src/images/assurance-correlation-image4.png
|
Correlation Filters provide a simple way of ensuring that all of
the correlation rules within the policy are firing on the correct set of
data. The engine first looks at the filter criteria, then it selects only the
data that matches the criteria, and then it applies the correlation
rule. You can add as many of these as required.
Each filter has the following options:
===================== ==========================================================================
Filter Option Description
===================== ==========================================================================
Name Provide a name as close as possible to the data elements you wish to
filter. This allows the output to match the name once viewed in the
alert text.
Pattern The extraction method used to pull a particular data point out. Click
the Wrench icon adjacent to the box to launch the **Regex Wizard**,
which helps you to find and extract the data.
The **Regex Wizard** has two sections:
1. Select a Log: In the top section you can search and select the log
or data set you will be utilizing. That will then show up in the
bottom portion under the phrase "Select log from the list above or
paste log here:". You can copy and paste a log into this section
as well.
2. Create Regex: Once you have your log then go to this section. Here
you can use the wizard to create the Regular Expression required.
Close the wizard and copy this pattern the Regex into the box under
Pattern.
Source Field From the drop-down, choose the source from which data is extracted.
Pattern Type From the drop-down, choose the type of expression you want to use:
* String Match
* Regular Expression Match
* Regular Expression Match/Extract (Most Often Used)
* Regular Expression Multi-Valued Extract
Function If the extracted data is integer-based, you can apply the following
functions for comparing data:
* None
* Greater Than
* Less Than
* Same
Value This field is available only if the data extracted is an integer.
===================== ==========================================================================
|
.. image:: /src/images/assurance-correlation-image1.png
|
.. rubric:: Example: Policies and Alerts
Let's say you have a Ping policy that you've set to alert after 10 failures in 20 minutes.
Depending on how you've set up your rules, the following may occur:
* The policy may run against all your assets and trigger an alarm if the cumulative Ping
failure (across all assets) hits 10
* The policy may trigger an alarm for each asset that fails a ping 10 times in 20 minutes
Thus if it sees 10 failures (across all assets) in 20 minutes, an alert is triggered. However,
if you want 10 failures per asset, you need a definition for the IP address, and
set the filter function to **Same**, which defines that when you see 10 failures for the same IP address,
trigger an alert.
You can configure this definition in two ways:
* As a filter on the policy
* As a specific rule definition.
Correlation Definitions
.......................
A Correlation Definition defines what criteria to match within the data.
Each definition will consist of the following parameters:
.. tabularcolumns:: |p{4.5cm}|p{10.5cm}|
+----------------+-----------------------------------------------------------------+
| Parameter | Description |
+================+=================================================================+
| | Name this as close as possible to the data elements being |
| Name | extracted. That way the output matches the name once viewed |
| | in the alert text. It is also utilized in the key value pair |
| | within the alert text. |
| | |
| | This is the extraction methodology utilized to pull the |
| | particular data point(s) out. Simply find the log containing |
| | the data by utilizing the search bar above. Within that log |
| | you can highlight the text you want to extract. Once |
| | highlighted a box will pop up allowing you to name the field |
| | and extract it. This will automatically create the Regex to |
| | extract the data. The highlight method is about 95% accurate. |
| | |
| | If you have trouble with this method due to special |
| | characters in the data set, then you can utilize the "wrench" |
| | icon beside the Pattern box and it will bring up the "Regex |
| | Wizard" to assist in finding and extracting the data. |
+----------------+-----------------------------------------------------------------+
| Pattern | Within the Regex Wizard there are 2 sections: |
| | |
| | * Select a Log: In the top section you can search and |
| | select the log or data set you will be utilizing. That |
| | will then show up in the bottom portion under the phrase |
| | "Select log from the list above or paste log here:". As |
| | the phrase indicates you can copy and paste a log into |
| | this section as well. |
| | * Create Regex: Once you have your log then go to this |
| | section. Here you can utilize the wizard to create the |
| | Regular Expression required. Close the wizard and copy |
| | this pattern the Regex into the box under Pattern. |
+----------------+-----------------------------------------------------------------+
.. tabularcolumns:: |p{4.5cm}|p{10.5cm}|
+----------------+----------------------------------------------------------------------+
| Parameter | Description |
+================+======================================================================+
| Source Field | In the drop-down box select the source from which the data is |
| | being extracted. |
+----------------+----------------------------------------------------------------------+
| | Select from the drop-down box the type of |
| | expression you want to utilize: |
| | |
| Pattern Type | * String Match |
| | * Regular Expression Match |
| | * Regular Expression Match/Extract (Most Often Used) |
| | * Regular Expression Multi-Valued Extract |
| | |
| | .. note:: |
| | |
| | The "Extract" pattern types above will cause the correlation |
| | engine to include the definition name and the matched value in |
| | the Alert Message. |
| | |
| | |
| | |
| | |
| | |
+----------------+----------------------------------------------------------------------+
| Function | The functions below may be used to change what the correlation |
| | engine counts as a "match" in the log. Alerts are only triggered |
| | if the specific number of matches are found. |
| | |
| | * None - Default. Only use Pattern type matching to trigger a match. |
| | * Greater Than - Should only be applied to integer values. |
| | If the extracted value is greater than the configured value, |
| | then a "match" is made. |
| | * Less Than - should on be applied to integer values. If the |
| | extracted value is less than the configured value, then a |
| | "match" is made. |
| | * Same - Can be applied to both Text or Integer. If the extracted |
| | value is the same as previous occurrences, a match triggered. |
| | For example, if multiple devices are sending an error message, |
| | only the first error will trigger an alert. If the desired goal |
| | is to trigger an alert for unique IP address, then the IP |
| | address definition should have the Same function applied. |
+----------------+----------------------------------------------------------------------+
| Value | This field will only be available if the |
| | Function selected is either "Greater Than" or "Less Than". |
+----------------+----------------------------------------------------------------------+
|
.. image:: /src/images/assurance-correlation-image2.png
|
Creating a Policy
.....................
To Create a Policy:
1. Click the Policy View from the Configuration Menu Bar at the top of the
page.
2. Click the Plus Icon at the bottom left of the Policies panel
3. Fill in the Policy name and press enter.
|
.. image:: /src/images/assurance-correlation-image8.png
|
Creating a Correlation Rule
...............................
To Create a new Correlation Rule:
1. Click the Policy to which you wish to add the rule.
2. Click the Plus icon at the bottom of the Rules panel.
3. Fill in the rule name and the parameters.
|
.. image:: /src/images/assurance-correlation-image33.png
|
Creating a Definition
......................
To create a new definition:
1. Click the wrench icon within any rule to bring up the search engine.
2. Enter a search term that is relevant or is in the log that you would
like to match and press Enter. This will return the last 10 logs with
this term in them.
3. Utilize the highlight and extract procedure or the Regex Wizard as
described in the in "Correlation Definitions" section above.
4. Once finished click Update in the top right of the screen and be sure
to save your Definition on the next page.
|
.. image:: /src/images/assurance-correlation-image34.png
|
Deleting a Correlation Rule
.............................
To delete a Correlation Rule:
1. Click the policy name on the left side of the screen.
2. Click the check box on the Correlation rule you wish to delete.
3. Click the minus icon at the bottom of the correlation panel.
4. Click the Save icon in the upper right to save your change.
|
.. image:: /src/images/assurance-correlation-image31.png
|
Deleting a Policy
....................
To delete a Policy:
1. Click the check box next to the name of the Policy you wish to delete.
2. Click the minus icon in the bottom left of the policy panel.
3. Click the Save icon in the upper right to save your change.
|
.. image:: /src/images/assurance-correlation-image32.png
|
Disabling and Enabling a Policy
.................................
To Disable and Enable a Policy:
1. Select the Policy by clicking the check box next to the name of the
policy.
2. Click the Green Check Box at the bottom of the Policies listing
column.
3. The Name of the Policy will become italicized indicating that the
Policy is Disabled
4. To Enable the Policy: Click the Green Check Box again. The name will
turn back to a normal font indicating it is enabled.
|
.. image:: /src/images/assurance-correlation-image29.png
|
Cloning a Policy
..................
Cloning a Policy allows the quick replication of all of the Correlation
Policy rules and definitions. The user then can simply change only the
required elements for the new policy.
To Clone a Policy:
1. Select the Policy by clicking the check box next to the name of the
policy.
2. Click the Blue "C" Box at the bottom of the Policies listing column.
3. Rename the Policy and make your modifications.
4. Be sure to click Save to save the new policy.
|
.. image:: /src/images/assurance-correlation-image30.png
|
Export and Import a Policy
............................
The Arbitrator platform allows for full export / import of all of its
configuration. Within the Policy Configuration section, you can export and
import the policy 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:
.. raw:: html
Log Search Section
.. raw:: latex
Log Search Section in the Dashboard and Reporting Administration Guide.
|
.. image:: /src/images/insights-import-export-log.png
|
To Export a Policy:
1. Select the check boxes of the policies to export, or select the **Name** check box
at the top of he **Policies** list to select *all* policies.
2. Click the green Down arrow button at the bottom of the **POLICY CONFIGURATION** panel.
3. The **Export CSV** dialog opens. Enter a **CSV file name** (You do
not have to add the ``.csv`` file extension) and click **Export**.
4. The **Export finished** dialog shows when the export file has been created.
Click **Download** to save the CSV file to your selected download location.
To Import a Policy:
1. Click the green Up arrow button at the bottom of the **POLICY 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.
Policy CSV Format
''''''''''''''''''
The following columns are in an exported CSV file:
::
"row action","policy group name",name,description,type,action,severity,
"respond procedure","SubCategory (definition: regular expression match)",
"Message (definition: regular expression match/extract)"
.. note::
* The ``"row action"`` column is used when importing and if it contains "delete",
then the row will be deleted upon import.
* The ``"respond procedure"`` column can be used when importing and should
then contain the Response Procedure name *exactly* as it exists on the system.
If a procedure is found, then it will be assigned to the associated rule.
If a new value is entered, a new Response Procedure is created. The default
Response Procedure is used if no value is entered.
* The combination: "policy group name", "name", "respond procedure" should be unique in
CSV row. If a policy found, its data will be updated. If not found, new policy will
be inserted. The "name" has to be unique. If a rule is found, its data will be updated.
If not found, new rule will be inserted to the policy indicated in "policy group name".
See: :ref:`arbitrator-response-procedure-configuration`.
|
.. image:: /src/images/assurance-correlation-image27.png
|
.. _arbitrator-asset-configuration:
Asset Configuration
--------------------
The Asset Configuration panel allows you to create Assets and Asset
Groupings. Assets can be any devices that are either sending data or from
which data is being retrieved. Each Asset can be assigned to a specific
customer to create a multi-tenant environment.
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:
.. raw:: html
Log Search
.. raw:: latex
Log Search Section in the Dashboard and Reporting Administration Guide.
Creating an Asset Group
........................
To create a new Asset Group:
1. Click the Asset icon from the Menu bar.
2. Click the Plus icon in the bottom left corner of the Asset Groups
panel.
3. Enter the Group name and press Enter.
4. Click the Save icon in the upper right.
|
.. image:: /src/images/assurance-correlation-image28.png
|
Adding an Asset to an Existing Group
......................................
To add a new Asset to a Group:
1. Click Asset Group to which you wish to add an asset.
2. Click the Plus icon at the bottom of the Asset panel.
3. An asset entry box will open up. Fill out all of the details for the
asset under "Properties".
4. Click the "Interface" tab and fill out the details, if applicable.
5. Click the check button to the right of the screen to add the asset.
|
.. image:: /src/images/assurance-correlation-image25.png
|
.. note::
**Modification**: If present, then more than one asset in more than
one group can be modified when *modifying* assets. Change bars are
displayed next to each asset and group when the assets or groups
modified, for example:
|
.. image:: /src/images/insights-arb-assets-conf-change-bar.png
|
Deleting an Asset
...................
To delete an Asset:
1. Click the Asset Group in which your Asset is located.
2. Click the "check" box next to the asset you wish to delete.
3. Click the "minus" icon within the Asset panel.
4. Click the "Save" icon in the upper right corner.
|
.. image:: /src/images/assurance-correlation-image26.png
|
Deleting an Asset Group
..........................
To delete an Asset Group:
1. Click the "check" box next to the Asset Group you wish to delete.
2. Click the "minus" icon in the bottom left of the Asset Group panel.
3. Click the "Save" icon in the upper right corner.
|
.. image:: /src/images/assurance-correlation-image24.png
|
Assigning a Probe to an Asset
...............................
A Probe is a script or set of commands that are saved in the system and
can be utilized to gather data, issue commands to systems, auto repair or
send data. Assigning a probe to an asset is typically done to retrieve
data from that asset. Commands such as an SNMP GET or an API call are
utilized to retrieve data from a particular asset.
To assign a Probe to an Asset:
1. Click the asset group and then click on the actual asset within that
group that the Probe will run against.
2. Click the wrench icon, which will add a monitor profile to the asset.
3. The Probe Group (covered in the next section) screen is opened where
you can select from all of the saved Probes in the system.
4. Select the desired Probe
5. Next click the green pencil icon, which will open up a profile to
define the frequency the probe runs, the credentials needed for the
probe to run, the schedule for the Probe to run and the choice to
start it immediately.
.. note::
For SP25, the frequency for Polycom devices is set at 5 minutes.
6. Once complete click the check button to finalize the probe. This will
take you back to the Asset screen and to the asset you had selected.
|
.. image:: /src/images/assurance-correlation-image21.png
|
.. image:: /src/images/assurance-correlation-image22.png
|
Assigning a Customer to an Asset
.................................
The Correlation Platform has multi-tenancy built in that provides the
ability for different customers to see correlated or collected results of
only their data. Within the configuration of assets, you can assign each
asset to a specific customer. To assign a Customer to an Asset:
1. Click the asset group and then click on the actual asset within that
group that is to be assigned to a Customer.
2. Click the pencil icon that will open up the details of that asset.
3. Click the field labeled Customer and a drop-down list of available
Customers will appear.
4. Select the Customer that the asset belongs to and then click the blue
check box in the top right.
5. Click the Save icon to save the changes.
|
.. image:: /src/images/assurance-correlation-image19.png
|
Placing an Asset in Maintenance Mode
.....................................
The Correlation Platform allows any asset to be placed into Maintenance mode.
Doing so will stop the platform from responding with alerts until it is
removed from the mode. Data will still be collected but alerts will not be
sent.
1. Click the asset group and then click on the actual asset within that group
that is to be put into Maintenance mode.
2. Click the pencil icon that will open up the details of that asset.
3. Check the box next to the label Maintenance Mode and then click the
blue check box in the top right.
4. Click the "plus" icon to return to the Asset Group and then click the
"Save" icon to save the Maintenance Mode settings.
|
.. image:: /src/images/assurance-correlation-image20.png
|
Assets in maintenance mode can be filtered by selecting **Maintenance**
from the **Filter column** drop down list.
|
.. image:: /src/images/insights-arb-maintenance-filter.png
|
Export and Import an Asset
............................
Within the **ASSET CONFIGURATION** section, you can export and
import the asset that you exported from another system.
* When selecting asset groups, all assets belong to those groups will be selected
(selecting individual assets will not take effect).
* If the **Group Name** checkbox is selected, all assets will be included
- both **All groups** and **Ungrouped**.
To Export an Asset:
1. Select the check boxes of the assets to export, or select the **Group name** check box
at the top of he **Groups** list to select *all* assets.
2. Click the green Down arrow button at the bottom of the **ASSET CONFIGURATION** panel.
3. The **Export CSV** dialog opens. Enter a **CSV file name** (You do
not have to add the ``.csv`` file extension) and click **Export**.
4. The **Export finished** dialog shows when the export file has been created.
Click **Download** to save the CSV file to your selected download location.
To Import an Asset:
1. Click the green Up arrow button at the bottom of the **ASSET 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.
Asset CSV Format
''''''''''''''''''
The following columns are in an exported CSV file:
::
"Asset Name",Description,"IP Addres","MAC Address",Vendor,
Model,Version,"Host Name",Alias,"Asset Group Name",
"Type of Device(see below)","Device’s Timezone",Comments,
"Physical Address","Customer Name","Site Name","Row Action"
.. note::
* The ``"Row Action"`` column is used when importing and if it contains "delete",
then the row will be deleted upon import.
* Row uniqueness is the combination of: "IP Address", "Customer Name", "Site Name".
If an asset found, its data will be updated. if not, new asset will be inserted
under the asset group indicated in column "Asset Group Name".
* The column "Asset Group Name" has to be unique. if an asset group is found, its
data will be updated. If not, a new asset group will be inserted.
* There are 2 entries in the import CSV:
* An asset with data in all columns. Most important is the very first column "Asset Name".
* An interface is a property of an asset. An interface only has data in from column "Description" to "Host Name".
Most important is that it does not have data on the very first column "Asset Name".
All CSV interface row(s) will be under an asset just right above it(them).
|
.. image:: /src/images/arbitrator-import-asset.png
|
.. _arbitrator-probe-configuration:
Probe Configuration
---------------------
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:
.. raw:: latex
Arbitrator Cisco PRI and SIP Probe Configuration
.. raw:: html
Arbitrator Cisco PRI and SIP Probe Configuration
for instructions.
Creating 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.
|
.. image:: /src/images/assurance-correlation-image17.png
|
Cloning 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: *