The following updates were released to the Kentik platform for Alerting during July 2026.
Features
- Jira and Jira Service Management notification channels: Alerts can now create and update tickets in Jira Cloud and JSM. Configure token-based authentication, a project key, and an issue type; custom headers are now entered as structured key-value pairs instead of hand-formatted strings.
- Suppressions table rebuilt: The Suppressions and Silences table now includes a search bar, contained scrolling, multi-row selection for bulk deletion, and an Active/Expired status filter.
- Jump straight to a new suppression: After creating a suppression, the success toast includes a "View Suppression" link that opens the Suppressions and Silences page filtered to the new entry.
- Floating bulk actions: The Alerting, Policies, and Mitigations tables now show a floating action bar when rows are selected, with built-in Remove and Labels actions, matching the Devices page.
- Suppressions can filter on alert context: Suppression rules can now be further limited by materialized context attributes such as device, site, and interface.
- Richer structured context in alert triggers: Triggers now carry structured context (device, site, interface, and geographic details) alongside the legacy context blob, and Synthetics triggers include detailed observation metrics such as latency, jitter, packet loss, HTTP status, DNS codes, throughput, certificates, timeouts, and errors.
- Default top keys evaluated reduced to 1,000: kEvent policies now evaluate 1,000 top keys by default (previously 10,000), improving evaluation performance. Existing policies are migrated automatically.
- Alerting table pagination standardized: The Alerting table now uses the shared paginator component, with disabled next/previous buttons at list boundaries, result counts shown while loading, and configurable per-page counts.
Bug Fixes
- Baseline configuration fields restored: Baseline settings, including minimal length, are visible and editable again on the Baseline tab of alert policies.
- Baseline policy updates for kmetrics: Additional QueryColumn field names are now permitted in the kmetrics SQL generator, so baseline alerting policies can be created and updated again.
- kmetrics filter field names in policies: Dimension and metric mapping now handles both Column and QueryColumn properties, preventing invalid filter field names when configuring kmetrics policies.
- Bulk editing of policy labels: A missing RBAC permission mapping caused permission-denied errors during bulk label edits; this is fixed.
- Mitigations page double-fetch: The Mitigations table no longer fetches its data twice on a fresh page load.
- MKP alert history charts: The missing history endpoint was added, so MKP alert detail pages display their historical chart data.