Alerts and integrations
Monitoring only matters when the right people receive useful alerts. LuminaKite centralizes events from every module and routes them through the channels and workflows teams already use.
Operational outcomes
Alerts
- Use one alerting model across TLS, DNS, ASM, uptime, brand and identity modules.
- Deliver alerts by email for all plans and webhooks or chat integrations for paid plans.
- Deduplicate noisy events and escalate important issues to the right channel.
- Keep alert acknowledgement and ownership connected to the underlying evidence.
Core capabilities
How the module works
Create channels
Configure email, webhook or chat channels and verify that they can receive events.
Tune policy
Select event types, quiet hours, deduplication windows and escalation behavior.
Receive module events
Certificate, DNS, ASM, uptime, brand and identity modules produce events with source evidence.
Acknowledge and resolve
Teams use the alert inbox to assign ownership, acknowledge known issues and move work toward closure.
Signals and evidence
Common use cases
Create renewal runbooks
Send certificate expiration alerts to the platform team and webhook the ticketing workflow.
Escalate uptime incidents
Notify the incident channel when monitors go down or cross degradation thresholds.
Connect security operations
Forward high-risk brand, ASM or identity findings to existing security queues.
Frequently asked questions
Are email alerts included in every plan?
Yes. Email alerts are included in all plans, while advanced integrations depend on the active plan.
Can webhooks be used for automation?
Yes. Webhooks are designed for custom workflows such as ticket creation, enrichment or internal notifications.
Can alerts be acknowledged?
Yes. The alert inbox supports acknowledgement and operational review so teams can manage open work.
Do all modules use the same alerting model?
Yes. Module events feed a shared alerting model, which keeps routing and ownership consistent.