CircleCI Integration
Connect CircleCI pipelines to TigerOps. Deploy markers, job duration trends, pipeline event ingestion, and production anomaly correlation — no plugin or CircleCI plan upgrade required.
How It Works
Add API Key Context
Create a CircleCI context (e.g., tigerops) and add TIGEROPS_API_KEY as an environment variable. Contexts allow you to share the secret across multiple projects and pipelines securely.
Add Notification Job
Add a notify_tigerops job to your .circleci/config.yml that runs at the end of your deploy workflow. Use a curl command or the tigerops/notify CircleCI orb to send pipeline events to TigerOps.
Configure Workflow
Add the notify_tigerops job to your deploy workflow with requires: [deploy] so it runs after a successful or failed deployment. Use when: always to capture both success and failure events.
Pipeline Events Flow In
Every CircleCI deploy creates a marker on TigerOps dashboards with workflow name, pipeline number, branch, commit SHA, and job duration. Failed pipelines are surfaced in incident correlation.
What You Get Out of the Box
Pipeline Event Ingestion
Pipeline created, workflow completed, workflow failed, and job completed events with pipeline number, workflow name, branch, commit SHA, actor, and total duration are forwarded to TigerOps.
Deploy Markers on Dashboards
Every successful deploy to production creates a vertical marker on all TigerOps metric dashboards. The marker includes the CircleCI pipeline URL, committer, and the deployed revision.
Job Duration Tracking
Send per-job timing to TigerOps to track build, test, and deploy job durations over time. Slow CI jobs are detected and alerted on, preventing CI bottlenecks from blocking engineering velocity.
Failed Deploy Correlation
CircleCI pipeline failures and failed deploys appear in the TigerOps incident timeline. When a metric anomaly follows a deploy, the pipeline link is surfaced automatically for faster root cause analysis.
Multi-Workflow Support
Different workflows (build, deploy, rollback, canary) are tracked separately in TigerOps. Each workflow type creates events tagged with the workflow name for granular visibility.
Orb-Based Integration
The tigerops/notify CircleCI orb simplifies setup to three lines. The orb handles event construction, authentication, and retry logic automatically — no need to write curl commands manually.
config.yml Setup
Add a notify job and wire it to your deploy workflow to forward events to TigerOps.
# .circleci/config.yml
version: 2.1
# Option A: Use the TigerOps orb (simplest)
orbs:
tigerops: tigerops/notify@1
jobs:
build:
docker:
- image: cimg/node:20.10
steps:
- checkout
- run: npm ci && npm run build
test:
docker:
- image: cimg/node:20.10
steps:
- checkout
- run: npm test
deploy:
docker:
- image: cimg/node:20.10
steps:
- checkout
- run: ./scripts/deploy.sh
# Option B: Manual notification job (no orb required)
notify_tigerops:
docker:
- image: curlimages/curl:latest
steps:
- run:
name: Send deploy event to TigerOps
command: |
curl -sf -X POST https://api.tigerops.io/v1/events -H "Authorization: Bearer $TIGEROPS_API_KEY" -H "Content-Type: application/json" -d "{
"event_type": "ci.deploy",
"service": "$TIGEROPS_SERVICE_NAME",
"environment": "production",
"attributes": {
"ci.pipeline.number": "$CIRCLE_BUILD_NUM",
"ci.workflow.id": "$CIRCLE_WORKFLOW_ID",
"ci.commit.sha": "$CIRCLE_SHA1",
"ci.commit.branch": "$CIRCLE_BRANCH",
"ci.pipeline.url": "$CIRCLE_BUILD_URL",
"ci.deployer": "$CIRCLE_USERNAME"
}
}"
workflows:
deploy_workflow:
jobs:
- build
- test:
requires: [build]
- deploy:
requires: [test]
filters:
branches:
only: main
- notify_tigerops:
requires: [deploy]
context: tigerops # context holding TIGEROPS_API_KEY
when: always # run even if deploy failsCommon Questions
Does the integration require a CircleCI paid plan?
No. Contexts (for storing the TIGEROPS_API_KEY) are available on all CircleCI plans including Free. The curl-based notification approach works with any CircleCI plan. The TigerOps orb also works on all plans.
How do I ensure the notify job runs even when the deploy fails?
Set when: always on the notify_tigerops job in the workflow definition. This ensures the job runs regardless of whether the upstream deploy job succeeded or failed, so both outcomes are captured in TigerOps.
Can I use CircleCI webhooks instead of a job in the pipeline?
Yes. CircleCI supports project-level webhooks that POST to a URL on workflow completion. Configure a CircleCI webhook pointing to the TigerOps Webhook receiver URL for a zero-config-file alternative.
How does TigerOps handle CircleCI parallelism and matrix jobs?
Each parallel job run sends an individual event. TigerOps groups events from the same workflow run using the CIRCLE_WORKFLOW_ID attribute, allowing you to see aggregate statistics for parallelized test suites.
Does TigerOps track rerun workflows from CircleCI?
Yes. Rerun workflows include CIRCLE_WORKFLOW_ID which differs from the original. TigerOps treats reruns as new pipeline events tagged with a rerun: true attribute so you can filter them in dashboards.
Correlate CircleCI Deploys with Production Metrics
Pipeline events, deploy markers, job duration trends — add one notify job to .circleci/config.yml.