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 Notion

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

tonotion.dbNotion
databaseSignups

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 Notion

Append events as rows to a Notion database, or content to a page. Connect once with OAuth, pick the target per pipeline.

01
connect your workspace
Authorize the ingestlayer Notion integration over OAuth from the destinations page, then choose which databases and pages it may touch. We hold only that workspace's access token, in-region, in the same KMS as your other credentials.
02
pick a target
Per pipeline, choose a database to append a typed row to, or a page to append content to. The picker lists exactly what you shared with the integration during authorization — nothing else.
03
map the columns
For a database, match event fields to Notion properties — automatically by column name, or per-column with $event.* templates. The title column falls back to the event name, so a row is never blank. For a page, the rendered body is appended as blocks.

in notiondelivered

┌─ Signups · database ───────────────────┐
│  Name        ada@acme.com               │
│  Plan        ● pro                       │
│  Source      marketing-site             │
│  Signed up   2026-06-03                  │
└─────────────────────────────────────────┘

notes

Notion grants access page by page: the integration only sees databases and pages you explicitly share during authorization. Add the target there, or the delivery dead-letters as object_not_found.
Each column is coerced to its Notion type — number, date, select, checkbox, URL, and so on. Properties an integration can't write (people, relations, files, formulas, rollups) are skipped rather than guessed.
Title and rich-text values cap at 2000 characters per block and are chunked beyond that; a single page append tops out at 100 blocks.
Tokens don't expire, but revoking the integration inside Notion flips the destination to an error state — reconnect from the destinations page to resume 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 →