Skip to content

GitHub / GitLab Integration

CheckOps integrates with GitHub and GitLab to automatically track deployments and correlate code changes with performance data.

Deployment markers create visual annotations on your monitoring timeline. They let you correlate performance changes with specific deployments.

Field Source Description
service CI/CD config Service or application name
version Git SHA or tag Deployed version identifier
environment CI/CD config Target environment (staging, production)
commit_url Git provider Link to the commit or merge request
author Git provider Who triggered the deployment
timestamp Automatic When the deployment was recorded

Deployment markers appear as vertical lines on monitor graphs:

Response Time (ms)
400 ┤
350 ┤
300 ┤ ┃ deploy v2.1.0
250 ┤ ────┃────────────
200 ┤────── ┃
150 ┤ ┃ ────
100 ┤ ┃
└──────────┃──────────────
00:00 06:00 12:00

This makes it immediately obvious when a deployment caused a performance regression or improvement.

When deployment markers are enabled, CheckOps automatically compares metrics before and after each deployment:

Metric Before After Change
Avg response time 210ms 185ms -12%
P95 response time 450ms 380ms -16%
Error rate 0.1% 0.3% +200%
Uptime 99.98% 99.95% -0.03%

Significant regressions trigger alerts through your configured notification channels.

  1. Navigate to Settings > Integrations
  2. Click Add Integration > GitHub
  3. Authorize CheckOps to access your repositories
  4. Select which repositories to track

CheckOps requests minimal permissions:

  • repo:status — Read commit status
  • read:org — Read organization membership

Once connected, CheckOps can automatically create deployment markers when:

  • A deployment event is received via GitHub webhook
  • A release is published
  • A workflow run completes on the main branch
  1. Navigate to Settings > Integrations
  2. Click Add Integration > GitLab
  3. Enter your GitLab instance URL (supports self-hosted)
  4. Create a Project Access Token with read_api scope
  5. Configure the webhook URL in your GitLab project

Configure your GitLab project webhook to send:

  • Deployment events — Triggered when a deployment completes
  • Pipeline events — Triggered when a pipeline finishes (filter by branch)
  • Tag push events — Triggered when a release tag is pushed

If you prefer not to use OAuth, you can create deployment markers directly via the API. See the API Keys & CI/CD guide for examples with GitHub Actions and GitLab CI.

You can connect multiple repositories to a single CheckOps organization. Each repository maps to one or more services, allowing you to track deployments across your entire stack:

frontend (GitHub) → service: "web"
backend (GitLab) → service: "api"
workers (GitLab) → service: "workers"

All deployment markers appear on the same timeline, giving you a unified view of changes across services.