While editing Microsoft Azure Discovery or Visibility, Monitoring options let you configure monitoring settings for importing subsequent data into Address Manager. Here, you configure how you want Cloud Discovery & Visibility (CDV) to make changes in network data visible for further monitoring after discovery for that Schedule manager or Visibility manager is finished — essentially, which of Discovery or Visibility you want to use for the specified network infrastructure.
You can choose from two monitoring modes: Scheduled updates and Real time updates (Visibility).
You can choose from two monitoring options:
Scheduled updates: Cloud Discovery & Visibility (CDV) performs discovery and rediscovery jobs on Azure resources at specified times and intervals. Discovery parameters are based on those defined in the Discovery Options section.
Attention: When you select Scheduled Discovery, CDV also selects the Remove Deleted Resources during Rediscovery Discovery option and the Override Configuration Configuration option (which is also disabled to prevent users from clearing it). These selections are made to avoid failures during subsequent scheduled discoveries. For more details on these options, see Azure job settings: Discovery options and Azure job settings: Configuration options.Visibility: Cloud Discovery & Visibility creates visibility jobs and Visibility Managers to continuously monitor changes made to Azure resources, based on the configuration settings in the Discovery Options section.
Tip: A Visibility Manager is a collection of visibility jobs that were created during Discovery when the Azure Monitoring Options are set to Visibility. The jobs that a Visibility Manager contains depend on the subscription and/or resource groups that you specify in the Azure Credentials page. When you perform actions on a Visibility Manager (Start, Stop, and so on), CDV performs those actions on all jobs within that Visibility Manager. For more details, see Visibility tab.When using the Visibility option with Discovery jobs on an entire subscription (or on all subscriptions), CDV will also start new Discovery jobs for any new resource groups it finds.
Scheduled updates (scheduled discovery)
The Schedule Options section appears only if you select Scheduled Discovery as your monitoring option.
When using Scheduled updates, Cloud Discovery & Visibility (CDV) reruns the discovery job on Azure resources at specified times and intervals. Discovery parameters are based on those defined in the Discovery Options section.
| Field/Option | Description |
|---|---|
| Run once (Schedule can be enabled later) |
Cloud Discovery & Visibility runs discovery on Azure resources a single time, based on the configuration settings in the Discovery Options section. Tip: To instead run this discovery configuration multiple
times at regular intervals, simply clear this checkbox and enter the
desired interval in the Interval
field.
|
| Interval | The interval time between discovery jobs, in seconds. The interval indicates the amount of time that Cloud Discovery & Visibility waits after the previous discovery job finishes before starting the next discovery job. |
Real time updates (Visibility)
The Visibility System Locations section appears only if you select Visbility as your monitoring option.
When you use Real time updates (also known as Visibility), CDV creates visibility jobs and Visibility Managers to continuously monitor changes made to Azure resources, based on the configuration settings in the Discovery Options section.
When using the Visibility option with Discoveries on an entire subscription (or on all subscriptions), CDV will also start new Discoveries for any new resource groups it finds.
The method that CDV uses to choose the resource group required to set up CDV's Service Bus and Event Grid resources when running CDV on all resource groups in all subscriptions.
This can be the following:
Default: You specify the resource group individually for each existing subscription. The first valid resource group will be used for new subscriptions that were added since the last discovery or visibility operation.
CDV will list the available subscriptions and let you select the resource group for each one.
Note: CDV will only display available subscriptions if it can connect to the Azure network.Custom: You specify a single resource group to use for all subscriptions. When performing visibility on all subscriptions (or all resource groups for a subscription), CDV will use the specified resource group. If the resource group doesn't exist, CDV will create it if it has permissions (and fail otherwise).
You can select or enter the resource group in the Specify Resource Group field. This field is available only if CDV has access to the Azure system.
Note: This feature requires users to have the following permissions:Microsoft.Resources/subscriptions/resourceGroups/write Microsoft.Resources/subscriptions/resourceGroups/read
Other options
| Field/Option | Description |
|---|---|
| Visibility system locations |
The method that CDV uses to choose the resource group required to set up CDV's Service Bus and Event Grid resources when running CDV on all resource groups in all subscriptions. This can be the following:
Note: If you are configuring a custom resource group for all
subscriptions, make sure that you configure the correct
permissions for your role in the Actions list. For more
information, refer to Custom visibility system location
permissions.
|
Override queue and notification default names Service bus namespace name Service bus queue name Event grid subscription name |
(These fields appear only if a specific resource group is selected in Visibility system location (Specify resource group).) Select the Override queue and notification default names checkbox to specify custom queue and notification names to be created in the cloud where you have specific naming requirements for those resources, instead of using the default generated names. Selecting this checkbox displays the following fields:
If you enter a name that already exists in the resource group, you'll be asked if you want to reuse the same name. Click Cancel (and choose a different name) if you think your Visibility jobs will affect other Visibility jobs using the same name. Click Reuse to confirm use of the same name (that is, if you're sure that your jobs will not impact other Visibility jobs with the same name). Attention:
When overriding queue and notification default names:
|