Can staging stay out of the on-call channel?

Filter on env so only production spikes page anyone; staging can route to a quieter place or nowhere.

How is severity decided?

classify weighs the error class and count against your prompt and returns a typed severity the pipeline branches on.

Will one bad minute spam the channel?

You emit one spike event per window, so a burst is summarized as a count rather than streamed error by error.

Monitor error spikes in Discord

Turn a sudden burst of one error into a single, classified alert — production only, severity already decided — instead of a wall of duplicate noise.

01source

sourcesdk.eventTypeScript SDK

matcherror.spike

02pipeline · 2 steps

01CTLfilter.matchenv = prod only
02ENRclassifyseverity → page | notify | ignore

03destinations · 1

todiscordDiscord
channel#ops

the event

You emit error.spike with this shape. The TypeScript SDK keeps the call type-safe, and the event is stored whole — so every field below is available to the pipeline by name.

servicestring
errorstringerror class
countnumberin window
windowstringe.g. 5m
envstringprod | staging

emit it

From your code with the TypeScript SDK — or any language over the REST endpoint and signed webhook ingress.

emit error.spike

import { ingest } from "@ingestlayer/sdk";

await ingest("error.spike", {
  service: "checkout",
  error:   err.name,
  count:   windowCount,
  window:  "5m",
  env:     process.env.NODE_ENV,
});

route it to Discord

Send rich embeds to a channel via a connected bot or a channel webhook.

01
connect the bot
Add the ingestlayer bot to your server, or paste a channel webhook URL. Either credential is held in-region.
02
choose the channel
Select the target channel from the picker. Each connected channel is one reusable destination row.
03
shape the embed
The default embed carries the event name as its title and the payload as name/value fields; override with $event.* references.

in discorddelivered

┌─ #ops ─────────────────────────────────┐
│ ▎ payment.failed                        │
│ ▎ customer   acme-inc                   │
│ ▎ amount     €240.00                    │
│ ▎ reason     insufficient_funds         │
│ ▎ attempt    2                          │
└─────────────────────────────────────────┘

notes

Channel webhooks are limited to about 30 messages per minute; sustained volume should use the bot connection instead.
An embed allows at most 25 fields and 6000 total characters; larger events are summarized.
Mentions (@everyone, @role) are suppressed by default — opt in per pipeline if you actually want a ping.

questions

Can staging stay out of the on-call channel?: Filter on env so only production spikes page anyone; staging can route to a quieter place or nowhere.
How is severity decided?: classify weighs the error class and count against your prompt and returns a typed severity the pipeline branches on.
Will one bad minute spam the channel?: You emit one spike event per window, so a burst is summarized as a count rather than streamed error by error.

build this pipeline or read the quickstart →