Deploy Tracking

Record deployments via the API and view deploy markers on your uptime charts to correlate releases with incidents.

Overview

Deploy tracking lets you record when you ship new code and visualize those deployments alongside your uptime and response time charts. When something breaks after a deploy, you can immediately see the correlation — no more guessing which release caused the regression.

Recording a deployment

Send a POST request to the Signalog API when your deployment completes:

curl -X POST https://api.signalog.dev/v1/projects/{project_id}/deployments \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "version": "v2.4.1",
    "commit_sha": "a1b2c3d4e5f6",
    "environment": "production"
  }'

Request fields

FieldTypeRequiredDescription
versionstringYesVersion tag or label (e.g., v2.4.1, build-1234)
commit_shastringNoGit commit SHA for traceability
environmentstringNoEnvironment name (e.g., production, staging)
descriptionstringNoOptional description of what changed

Viewing deploy markers

Deploy markers appear as vertical dashed lines on your monitor’s response time and uptime charts. Hover over a marker to see the version, commit SHA, environment, and timestamp.

This makes it immediately visible when a deploy correlates with:

  • A spike in response times
  • A drop in uptime
  • The start of an incident

CI/CD integration

GitHub Actions

Add a step at the end of your deployment workflow:

- name: Record deployment in Signalog
  if: success()
  run: |
    curl -X POST https://api.signalog.dev/v1/projects/${{ secrets.SIGNALOG_PROJECT_ID }}/deployments \
      -H "Authorization: Bearer ${{ secrets.SIGNALOG_API_KEY }}" \
      -H "Content-Type: application/json" \
      -d '{
        "version": "${{ github.ref_name }}",
        "commit_sha": "${{ github.sha }}",
        "environment": "production"
      }'

GitLab CI

Add a deployment recording job to your .gitlab-ci.yml:

record_deployment:
  stage: post-deploy
  script:
    - |
      curl -X POST https://api.signalog.dev/v1/projects/${SIGNALOG_PROJECT_ID}/deployments \
        -H "Authorization: Bearer ${SIGNALOG_API_KEY}" \
        -H "Content-Type: application/json" \
        -d "{
          \"version\": \"${CI_COMMIT_TAG:-$CI_COMMIT_SHORT_SHA}\",
          \"commit_sha\": \"${CI_COMMIT_SHA}\",
          \"environment\": \"production\"
        }"
  only:
    - main

Other CI systems

The pattern is the same for any CI/CD system: make a POST request to the deployments endpoint after a successful deploy. Store your project ID and API key as secrets in your CI provider.

Filtering by environment

If you deploy to multiple environments (staging, production, etc.), deploy markers can be filtered by environment on the monitor detail page. Use the Environment dropdown above the chart to show markers for a specific environment or all environments.

Next steps