GCP Visibility Options - Adaptive Applications - BlueCat Gateway - 23.1.1

Cloud Discovery & Visibility Administration Guide
Locale
English
Product name
BlueCat Gateway
Version
23.1.1
The Visibility Options section of the Google Cloud Platform 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.
Attention: The Visibility functionality imports only incremental 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.

Basic Visibility Options

Field/Option Description
Enable Visibility after Discovery Select this checkbox to continuously monitor changes to the discovered resources from the GCP infrastructure.

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

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: Behavior when overriding queue and notification default 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 an existing Pub/Sub Topic, Logging Sink, and Pub/Sub Subscription that you do not own or control.