Skip to content
AutoObserve
Design Partner

CHANGE EVIDENCE

GitHub Correlate deployments with production behaviour.

Commits, pull requests and deployment events explain what changed before latency spiked. AutoObserve connects GitHub change evidence to the production timeline — not as a CI dashboard, but as investigation context.

Evidence
Commits · PRs · Deployments
Source
GitHub webhooks
Enables
Change-aware RCA
Status
GA
See the evidence received ↓View architecture →

Read integration docs →

GitHub

  1. Change events

  2. AutoObserve

  3. Deployment correlation

  4. Investigation

WHY THIS INTEGRATION MATTERS

Production failures often follow production changes.

When checkout-api degrades, the first question is what deployed. GitHub change evidence answers that inside the same investigation window as metrics and logs.

  • Deployment correlation

    Align commit SHA and deployment timestamps with latency evidence.

  • Change timeline

    See PR merges and releases on the same axis as production signals.

  • Change ownership

    Connect regressions to the change set that introduced them.

  • Change-aware RCA

    Reduce time spent asking whether a deploy caused the spike.

EVIDENCE RECEIVED

Commits, pull requests and deployment events

GitHub delivers change evidence — when code moved, who merged it, and when it reached production.

  • Commits
  • Pull requests
  • Deployments

  1. Capture

    Ingest merge, release and deployment events from GitHub.

  2. Align

    Place change events on the production evidence timeline.

  3. Correlate

    Match deploy SHA to service version during degradation.

  4. Investigate

    Start RCA with change context — not a separate CI tool.

HOW AUTOOBSERVE USES THIS EVIDENCE

Change events become causal hypotheses.

GitHub does not replace telemetry. It explains what changed while telemetry explains what broke.

Provides

  1. Commits
  2. Pull requests
  3. Deployments

AutoObserve creates

  1. Change timeline
  2. Deployment correlation
  3. Release attribution
  4. Change-aware RCA

GitHub is what changed. AutoObserve is why it mattered.

CONNECT YOUR CHANGE PIPELINE

Ingest GitHub change evidence alongside production telemetry.

Webhooks, Actions and deployment integrations feed the same evidence model — without duplicating your CI/CD platform.

Push and deployment webhooks stream change events to AutoObserve.

  1. GitHub repository

  2. Change webhooks

  3. AutoObserve

QUICK START

Connect GitHub change evidence

Configure webhooks or Actions to send deployment events, then verify change correlation on a known service.

  1. Configure webhooks

    Point repository webhooks at AutoObserve for push, release and deployment events.

    Integrations reference →

  2. Map services to repos

    Associate checkout-api with its GitHub repository and deployment environment.

    Architecture overview →

  3. Verify deployment correlation

    Deploy a test change and confirm the commit appears on the production timeline.

    Troubleshooting guide →

WHAT SUCCESS LOOKS LIKE

Changes visible on the production timeline.

Success means deployment events align with service versions during incidents — not merely that webhooks arrive.

  • Deployment events ingested

    Merge and release events appear within minutes of production deploy.

  • Commit SHA resolved

    checkout-api version matches GitHub commit on the timeline.

  • Timeline alignment

    Change events sit in the same window as latency evidence.

  • Change attribution active

    Investigation surfaces likely deploy correlation automatically.

REAL INCIDENT

Same checkout spike — deployment commit in focus.

The canonical checkout-api degradation with the deployment event highlighted — which version shipped before latency rose.

  1. Metric

    14:31:00

    Checkout latency +184%

Walk through the evidence chain · 1/6

Evidence step 1 of 6

TROUBLESHOOTING

Common GitHub change evidence failures

  • Problem

    Deployment events not appearing

    Likely cause

    Webhook not configured for deployment_status or workflow events.

    Resolution

    Enable deployment and workflow webhook events for the production repository.

    Verify

    Test deploy creates a visible event on the checkout-api timeline.

  • Problem

    Commit SHA does not match service version

    Likely cause

    Service mapping points at wrong repository or branch filter.

    Resolution

    Update service-to-repo mapping and default branch configuration.

    Verify

    Active version equals latest merged commit SHA after deploy.

  • Problem

    Change events arrive late

    Likely cause

    Webhook delivery retries or Actions job completion lag.

    Resolution

    Check webhook delivery logs and Actions completion timestamps.

    Verify

    Events appear within five minutes of production deploy completion.

PRODUCTION INTELLIGENCE

How GitHub contributes to production understanding

Each change signal enables a distinct investigation capability.

EvidenceEnables
CommitsVersion attribution
Pull requestsChange ownership
DeploymentsChange-aware RCA

DESIGN PARTNERS

Validate this evidence source with your production stack.

Design partners connect real evidence sources and validate investigation workflows before GA — with direct engineering access.

Become a Design PartnerRead integration docsBecome a Design Partner