Azure Monitoring Options - Adaptive Applications - BlueCat Gateway - 23.1.1

Cloud Discovery & Visibility Administration Guide
Locale
English
Product name
BlueCat Gateway
Version
23.1.1
The Monitoring Options section lets you configure monitoring settings for importing data into Address Manager.
Attention: Azure Visibility functionality imports only incremental virtual networks, virtual machine, load balancer, DNS zone, and private endpoint changes to Address Manager.

Discovery only

When you select the Discovery only radio button, Cloud Discovery & Visibility only performs a one-time discovery of Azure resources based on the configuration settings in the Discovery Options section.

Schedule

When you select the Schedule radio button, Cloud Discovery & Visibility creates a scheduled discovery of Azure resources based on the configuration settings in the Discovery Options section. Cloud Discovery & Visibility will periodically monitor changes made to Azure resources based on the configured interval.

Attention: When you select the Schedule radio button, the Remove Deleted Resources (Tag Deleted Views/Zones) during Rediscovery Discovery option is automatically checked and Override Configuration Configuration option is automatically checked and greyed out to avoid failures for subsequent scheduled discovery jobs. For more information, refer to Azure Discovery Options and Azure Configuration Options.

You can configure the following options:

Schedule Options

Field/Option Description
Interval Enter the interval time between discovery jobs. The interval indicates the amount of time, in seconds, that Cloud Discovery & Visibility waits after the previous discovery job finishes before starting the next discovery job.
Note: The scheduled discovery task only supports the discovery of Virtual Networks, Virtual Machines, Load Balancers, DNS Zones, Private Endpoints, and Kubernetes Services.

Address Manager User options

Field/Option Description

Address Manager Username

Address Manager Password
The Address Manager Username field is populated with the current user that is logged into Gateway. If required, you can update the username to another Address Manager user.
Note: This user should be an Address Manager administrative API user with full permissions.
In the Address Manager Password field, enter the password for the Address Manager user.

Visibility

When you select the Visibility radio button, Cloud Discovery & Visibility creates a visibility task to retrieve Azure resources based on the configuration settings in the Discovery Options section.

You can configure the following options:

Address Manager User options

Field/Option Description

Address Manager Username

Address Manager Password
The Address Manager Username field is populated with the current user that is logged into Gateway. If required, you can update the username to another Address Manager user.
Note: This user should be an Address Manager administrative API user with full permissions.
In the Address Manager Password field, enter the password for the Address Manager user.

Other options

Field/Option Description

Override Queue and Notification Default Names

Service Bus Namespace Name

Service Bus Queue Name

Event Grid Subscription Name

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:
  • Service Bus Namespace Name: Enter the name of the Service Bus Namespace that will be used to retrieve data from Azure.

    This name must have 6-50 characters using letters, numbers, and hyphens ("-"). It must start with a letter and end with a letter or number. It must not end with "-sb" or "-mgmt" and cannot contain consecutive hyphens.

  • Service Bus Queue Name: Enter the name of the Service Bus Queue that will be used to retrieve data from Azure.

    It can have up to 260 characters using letters, numbers, periods ("."), hyphens ("-"), and underscores ("_"). It must start and end with a letter or number.

  • Event Grid Subscription Name: Enter the name of the Event Grid Subscription that will be used to retrieve data from Azure.

    This name must have 3-64 characters using letters, numbers, and hyphens ("-").

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 default names for queues and notifications, CDV will resolve changes and name collisions as follows:
  • If you reuse an existing Event Grid Subscription name, any changes in the filter will update it within your Azure environment. If you do not have permissions to update the Event Grid Subscription name, contact your administrator to modify it to the existing Event Grid Subscription name.
  • The filter will update if you modify any Discovery Options within the same Visibility job.
  • If errors occur due to modifications of the filter, older information will be used and the following errors appear in the UI: 
    [AZURE :: Visibility] : Cannot update filters of types virtual machine, private endpoint in the event subscription named test-sub. 
    [AZURE :: Visibility] : Cannot remove filters of types loadbalancer, kubernetes in the event subscription named test-sub
  • To avoid conflicts, do not use the same Service Queue and Event Grid Subscription names in multiple Visibility jobs. In general, do not reuse names of Service Bus Namespaces, Service Bus Queues, or Event Grid Subscriptions that you do not own or control.