Delete notification endpoints
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 notifications are no longer sent to an endpoint, complete the steps below to delete the endpoint, and then update notification rules with a new notification endpoint as needed.
Delete a notification endpoint
In the navigation menu on the left, select Alerts > Alerts.
Select Notification Endpoints and find the rule you want to delete.
Click the icon on the notification you want to delete and then click Confirm.
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.