Skip to content

AWS Backup

Collect asset and monitoring data for AWS Backup backup vaults.

Configuration

Install Func

We recommend enabling Hosted Func under Guance Integrations - Extensions. All prerequisites are installed automatically; continue with script installation.

For a self-hosted Func deployment, see Self-host Func.

Activate Script

Note: Prepare an AWS AK that meets the requirements. For simplicity, you can grant the global read-only permission ReadOnlyAccess directly.

Activate the script in Hosted Func

  1. Log in to the Guance console
  2. Click the 【Integration】 menu and select 【Cloud Account Management】
  3. Click 【Add Cloud Account】, select 【AWS】, and fill in the required information on the interface. If you have already configured the cloud account information before, ignore this step
  4. Click 【Test】, and if the test is successful, click 【Save】. If the test fails, please check if the relevant configuration information is correct and test again
  5. Click 【Cloud Account Management】, and you can see the added cloud account in the list. Click the corresponding cloud account to enter the details page
  6. Click [Integrations] on the cloud account details page. Find AWS Backup in the Not installed list and click [Install] to open the installation dialog and complete the installation.

Activate the script manually

  1. Sign in to the Func console, click [Script Market], open the Guance script market, and search for integration_aws_backup.
  2. Click 【Install】 and enter AWS AK ID, AK Secret, and the account name.
  3. Click [Deploy Startup Script]. The system automatically creates the Startup script set and configures the corresponding startup script. In the startup script, remove the fixed dimensions and statistics settings from cloudwatch_configs so that dimensions are discovered from actual metrics and default statistics are used. Replace targets with the following and save:

    'targets': [
        {
            'namespace': 'AWS/Backup',
            'metrics': [
                'NumberOfBackupJobsCompleted',
                'NumberOfBackupJobsCreated',
                'NumberOfRecoveryPointsCompleted',
                'NumberOfRecoveryPointsDeleting',
                'NumberOfBackupJobsRunning',
                'NumberOfBackupJobsFailed',
                'NumberOfRecoveryPointsCold',
                'NumberOfCopyJobsCompleted',
                'NumberOfCopyJobsCreated',
                'NumberOfCopyJobsRunning',
            ],
        },
    ],
    
    4. after enabling it, open"Management / Automatic Trigger Configuration"to view the automatic trigger configuration.Click[Run],to run it immediately,without waiting for the scheduled interval.wait a moment,you can view execution records and related logs

Verification

  1. In"Management / Automatic Trigger Configuration"confirm that the automatic trigger configuration exists for the task,and review task records and logs for exceptions
  2. In Guance, check [Infrastructure / Custom] for asset information.
  3. InGuance,"Metrics"verify that the corresponding monitoring data

Metrics

After configuring AWS cloud monitoring, the default metrics are listed below. You can configure additional metrics for collection.AWS Backup Metric details

AWS Backup metrics are in the aws_backup measurement.

AWS Backup updates metrics every 5 minutes and publishes them under nonzero conditions; missing data points do not mean zero. backup_vault_name and resource_type appear according to the actual dimension combination. For copy jobs, backup_vault_name identifies the destination backup vault.

MetricName MetricDescribe Dimensions Unit
number_of_backup_jobs_completed_sum Number of completed backup jobs backup_vault_name, resource_type, region_id count
number_of_backup_jobs_created_sum Number of created backup jobs backup_vault_name, resource_type, region_id count
number_of_recovery_points_completed_sum Number of completed recovery points backup_vault_name, resource_type, region_id count
number_of_recovery_points_deleting_sum Number of recovery points being deleted backup_vault_name, resource_type, region_id count
number_of_backup_jobs_running_sum Number of running backup jobs backup_vault_name, resource_type, region_id count
number_of_backup_jobs_failed_sum Number of failed backup jobs backup_vault_name, resource_type, region_id count
number_of_recovery_points_cold_sum Number of recovery points moved to cold storage backup_vault_name, resource_type, region_id count
number_of_copy_jobs_completed_sum Number of completed cross-account and cross-region copy jobs backup_vault_name, resource_type, region_id count
number_of_copy_jobs_created_sum Number of created cross-account and cross-region copy jobs backup_vault_name, resource_type, region_id count
number_of_copy_jobs_running_sum Number of running cross-account and cross-region copy jobs backup_vault_name, resource_type, region_id count

Feedback

Is this page helpful?