Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Alerting: Linear as a destination type, opening one issue per incident

Aperta
  • Qualcosa non va?
#1,896 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@Makisuo ci sta già lavorando.

Dal 28/10/2026.

  • #1940 di @Makisuo — aperta

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
20/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
backend

Direzione di ricerca

Start in packages/backend/src/services/alerts/AlertDestinationDelivery.ts, especially composeLinkUrl, then trace how existing destination types such as Slack are configured and delivered through the alerts services. Read the webhook delivery/signature path and the integration configuration used to connect Slack. Done means a connectable linear destination can create an issue for a trigger, comment on renotify/resolve, link the incident, and composeLinkUrl yields an incident-specific URL.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Written by an AI agent (Claude) on behalf of @jasonkuhrt.

A team that tracks its work in Linear can't send Maple alerts there. Linear isn't a destination type, so getting an incident into Linear means writing and hosting your own webhook endpoint.

Here's what that takes today. It's the Worker we're about to build for Heartbeat:

// Behind a `webhook` destination. Check x-maple-signature first.
// Linear accepts a caller-chosen UUID on create, so ids derived from
// incidentId and x-maple-delivery-key make Maple's retries harmless.
switch (body.eventType) {
	case "trigger":
		// Linear issueCreate in the team's Triage, id = uuid(incidentId).
	case "renotify":
	case "resolve":
		// Linear commentCreate on issue uuid(incidentId),
		// id = uuid(x-maple-delivery-key).
	case "test":
		// nothing
}

It also needs a Linear API key in the Worker's secrets, so every issue shows the key's owner as its creator, not Maple.

What we'd like to write instead, after connecting Linear once in Maple's integrations the way Slack is connected:

yield* Maple.AlertDestination("linear", {
	type: "linear",
	name: "Engineering triage",
	team_id: "…", // the Linear team whose Triage receives the issues
})

Maple would then open one issue per incident in that team, comment on it at renotify and resolve, link it back to the incident, and show itself as the issue's creator.

Linear's own Sentry integration is the precedent (https://linear.app/docs/sentry). Sentry alert rules can create Linear issues, a Sentry issue can link to a Linear issue, and completing the Linear issue resolves the Sentry one. Maple's error issues could work the same way: create or link a Linear issue from an error issue, and move the error issue to resolved when its Linear issue completes.

One related gap: the webhook reference describes linkUrl as "the incident in the Maple dashboard", but composeLinkUrl in packages/backend/src/services/alerts/AlertDestinationDelivery.ts builds /services/<name>, the same URL for every incident of a service. That's why the Worker above keys on incidentId, and its issue can only link to the service page.

Lingua principale
TypeScript
Stelle
1.8k
Fork
120
Merge medio
8h 11m
PR unite (30g)
667

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di MapleTechLabs/maple

Tutte le issue di MapleTechLabs/maple

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.