---
title: Delete checks
description: Delete checks in the InfluxDB UI.
url: https://docs.influxdata.com/influxdb/v2/monitor-alert/checks/delete/
estimated_tokens: 529
product: InfluxDB OSS v2
version: v2
---

# Delete checks

This page documents an earlier version of InfluxDB OSS. [InfluxDB 3 Core](/influxdb3/core/) is the latest stable version.

#### API token hashing is enabled by default in InfluxDB OSS 2.9.0

Stronger token security: tokens are stored as hashes on disk, so a copy of the database file doesn’t expose usable tokens. Existing tokens are hashed on first startup and the original strings can’t be recovered afterward — **capture any plaintext tokens you still need before you upgrade**.

For more information, see [Token hashing](/influxdb/v2/admin/tokens/#token-hashing).

If you no longer need a check, use the InfluxDB user interface (UI) to delete it.

Deleting a check cannot be undone.

1. In the navigation menu on the left, select **Alerts > Alerts**.
    
    Alerts
    
2. Click the icon, and then click **Confirm**.
    

After a check is deleted, all statuses generated by the check remain in the `_monitoring` bucket until the retention period for the bucket expires.

You can also [disable a check](/influxdb/v2/monitor-alert/checks/update/#enable-or-disable-a-check) without having to delete it.

#### Related

-   [Manage notification rules](/influxdb/v2/monitor-alert/notification-rules/)
-   [Manage notification endpoints](/influxdb/v2/monitor-alert/notification-endpoints/)