---
title: "August 2026 - Alerting"
slug: "august-2026-alerting-1"
updated: 2026-09-09T21:13:46Z
published: 2026-09-09T21:13:46Z
canonical: "kb.kentik.com/august-2026-alerting-1"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.kentik.com/llms.txt
> Use this file to discover all available pages before exploring further.

# August 2026 - Alerting

The following updates were released to the Kentik platform for Alerting during August 2026.

## Features
- **Alert chart resolution and Edit Policy shortcut**: Alert charts now select an appropriate resolution automatically, and an "Edit Policy" link was added to the alert sidebar for faster access to policy settings. 
- **Agent health policy warnings**: Kentik now displays a banner when your organization has synthetic or universal agents but no alert policy covering agent health or agent capability health.
- **ServiceNow integration for Australia**: An Australia-specific version of the ServiceNow integration package is now available, along with troubleshooting guidance for missing flow conditions and fields after import. 
- **Clearer integration setup guidance**: Documentation for the Jira alert-deduplication webhook now shows a concrete authorization header example, and the ServiceNow integration docs explain that all actions run under a single configured Kentik credential, recommending a dedicated least-privilege account. 

## Bug Fixes
- **Disabling toggle-mode policies**: Toggle-mode alerting policies now correctly clear activation and clearance delays when disabled, which previously could resurrect stale rule delays. 
- **Alerting page filter crashes**: Fixed crashes on the Alerting page caused by non-array values passed to the application and severity filters. 
- **Policy condition crash**: Editing an NMS alert policy condition no longer crashes when the selected metric is null. 
- **Juniper BGP session alerts**: BGP session-state alerts on Juniper devices now trigger reliably when a session flaps; unstable peer indexing previously prevented them from firing. Existing alerts clear and re-key on deploy.