---
title: "Drop"
description: "Check what depends on a pattern before dropping it, then generate the drop config."
icon: material/filter-off
---

Silence or sample a noisy pattern without breaking a dashboard or alert. Dependency check first, then config.

!!! tenx-ask "You"

    deps on `Payment_Gateway_Timeout` in Splunk

!!! tenx-answer "Log10x"

    Dependency Check on Splunk (executed). 2 alerts, 1 saved search, 3 dashboards reference the pattern. Top: `Payments_Timeout_Spike` alert · `Payments Service Live` dashboard · `Payment_Gateway_Timeout_24h_summary` saved search. Redirect or remove these consumers before muting.

!!! tenx-ask "You"

    none critical, drop `Payment_Gateway_Timeout` in Datadog

!!! tenx-answer "Log10x"

    Recommended, exact `tenx_hash` (sZw4qq3MCWE):

    ```
    @tenx_hash:"sZw4qq3MCWE"
    ```

    Paste into Logs > Configuration > Indexes > Exclusion Filters.

| You ask | Example answer |
|---|---|
| [deps on `Payment_Gateway_Timeout` in Splunk](dependency-check.md) | Actual list of dashboards / alerts / saved searches referencing the pattern when log analyzer creds are in the env (Splunk, Datadog, CloudWatch, or Kibana for Elasticsearch). Falls back to paste-ready bash when creds are missing. Read-only. |
| [options for `Payment_Gateway_Timeout`](pattern-mitigate.md) | One menu of every viable mitigation (drop / cap / compact), with paths unavailable in your env dimmed. Each option includes a paste-ready config snippet for the chosen vendor. |

## :material-check-decagram-outline: Prerequisites

No prerequisites, both tools work without any Log10x components deployed. To cap volume at the engine level instead of dropping at the vendor, see [Engine PR](../install/configure-engine.md).