Impact on Monitoring

When a monitor is part of an active incident, incident impact can override realtime status shown on the status page.

Status precedence

Kener applies status sources in this order (later overrides earlier):

default status → realtime monitor result → incident impact → maintenance impact

This ensures users see consistent incident/maintenance communication while checks continue in the background.

Incident impact values

Set impact per monitor in an incident:

• DOWN
• DEGRADED

Use DOWN for full outage and DEGRADED for partial impact.

Realtime checks still run

Incident override does not stop monitor execution.

• Monitoring jobs still run on schedule
• Data points are still stored
• Incident impact only affects effective/public status

Event Display Settings

Control incident visibility at:

Manage → Site Configurations → Event Display Settings

These incident settings are used when Kener builds notification/event payloads for users.

Incidents settings

How values are applied

At runtime, Kener checks these flags before querying incidents:

• If disabled, query returns no incidents.
• If enabled, only selected categories (ongoing/resolved) are fetched.
• Resolved incidents are limited by maxCount and daysInPast.

So changing these values directly changes what incident events users receive/see.

Practical guidance

• Keep incident impact aligned with real user impact.
• Update impact as recovery progresses.
• Use Event Display Settings to reduce noisy timelines.

Related guides

• Incidents Overview
• Creating and Managing Incidents