mirror of
https://github.com/hanzoai/kms.git
synced 2026-10-17 11:18:16 +00:00
zeekay
446e5ffd06
Comprehensive rip across the KMS UI + internal docs:
Frontend (47 .tsx + 5 .ts files):
- Infisical → Hanzo KMS
- INFISICAL_* env vars → KMS_*
- infisical-secret placeholder → hanzo-kms-secret
- infisicalSettings → hanzoKmsSettings
- 'infisical__provider-auth-token' → 'hanzo-kms__provider-auth-token'
(SecurityClient localStorage key)
- 'infisical loading indicator' alt text scrubbed
Docs (~10 .mdx files):
- All remaining brand mentions in platform/{pki,dynamic-secrets,pam}
integration guides → Hanzo KMS
- Image asset renamed:
images/platform/pki/sectigo/infisical-create-external-ca-acme.png
→ hanzo-kms-create-external-ca-acme.png
- Two doc references updated to point at the renamed asset
After this commit, the KMS admin UI shows zero upstream brand to
users. Verified by recursive grep: 0 .tsx / .ts / .mdx files contain
'Infisical' / 'INFISICAL' / 'infisical' in user-visible code paths.
Pairs with the prior hanzoai/docs scrub (commit 19c2a800a in
hanzoai/docs) and the recent IAM tenant-neutral rip.
45 lines
2.7 KiB
Plaintext
45 lines
2.7 KiB
Plaintext
---
|
|
title: "Alerting"
|
|
sidebarTitle: "Overview"
|
|
description: "Learn how to set up alerting for expiring certificates with KMS"
|
|
---
|
|
|
|
## Concept
|
|
|
|
In order to ensure that your certificates are always up-to-date and not expired, you can set up alerting in KMS for expiring CA and leaf certificates based on customizable filters.
|
|
|
|
## Guide to Creating an Alert
|
|
|
|
To create an alert, head to your Certificate Management Project > Alerting and press **Create Certificate Alert**.
|
|
|
|
|
|
|
|
|
|
|
|
### Field Descriptions
|
|
|
|
Here's some guidance for each field in the alert configuration sequence:
|
|
|
|
- **Alert Type**: The type of alert to create such as **Certificate Expiration**.
|
|
- **Alert Name**: A slug-friendly name for the alert such as `tls-expiry-alert`.
|
|
- **Description**: An optional description for the alert.
|
|
- **Alert Before**: The time before certificate expiration to trigger the alert such as 30 days denoted by `30d`.
|
|
- **Daily Alerts**: When not enabled, a single notification is sent when the threshold is first reached. Enabling this option sends notifications every day until the certificate expires or is renewed.
|
|
|
|
<Warning>
|
|
For certificates that cannot be renewed through Hanzo KMS, daily alerts will continue to be sent each day until the original expiration date.
|
|
</Warning>
|
|
- **Filters**: A list of filters that determine which certificates the alert applies to. Each row includes a **Field**, **Operator**, and **Value** to match against. For example, you can filter for certificates with a common name containing `example.com` by setting the field to **Common Name**, the operator to **Contains**, and the value to `example.com`.
|
|
|
|
### Notification Channels
|
|
|
|
Alerts can be delivered through one or more notification channels:
|
|
|
|
- **Email**: Send alert notifications to a list of email recipients. Enter one or more email addresses to notify when the alert triggers.
|
|
- **Webhook**: Send alert notifications to a webhook URL. The URL must use HTTPS. Optionally configure a signing secret to verify the authenticity of webhook payloads. See [Webhook Alerts](/documentation/platform/pki/alerting/webhook-alerts) for payload format and signature verification details.
|
|
- **Slack**: Send alert notifications to a Slack channel via an Incoming Webhook. See [Slack Alerts](/documentation/platform/pki/alerting/slack-alerts) for detailed setup steps.
|
|
- **PagerDuty**: Send alert notifications to PagerDuty via the Events API v2. See [PagerDuty Alerts](/documentation/platform/pki/alerting/pagerduty-alerts) for setup instructions.
|
|
|
|
You can configure up to 10 notification channels per alert.
|
|
|
|
 |