How Active Alerts Work (and How to Check Alert History) on StreamKite

Stream problems are only really a problem if you don’t find out about them. StreamKite’s alert system exists specifically to close that gap — the moment something happens to one of your streams or your plan, it gets logged automatically, with a badge on the dashboard telling you something needs attention. Here’s exactly what triggers an alert, where to see them, and how the history works once you’ve cleared them out.

Where to find alerts

Open the Power panel (the lightning-bolt icon on your dashboard) and go to the Alerts tab. You’ll see two sections: Active Alerts at the top, and Alert History below it.

What actually triggers an alert

Alerts aren’t manually created — they fire automatically based on real changes to your account and streams. Four types exist:

• Stopped (red) — fires when a stream that was previously running stops or crashes unexpectedly. If a slot’s status flips from “running” to anything else, this catches it — including a genuine crash, which gets its own distinct message.
• Expiry (yellow) — fires once your main plan is approaching its renewal date, once you enter the grace period after expiry, and separately for an addon plan nearing its own expiry.
• Limit (purple) — fires when you’ve used every slot available on your current plan, letting you know it might be time to consider an addon.
• Info (blue) — fires for lower-urgency events, like a scheduled stream starting or stopping as expected, or a chain rule successfully handing off from one stream to the next.

Each alert shows an icon matching its type, a short title, a subtitle with more context (like which slot was affected), and a relative timestamp — “2m ago,” “3h ago,” and so on, so you don’t have to do date math to know how recent it was.

Why some alerts only fire once

You won’t get spammed with the same expiry warning every few minutes. Expiry, grace period, addon expiry, and slot limit alerts are all deduplicated — once you’ve been notified about, say, “5 days left on your plan,” that specific alert won’t fire again until the number actually changes to something new, like 4 days left. This keeps the active alerts list meaningful instead of cluttered with repeats of the same warning.

Crash and stop alerts work a little differently — since those reflect a genuine state change each time, a slot that crashes multiple times in a day will generate a fresh alert for each crash.

The alert badge — your at-a-glance signal

You don’t actually need to open the Alerts tab to know something’s waiting for you. Whenever there’s at least one active alert, a small red badge appears on the Power panel’s lightning-bolt icon and on the Alerts tab itself, showing a count (capped at “9+” once you’re past nine). Zero active alerts means the badge simply disappears — a quick visual confirmation that everything’s currently clean.

Clearing active alerts

Active alerts don’t sit there forever cluttering your view — there’s a Clear option that moves everything currently active into your alert history in one action. This doesn’t delete anything; it just shifts those alerts from the “needs attention” list into the historical record, and resets your badge count back to zero.

How Alert History works

Alert History is a running log of everything that’s happened, shown with a slightly muted, faded appearance to visually separate it from your active list. It holds up to 30 entries — combining whatever you’ve cleared from active alerts plus older history — so you can look back and spot patterns, like a specific slot that keeps crashing around the same time every day, or how often you’ve been hitting your slot limit before finally upgrading.

A quick way to use both together

1. Check the badge on the Power icon first — if it’s empty, you likely don’t need to dig further.
2. If it shows a number, open the Alerts tab and read through the active list — this is your “what needs attention right now” view.
3. Handle whatever’s flagged (restart a crashed stream, renew an expiring plan, add slots if you’ve hit your limit).
4. Clear the active list once you’ve dealt with everything, so the next real alert stands out clearly rather than getting lost among old ones.
5. Check Alert History occasionally — not for urgent action, but to notice recurring patterns worth addressing properly.

Frequently asked questions

Do alerts send me a notification outside the dashboard?
The Alerts tab itself is dashboard-only. If you want alerts pushed somewhere external like Discord or Slack, that’s what the separate webhook dispatcher is for — the two systems can run alongside each other.

Can I delete individual alerts instead of clearing everything at once?
Currently, clearing moves your entire active list into history in one action rather than letting you remove alerts one by one.

Do alerts affect my stream in any way?
No — alerts are purely informational. They report on what happened; they don’t change anything about how a stream runs.

What happens once Alert History reaches its 30-entry limit?
Older entries get dropped off as new ones are added, keeping the history at a manageable, recent-focused size rather than growing indefinitely.

The short version

Active Alerts tell you what needs attention right now — a crash, an expiring plan, a maxed-out slot count. Alert History keeps a running record of everything that’s already happened, so you can spot patterns instead of just reacting one incident at a time. Between the badge, the active list, and the history, very little slips by unnoticed.