---
title: "Suppress insights | Grafana Cloud documentation"
description: "Create suppression rules so that insights don't fire"
---

# Suppress insights

Just like [notification rules](/docs/grafana-cloud/knowledge-graph/configure/notifications/create-rules/), you can also select certain insights to suppress so they don’t trigger. Suppressed insights aren’t considered in the knowledge graph processing and won’t be visible in the entity graph or RCA workbench. It’s important to note that this is distinct from an insight that triggers but doesn’t notify.

## Create a Request suppression

To create a Request suppression, complete the following steps:

1. Sign in to Grafana Cloud and navigate to **Observability > Rules > Suppress**.
2. On the **Request** tab, complete the following fields:
   
   Expand table
   
   | Field name      | Description                                                                                                                        |
   |-----------------|------------------------------------------------------------------------------------------------------------------------------------|
   | Job             | Select a job. The list of jobs is generated from your environment.                                                                 |
   | Insight         | Select the insight that you are suppressing.                                                                                       |
   | Request Type    | Optional. The category or type of suppression you are creating. For example: `inbound`, `client_connections`, `logger`, and so on. |
   | Request Context | Optional. Details about the request. For example: the API path, the operation performed, the method called, and so on.             |
   | Other Labels    | Any additional alert labels that you want to match on, for example, `asserts_severity="warning"`.                                  |
   | Rule Name       | Enter a name for the suppression rule.                                                                                             |
3. Click **Add new**.

## Create a Resource suppression

To create a Resource suppression, complete the following steps:

1. Sign into Grafana Cloud and click **Observability > Rules > Suppress**.
2. On the **Resource** tab, complete the following fields:
   
   Expand table
   
   | Field name    | Description                                                                                                                        |
   |---------------|------------------------------------------------------------------------------------------------------------------------------------|
   | Insight       | Select the insight you are suppressing.                                                                                            |
   | Resource Type | Optional. The category or type of suppression you are creating. For example: `inbound`, `client_connections`, `logger`, and so on. |
   | Container     | Optional. The name of the container using the resource.                                                                            |
   | Source        | The source of the metrics for the resource. This could be any exporter or framework serving up resource metrics.                   |
   | Severity      | The severity of the alert, for example `warning` or `critical`.                                                                    |
   | Other Labels  | Any additional alert labels that you want to match on, for example, `asserts_env="prod"`.                                          |
   | Rule Name     | Enter a name for the suppression rule.                                                                                             |
3. Click **Add new**.

## Create a Health suppression

To create a Health suppression, complete the following steps:

1. Sign into Grafana Cloud and click **Observability > Rules > Suppress**.
2. On the **Health** tab, complete the following fields:
   
   Expand table
   
   | Field name   | Description                                                                                       |
   |--------------|---------------------------------------------------------------------------------------------------|
   | Group        | Prometheus rules are organized into rule groups.                                                  |
   | Rules        | Select a rule from the rule group.                                                                |
   | Env          | Select the environment for which this suppression is relevant.                                    |
   | Other Labels | Any additional alert labels that you want to match on, for example, `asserts_severity="warning"`. |
   | Rule Name    | Enter a name for the suppression rule.                                                            |
3. Click **Add new**.

## Manage suppressed assertions using Terraform

You can also manage suppressed assertions configurations using Terraform for infrastructure as code workflows. This enables version control, automated deployments, and consistent suppression rules across environments.

For information about managing suppressed assertions with Terraform, refer to [Configure suppressed assertions using Terraform](/docs/grafana-cloud/as-code/infrastructure-as-code/terraform/terraform-knowledge-graph/suppressed-assertions/).

## Used in these workflows

Suppressing insights is used in:

- [Monitor services](/docs/grafana-cloud/knowledge-graph/use-cases/monitor-services/) - Filter out known issues and expected patterns to focus on critical service health indicators
- [Identify unhealthy infrastructure](/docs/grafana-cloud/knowledge-graph/use-cases/identify-unhealthy-infrastructure/) - Reduce noise from non-critical infrastructure issues to highlight genuine problems