Kener Docs
llms.txt
Search Documentation
Search through all documentation pages
Core Concepts

Alerting Overview

How alerts are evaluated, triggered, and delivered in Kener

Kener alerting turns monitor signals into notifications through configured triggers.

Flow

Monitor result -> Alert configuration evaluation -> Alert event -> Trigger delivery

Alert types

  • STATUS: evaluates monitor status (DOWN or DEGRADED targets)
  • LATENCY: evaluates latency threshold in milliseconds
  • UPTIME: evaluates uptime percentage threshold

Trigger lifecycle

Each alert event is sent as:

  • TRIGGERED when failure threshold is reached
  • RESOLVED when success threshold is reached

If incident creation is enabled on the configuration, Kener can also create/update incidents from alert events.

Supported trigger providers

Current runtime supports:

  • webhook
  • discord
  • slack
  • email

Template variable model

Trigger templates render with alert and site variables (for example {{alert_name}}, {{alert_status}}, {{site_name}}, {{site_url}}).

Use Templates for the canonical variable list.

Secret interpolation

Secrets are interpolated from environment variables using $VAR_NAME syntax (not {{env.VAR_NAME}}).

Example:

Authorization: Bearer $API_TOKEN

Next steps