Product logo
DocsBlogPricing

@turbot/gcp-monitoring

The gcp-monitoring mod contains resource, control and policy definitions for GCP Monitoring service.

Version
5.6.0
Released On
Feb 01, 2024
Depends On

Resource Types

Control Types

Policy Types

Release Notes

5.6.0 (2024-02-01)

What's new?

  • Resource's metadata will now also include createdBy details in Turbot CMDB.
  • We've updated the runtime of the lambda functions to Node 18. You wouldn't notice any difference and things will continue to work smoothly and consistently as before.

5.5.0 (2023-03-23)

What's new?

  • Users can now create their own custom checks against resource attributes in the Approved control using the Approved > Custom policy. These custom checks would be a part of the evaluation of the Approved control. Custom messages can also be added which are then displayed in the control details table. See Custom Checks for more information.

Bug fixes

  • We've updated the runtime of the lambda functions to node 16. You wouldn't notice any difference and things will continue to work smoothly and consistently as before.

Policy Types

  • GCP > Monitoring > Alert Policy > Approved > Custom
  • GCP > Monitoring > Group > Approved > Custom
  • GCP > Monitoring > Notification Channel > Approved > Custom

5.4.0 (2021-12-09)

What's new?

  • We've improved the state reasons and details tables in various Approved and Active controls to be more helpful, especially when a resource is unapproved or inactive. Previously, to understand why one of these controls is in Alarm state, you would need to find and read the control's process logs. This felt like too much work for a simple task, so now these details are visible directly from the control page.

Bug fixes

  • We've made a few improvements in the GraphQL queries for various router actions. You won't notice any difference, but things should run lighter and quicker than before.

5.3.4 (2021-01-20)

Bug fixes

  • Controls run faster now when in the tbd and skipped states thanks to the new Guardrails Precheck feature (not to be confused with TSA PreCheck). With Guardrails Precheck, controls avoid running GraphQL input queries when in tbd and skipped, resulting in faster and lighter control runs.

5.3.3 (2020-12-10)

Bug fixes

  • We've updated the GCP > * > Set API Enabled actions to use the latest API calls when checking the state of the service in the GCP project. There's no noticeable difference, but things should run smoother now.

5.3.2 (2020-11-23)

Bug fixes

  • The GCP > Monitoring > Alert Policy > CMDB control would go into an error state if the alert policy name had non-alphanumeric characters. This issue has now been fixed.

5.3.1 (2020-10-30)

Bug fixes

  • We've updated the Discovery controls for resources to now move to skipped instead of invalid if the service API is disabled in the project and the GCP > {service} > API Enabled policy is checking if the API is disabled. This will reduce the amount of noisy controls that cannot be easily resolved without making changes to the service API.

5.3.0 (2020-09-15)

What's new?

  • We've made improvements to how Active controls interact with CMDB policies and controls for more reliable active checks. Now, if a resource's CMDB policy is set to Skip, its Active control will move to invalid to prevent the Active control from making a decision based on outdated information. Also, Active controls will now wait until the resource's CMDB control has run at least once to ensure the required data is available.

5.2.0 (2020-08-28)

What's new?

  • Discovery controls now have their own control category, CMDB > Discovery, to allow for easier filtering separately from other CMDB controls.

5.1.5 (2020-08-11)

Bug fixes

  • We’ve made improvements to our GraphQL input queries for various controls and actions. You won’t notice any differences, but things should run smoother and quicker than before.

5.1.4 (2020-07-24)

Bug fixes

  • Active controls for all resources were not calling the delete action properly, which meant inactive resources were not being deleted when the policy was set to enforce deletions. This has been fixed and inactive resources will now be cleaned up again.

5.1.3 (2020-06-04)

What's new?

  • All resource Router actions now run even if Guardrails is outside of its allowed change window. This allows Guardrails to maintain an up-to-date CMDB by handling resource updates at all times. Note that this only affects Guardrails' ability to process resources changes that were made in the cloud provider - enforcement actions are still disabled outside of the change window.

5.1.2 (2020-05-13)

Bug fixes

  • Although the data validation errors, which appear in various CMDB and Discovery controls, are not blockers, they look ugly in the UI and should be cleaned up. These errors have now been fixed.

5.1.1 (2020-05-06)

