// Services

Five surfaces, one console.

segi gives every project the essentials for error visibility. Run it on your own infrastructure or use a managed setup.

/ 01

Error monitoring

What: Browser, Next.js, NestJS, and CDN SDKs
When: Stack-based fingerprinting and issue grouping

FATALPrismaClientKnownRequestErrorv2.4.0

ERRORTypeError: cannot read 'pages'v2.4.1

WARNSlow query > 800ms detectedv2.4.1

DEBUGretry attempt 3/5 for kakao webhookv2.4.1

/ 02

Session recording & heatmap

What: rrweb DOM replay — 30 s FullSnapshots + incremental events, playable from any chunk boundary
When: Click heatmap layered over a live DOM backdrop (not a static grid) so dots align with real buttons

session replay · mocked viewport

▶

00:38 / 01:24

/ 03

Health checks

What: HTTP checks on your chosen interval (15s minimum)
When: Response body matching for expected text

UPapi.extn.ai/health128ms

UPadmin.extn.ai/login78ms

TEXT_MISMATCHwebhook.extn.ai/kakao210ms

UPcdn.extn.ai42ms

DOWNstaging.extn.ai— —

/ 04

PM2 process monitoring

What: Public ingest endpoint authenticated by project key
When: Live process status, CPU, memory, and restart counts

api-serveronline

cpu

22%

mem

48%

workeronline

cpu

mem

32%

schedulerrestart

cpu

56%

mem

64%

/ 05

Notifications

What: Email alerts for newly discovered issues
When: Project-level notification controls

New-issue email

When a brand-new issue first lands, verified org members get an email. Per-project toggles keep noise low.

emailslackwebhookpagerduty

Integration examples

@segi/browser

Segi.init({
  projectKey: "segi_pk_live_xxxxx",
  environment: "production",
  release: "v2.14.3"
});

@segi/nextjs

initSegiNext({
  projectKey: process.env.SEGI_PROJECT_KEY!,
  environment: process.env.NODE_ENV
});

@segi/nestjs

SegiModule.forRoot({
  projectKey: process.env.SEGI_PROJECT_KEY!,
  release: process.env.APP_VERSION
});

pm2 agent

SEGI_PROJECT_KEY=segi_pk_live_xxxxx \
SEGI_ENDPOINT=https://segiapi.extn.ai/api/ingest/pm2 \
node agent.js --loop