Delete checks
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.
If you no longer need a check, use the InfluxDB user interface (UI) to delete it.
Deleting a check cannot be undone.
In the navigation menu on the left, select Alerts > Alerts.
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 without having to delete it.
Was this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB OSS v2 and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support.