Track Deployments in Your Log Timeline

Deployment markers appear as purple vertical lines on your LogFlow overview chart. When you see a spike in errors after a deploy, you know exactly which release caused it — without cross-referencing timestamps between your CI tool and your logging dashboard.

How it works

After every deploy, send a single API call to LogFlow with the version, service name, and optional description. LogFlow stores it and overlays it on the 24-hour timeline chart.

Step 1 — Get your API key

Go to LogFlow → Settings and copy your API key. It starts with lf_.

Step 2 — Send a deployment marker

The simplest integration is one curl command at the end of your deploy script:

curl -X POST https://api.getlogflow.com/v1/deployments \
  -H "Authorization: Bearer lf_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "version": "v1.4.2",
    "service": "api",
    "environment": "production",
    "description": "Fix payment timeout bug"
  }'

Fields:

• version — git tag, commit SHA, or version string (required)
• service — which service was deployed (required)
• environment — production, staging, etc. (optional)
• description — what changed (optional, shown in the dashboard)

Step 3 — Add to GitHub Actions

Add a deployment step at the end of your release workflow:

# .github/workflows/deploy.yml
name: Deploy

on:
  push:
    branches: [main]

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Deploy to production
        run: |
          # your existing deploy commands here
          ./scripts/deploy.sh

      - name: Record deployment in LogFlow
        if: success()
        env:
          LOGFLOW_API_KEY: ${{ secrets.LOGFLOW_API_KEY }}
        run: |
          curl -X POST https://api.getlogflow.com/v1/deployments \
            -H "Authorization: Bearer $LOGFLOW_API_KEY" \
            -H "Content-Type: application/json" \
            -d "{
              \"version\": \"${{ github.sha }}\",
              \"service\": \"api\",
              \"environment\": \"production\",
              \"description\": \"${{ github.event.head_commit.message }}\"
            }"

Add LOGFLOW_API_KEY to your repository secrets: GitHub → Settings → Secrets and variables → Actions → New repository secret.

Step 4 — View in the dashboard

Open LogFlow → Overview. The 24-hour chart now shows purple vertical lines at each deployment time. Hover over a line to see the version and description. The "Deployments (last 24h)" panel below the chart lists them chronologically.

Correlating errors with deploys

Scenario: Your error rate jumps from 0.1% to 3.2% at 14:32. You see a purple marker at 14:30 labeled v2.1.0 — Refactor payment flow.

Click the marker → LogFlow filters logs to the 10-minute window around that deployment. You can immediately search for errors in that window:

level:error service:api

And correlate with the specific commit that caused the issue.

Using the CLI

You can also record deployments via the LogFlow CLI:

# Coming in CLI v0.2.0
logflow deployments create --version v1.4.2 --service api --env production

For now, use the HTTP API as shown above.

FAQ

Can I delete a deployment marker? Yes — via the API: DELETE /v1/deployments/:id. The deployment ID is returned in the POST response and shown in the dashboard.

How far back do deployment markers go? Deployment markers are stored in the database (not ClickHouse), so they don't expire with your log retention period. They persist indefinitely.

Can I record multiple services in one pipeline? Yes — just send multiple API calls, one per service deployed. Each appears as a separate marker on the timeline.