Bug fixes

  • While importing a GCP project, sometimes resources' Discovery controls would get stuck in an Invalid state due to incorrectly configured dependencies. This has been fixed and project imports should be smooth again.

5.1.0 (2020-04-13)

What's new?

  • Services can now be enabled as Metadata only, restricting users to only use metadata level permissions.

Bug fixes

  • Monitoring resources cannot exist if there is no Cloud Monitoring workspace defined in the project. In this case, our Discovery controls for monitoring resources will now return OK (instead of Error).
  • Many calculations for Permissions > Compiled > Service Permissions were in error due to a missing library. This is now fixed.

5.0.0 (2020-04-02)

Resource Types

  • GCP > Monitoring
  • GCP > Monitoring > Alert Policy
  • GCP > Monitoring > Group
  • GCP > Monitoring > Notification Channel

Control Types

  • GCP > Monitoring > API Enabled
  • GCP > Monitoring > Alert Policy > Active
  • GCP > Monitoring > Alert Policy > Approved
  • GCP > Monitoring > Alert Policy > CMDB
  • GCP > Monitoring > Alert Policy > Discovery
  • GCP > Monitoring > Alert Policy > Usage
  • GCP > Monitoring > CMDB
  • GCP > Monitoring > Discovery
  • GCP > Monitoring > Group > Active
  • GCP > Monitoring > Group > Approved
  • GCP > Monitoring > Group > CMDB
  • GCP > Monitoring > Group > Discovery
  • GCP > Monitoring > Group > Usage
  • GCP > Monitoring > Notification Channel > Active
  • GCP > Monitoring > Notification Channel > Approved
  • GCP > Monitoring > Notification Channel > CMDB
  • GCP > Monitoring > Notification Channel > Discovery
  • GCP > Monitoring > Notification Channel > Usage

Policy Types

  • GCP > Monitoring > API Enabled
  • GCP > Monitoring > Alert Policy > Active
  • GCP > Monitoring > Alert Policy > Active > Age
  • GCP > Monitoring > Alert Policy > Active > Last Modified
  • GCP > Monitoring > Alert Policy > Approved
  • GCP > Monitoring > Alert Policy > Approved > Usage
  • GCP > Monitoring > Alert Policy > CMDB
  • GCP > Monitoring > Alert Policy > Usage
  • GCP > Monitoring > Alert Policy > Usage > Limit
  • GCP > Monitoring > CMDB
  • GCP > Monitoring > Enabled
  • GCP > Monitoring > Group > Active
  • GCP > Monitoring > Group > Active > Age
  • GCP > Monitoring > Group > Active > Last Modified
  • GCP > Monitoring > Group > Approved
  • GCP > Monitoring > Group > Approved > Usage
  • GCP > Monitoring > Group > CMDB
  • GCP > Monitoring > Group > Usage
  • GCP > Monitoring > Group > Usage > Limit
  • GCP > Monitoring > Notification Channel > Active
  • GCP > Monitoring > Notification Channel > Active > Age
  • GCP > Monitoring > Notification Channel > Active > Last Modified
  • GCP > Monitoring > Notification Channel > Approved
  • GCP > Monitoring > Notification Channel > Approved > Usage
  • GCP > Monitoring > Notification Channel > CMDB
  • GCP > Monitoring > Notification Channel > Usage
  • GCP > Monitoring > Notification Channel > Usage > Limit
  • GCP > Monitoring > Permissions
  • GCP > Monitoring > Permissions > Levels
  • GCP > Monitoring > Permissions > Levels > Modifiers
  • GCP > Turbot > Event Handlers > Logging > Sink > Compiled Filter > @turbot/gcp-monitoring
  • GCP > Turbot > Permissions > Compiled > Levels > @turbot/gcp-monitoring
  • GCP > Turbot > Permissions > Compiled > Service Permissions > @turbot/gcp-monitoring

Action Types

  • GCP > Monitoring > Alert Policy > Delete
  • GCP > Monitoring > Alert Policy > Router
  • GCP > Monitoring > Group > Delete
  • GCP > Monitoring > Group > Router
  • GCP > Monitoring > Notification Channel > Delete
  • GCP > Monitoring > Notification Channel > Router
  • GCP > Monitoring > Set API Enabled