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 Email

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

toemail.outEmail
toalerts@acme.com

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 Email

Send a transactional email to one or more recipients, addressable from event fields.

01
set the recipient
Enter a fixed address, or reference an event field like $event.payload.email to route per event.
02
write subject and body
Both accept $event.* templates. The body renders as plain text with an optional summary table of the payload.
03
confirm the sender
Mail goes out from mail@notify.ingestlayer.com with SPF and DKIM aligned. Set a reply-to if you want responses to reach you.

in emaildelivered

From:    mail@notify.ingestlayer.com
To:      alerts@acme.com
Subject: Payment failed — acme-inc (€240.00)

A charge failed for acme-inc.
  amount   €240.00
  reason   insufficient_funds
  attempt  2

notes

Outbound email is metered against a monthly quota that scales with your plan; over-quota sends are deferred, not dropped.
Sending from a fixed ingestlayer domain keeps deliverability high, but the From address is not your own domain.
Recipient addresses pulled from event fields are validated at send time; a malformed address dead-letters that delivery.

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 →