Production API

Example: investigate an error increase following a production deployment.

Example data · nothing is connected

This incident shows how a deployment, changed code and error signals appear together. No sample events are written to your database or sent to alert destinations.

Connect your INTYGA workspace →
GitHub · APISentry · API

Needs attention

high new

Errors rose after deploying API v2.8.1

42 errors in the 30 minutes after deployment, against 3 for a comparable baseline window. The matching pull request changed permission checks. Investigate the release and upstream dependencies; this timing is not proof of cause.

Errors after deployment: 42 vs 3 baseline

Observation timeline

Last 7 days · showing 3 of 3 observations. Timing suggests where to investigate; it does not prove a cause.

  1. · sentry.error · Permission check rejected requests
    Sentry · API
  2. · github.deployment · API v2.8.1 · a91c328ef401
    GitHub · API
  3. · github.pull_request.merged · PR #42 · Update permissions · a91c328ef401
    GitHub · API
INTYGA · PROTECTED ACTION

Review and approve

Review the change below. INTYGA checks your passkey and workspace approval rules before Intelligence applies it.

  1. 1 · Review request
  2. 2 · Approve
  3. 3 · Applied
Preparing request

Opening a secure approval…

Requested change