Reference: Azure Visibility and Visibility Management - Adaptive Applications - BlueCat Gateway - 23.3.2

Cloud Discovery & Visibility Administration Guide

Locale
English
Product name
BlueCat Gateway
Version
23.3.2

After you configure the workflow in BlueCat Gateway, you can configure CDV to continuously monitor your Azure environment for changes to virtual networks, virtual machines, load balancers, and private endpoints.

To enable monitoring, you must fill in the Azure Credentials and Monitoring Options sections of the Azure Setup page. When you click Start Discovery, the configured settings are applied and Azure information is captured for the Azure resource groups you specified.

Captured visibility information looks something like this:



Note: Items in the Visibility Status table are Visibility Managers. These are containers that hold all Visibility jobs that were created during a specific Discovery job. For more details, see About Azure Visibility jobs and Visibility managers.

Within the Visibility Management tab, Azure Visibility Managers can have the following statuses:

  • Running: All Visibility jobs in the Visibility Manager are running.

  • Running with issues: At least 1 Visibility job in the Visibility Manager has failed.

  • Stopped: All Visibility jobs in the Visibility Manager are stopped.

  • Failed: All Visibility jobs in the Visibility Manager have failed.

Note:

The following statues are not shown in the Visibility Management table, but can be retrieved when checking the job status from the API:

  • Terminating: While waiting for all the Visibility jobs in the Visibility Manager to be terminated.

  • Updating: While waiting for all Visibility jobs in the Visibility Manager to be updated.

  • Pending: At least 1 Discovery job in the Visibility Manager is pending.

Types of events

When you create, update, or delete any of these resources in Azure, CDV notifies you about the action and indicates that the information is updated in Address Manager. CDV will notify you about the following events:

  • Virtual networks
    • A new virtual network has been created.
    • An existing virtual network has been deleted.
    • An existing virtual network has been updated by adding, updating, or deleting an IP address space.
  • Subnets
    • A new subnet has been created.
    • An existing subnet has been deleted.
  • Virtual machines
    • A new virtual machine has been created.
    • An existing virtual machine has been deleted.
    • A virtual machine has been started.
    • A virtual machine has been powered off.
    • A virtual machine has been deallocated.
    • A virtual machine has been restarted.
  • Load balancers
    • A new load balancer has been created.
    • An existing load balancer has been updated by adding or deleting a Frontend or Backend Pool.
    • An existing load balancer has been deleted.
  • Private DNS Zone
    • A new private zone has been created.
    • An existing private zone has been linked or unlinked to a virtual network.
    • A new resource record has been created within a private zone.
    • An existing resource record has been updated within a private zone.
    • An existing resource record has been deleted within a private zone.
    • An existing private zone has been deleted.
  • DNS Zone
    • A new DNS zone has been created.
    • A new resource record has been created within a DNS zone.
    • An existing resource record has been updated within a DNS zone.
    • An existing resource record has been deleted within a DNS zone.
    • An existing DNS zone has been deleted.
  • Private Endpoint
    • A new private endpoint has been created.
    • An existing private endpoint has been deleted.
  • Kubernetes Cluster
    • Creating a Cluster
    • Deleting a Cluster
    • Starting a Cluster
    • Stopping a Cluster
    • Creating a Node Pool of a Kubernetes Cluster
    • Deleting a Node Pool of a Kubernetes Cluster
    • Scaling a Node Pool of a Kubernetes Cluster