GCP job settings: Monitoring options - Adaptive Applications - BlueCat Gateway - 25.3

Cloud Discovery & Visibility Administration Guide
ft:locale
en-US
Product name
BlueCat Gateway
Version
25.3

While editing a Google Cloud Platform (GCP) 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 for Discovery, and Real time updates for Visibility.

Scheduled updates (scheduled discovery)

When you use the Scheduled updates monitoring mode, CDV creates a scheduled discovery of GCP resources based on the configuration settings in the Discovery options section. CDV will periodically monitor changes made to GCP resources based on the configured interval.

Scheduled monitoring is available only for VPC/Subnets, VM Instances, Load Balancers, Cloud DNS, Private Service Connect, and Kubernetes Engine.

Attention: When you select the Scheduled updates 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 job settings: Discovery options and GCP job settings: Configuration options.

When using Scheduled updates, you can configure the following options:

Field/Option Description
Run Once (Schedule can't be enabled later)

If ticked, CDV runs discovery on GCP resources a single time, based on the configuration settings in the Discovery Options section.

Effectively, ticking this option disables further monitoring for this job.

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, in seconds, that Cloud Discovery & Visibility waits after the previous discovery job finishes before starting the next discovery job.

Real time updates

When you select Real time updates monitoring mode (also known as Visibility), CDV 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.
Field/Option Description
Override queue and notification default names

If ticked, you can 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.