GCP Monitoring Options - Adaptive Applications - BlueCat Gateway - 23.3.2

Cloud Discovery & Visibility Administration Guide

Locale
English
Product name
BlueCat Gateway
Version
23.3.2

The Monitoring Options section of the Google Cloud Platform (GCP) Setup page lets you configure monitoring settings for importing data into Address Manager. Here, you configure what network data you want made visible for monitoring, and how you want to look for it.

Scheduled Discovery

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

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

You can configure the following options:

Schedule Options

Field/Option Description
Run Once

Cloud Discovery & Visibility runs discovery on GCP 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 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 VPC/Subnet, EC2 Instances, Load Balancers, Route 53, VPC 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 GCP resources based on the configuration settings in the Discovery Options section.

Note: The Visibility functionality imports only incremental VPC/Subnets, VM instance, Load Balancer, VPC network, cloud DNS (private zones), cloud DNS (public zones), private endpoint, and Kubernetes engine changes to Address Manager. Visibility for provided name resolution and public IP ranges is not supported.

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.
Override Queue and Notification Default Names

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:
  • Pub/Sub Topic Name: Enter the name of the Pub/Sub topic that will be used to retrieve data from GCP.

    This name must have 3-255 characters using letters, numbers, dashes ("-"), periods ("."), underscores ("_"), tildes ("~"), percents ("%") or plus symbols ("+"). It must start with a letter and cannot start with "goog".

  • Logging Sink Name: Enter the name of the Logging Sink that will be used to retrieve data from GCP.

    The name must use only upper and lower-case letters, numbers, underscores ("_"), dashes ("-"), and periods (".").

  • Pub/Sub Subscription Name: Enter the name of the Pub/Sub Subscription that will be used to retrieve data from GCP.

    This name must have 3-255 characters using letters, numbers, dashes ("-"), periods ("."), underscores ("_"), tildes ("~"), percents ("%") or plus symbols ("+"). It must start with a letter and cannot start with "goog".

If you enter a name that already exists, 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, when you're sure that your jobs will not impact other Visibility jobs with the same name).

Attention:

When overriding queue and notification names:

  • If you reuse the existing Logging Sink name, any changes in the filter will update it within your GCP environment. If you do not have permissions to update the Logging Sink name, contact your administrator to modify it to the existing Logging Sink name.

  • The filter will update if you modify any Discovery Options within the same Visibility job.

  • If any errors occur due to modifications of the filter, older information will be used and the following error appears in the UI:

    [GCP :: Visibility] : Cannot update filters of types loadbalancer, cloud DNS, kubernetes in the logging sink named test-sink.
  • To avoid conflicts, do not use the same Pub/Sub Topic, Logging Sink, and Pub/Sub Subscription names in multiple Visibility jobs. As a best practice, do not reuse names of existing Pub/Sub Topics, Logging Sinks, and Pub/Sub Subscriptions that you do not own or control.