---
title: Getting Started with Datadog
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: Docs > Infrastructure > Datadog Resource Catalog
---

# gcp_securitycenter_mute_config{% #gcp_securitycenter_mute_config %}

## `ancestors`{% #ancestors %}

**Type**: `UNORDERED_LIST_STRING`

## `create_time`{% #create_time %}

**Type**: `TIMESTAMP`**Provider name**: `createTime`**Description**: Output only. The time at which the mute config was created. This field is set by the server and will be ignored if provided on config creation.

## `description`{% #description %}

**Type**: `STRING`**Provider name**: `description`**Description**: A description of the mute config.

## `expiry_time`{% #expiry_time %}

**Type**: `TIMESTAMP`**Provider name**: `expiryTime`**Description**: Optional. The expiry of the mute config. Only applicable for dynamic configs. If the expiry is set, when the config expires, it is removed from all findings.

## `filter`{% #filter %}

**Type**: `STRING`**Provider name**: `filter`**Description**: Required. An expression that defines the filter to apply across create/update events of findings. While creating a filter string, be mindful of the scope in which the mute configuration is being created. E.g., If a filter contains project = X but is created under the project = Y scope, it might not match any findings. The following field and operator combinations are supported: * severity: `=`, `:` * category: `=`, `:` * resource.name: `=`, `:` * resource.project_name: `=`, `:` * resource.project_display_name: `=`, `:` * resource.folders.resource_folder: `=`, `:` * resource.parent_name: `=`, `:` * resource.parent_display_name: `=`, `:` * resource.type: `=`, `:` * finding_class: `=`, `:` * indicator.ip_addresses: `=`, `:` * indicator.domains: `=`, `:`

## `gcp_display_name`{% #gcp_display_name %}

**Type**: `STRING`**Provider name**: `displayName`**Description**: The human readable name to be displayed for the mute config.

## `labels`{% #labels %}

**Type**: `UNORDERED_LIST_STRING`

## `most_recent_editor`{% #most_recent_editor %}

**Type**: `STRING`**Provider name**: `mostRecentEditor`**Description**: Output only. Email address of the user who last edited the mute config. This field is set by the server and will be ignored if provided on config creation or update.

## `name`{% #name %}

**Type**: `STRING`**Provider name**: `name`**Description**: This field will be ignored if provided on config creation. Format `organizations/{organization}/muteConfigs/{mute_config}` `folders/{folder}/muteConfigs/{mute_config}` `projects/{project}/muteConfigs/{mute_config}` `organizations/{organization}/locations/global/muteConfigs/{mute_config}` `folders/{folder}/locations/global/muteConfigs/{mute_config}` `projects/{project}/locations/global/muteConfigs/{mute_config}`

## `organization_id`{% #organization_id %}

**Type**: `STRING`

## `parent`{% #parent %}

**Type**: `STRING`

## `project_id`{% #project_id %}

**Type**: `STRING`

## `project_number`{% #project_number %}

**Type**: `STRING`

## `region_id`{% #region_id %}

**Type**: `STRING`

## `resource_name`{% #resource_name %}

**Type**: `STRING`

## `tags`{% #tags %}

**Type**: `UNORDERED_LIST_STRING`

## `type`{% #type %}

**Type**: `STRING`**Provider name**: `type`**Description**: Optional. The type of the mute config, which determines what type of mute state the config affects. The static mute state takes precedence over the dynamic mute state. Immutable after creation. STATIC by default if not set during creation.**Possible values**:

- `MUTE_CONFIG_TYPE_UNSPECIFIED` - Unused.
- `STATIC` - A static mute config, which sets the static mute state of future matching findings to muted. Once the static mute state has been set, finding or config modifications will not affect the state.
- `DYNAMIC` - A dynamic mute config, which is applied to existing and future matching findings, setting their dynamic mute state to 'muted'. If the config is updated or deleted, or a matching finding is updated, such that the finding doesn't match the config, the config will be removed from the finding, and the finding's dynamic mute state may become 'unmuted' (unless other configs still match).

## `update_time`{% #update_time %}

**Type**: `TIMESTAMP`**Provider name**: `updateTime`**Description**: Output only. The most recent time at which the mute config was updated. This field is set by the server and will be ignored if provided on config creation or update.

## `zone_id`{% #zone_id %}

**Type**: `STRING`
