How to re-add deleted monitors in Google Cloud monitoring

How to re-add deleted monitors in Google Cloud monitoring

You cannot re-add resources that have been deleted or terminated from the Google Cloud console.
  1. Log in to Site24x7 and go to Cloud > GCP > click the Google Cloud project or Google Cloud monitor > Management Actions.
  2. Scroll down to the Add Deleted Resources for Monitoring section.
  3. You will find the list of deleted monitors. Click +Add next to the deleted resource to add it back for monitoring.

Learn more about out Google Cloud monitoring in this help document.

    • Related Articles

    • How does resource termination settings work for Google Cloud (GCP) monitoring?

      In the Add/Edit Google Cloud (GCP) Monitor page (Site24x7 > Cloud > GCP > Add GCP Monitor), the option Automatically Remove Terminated Resources under Resource Termination Settings lets you remove terminated resources (in Google Cloud Console) from ...

    • How many API calls does Site24x7 GCP monitor make

      Site24x7 Google Cloud monitoring (GCP) fetches the health and performance metrics and your Google Cloud resources' data via APIs. Here is an illustrative calculation on how many API calls will be made by Site24x7 for monitoring your Google Cloud ...

    • How to re-add deleted Azure resource monitors

      You cannot re-add resources that have been deleted from the Azure portal itself. Log in to Site24x7 and go to Cloud > Azure > click on the Azure monitor > Management Actions > Deleted Resources tab. You will find the list of deleted resources. Select ...

    • How to re-add a subscription monitor which was deleted in Site24x7

      When you create an Azure monitor via the Management Group, individual subscription monitors will be created. Each subscription monitor will have its own set of resource monitors. If you delete a subscription monitor, it will be removed from ...

    • How to add a PHP instance that was deleted earlier

      For agent versions 4.0 and above For every instance, there will be a corresponding configuration file present inside the conf folder of the S247DataExporter installation path. Delete the appropriate configuration file and restart the S247DataExporter ...