Harness Integration
Deployment verification metrics, pipeline execution stats, and feature flag events for Harness. Extend Harness CV with TigerOps metrics and get full observability across your entire software delivery lifecycle.
How It Works
Configure Harness Webhook Notifications
In Harness, create a notification rule using the Generic Webhook channel and point it to your TigerOps endpoint. Enable Pipeline, Stage, Step, and Deployment events to get full execution visibility.
Set TigerOps as a CV Metrics Provider
Add TigerOps as a Harness Continuous Verification health source. Configure the remote-read endpoint so Harness CV can query TigerOps metrics during deployment verification analysis.
Add the TigerOps Shell Script Step
Insert the TigerOps notify shell script step in your Harness pipelines to emit enriched change events at critical points — before traffic shifting, after canary verification, or after rollback.
Correlate CV Results with Production Metrics
TigerOps ingests Harness CV analysis results and overlays them alongside APM and infrastructure metrics, giving you a unified view of deployment health that extends beyond the CV window.
What You Get Out of the Box
Deployment Verification Analysis Tracking
Ingest Harness CV analysis results — risk scores, anomaly counts, and log cluster findings — as time series metrics. TigerOps tracks CV pass and fail rates per service to identify services with recurring verification failures.
Pipeline Execution Stats
Monitor Harness pipeline stage durations, step execution times, and pipeline success rates. TigerOps alerts when pipeline execution times regress and surfaces which stages are contributing to increased delivery latency.
Feature Flag Event Tracking
Ingest Harness Feature Flags toggle events as change events in TigerOps. When a feature flag change correlates with a metric anomaly, TigerOps surfaces the flag name and targeting rules in the incident context.
Canary & Blue-Green Analysis
Track canary traffic split progression, baseline vs. canary metric comparisons, and final promotion or rollback decisions. TigerOps stores the full canary analysis timeline for post-deployment review.
Rollback Frequency & Root Cause
Monitor rollback frequency per service and pipeline. TigerOps correlates rollback events with the specific CV findings or manual triggers that caused them, helping teams reduce root cause investigation time.
STO & Policy Failure Metrics
Track Harness Security Testing Orchestration scan results and OPA policy evaluation failures as pipeline health metrics. TigerOps alerts when STO failure rates indicate increasing supply chain risk across your services.
Harness Pipeline with TigerOps Notify Step
Add a Shell Script step to your Harness pipeline to emit deployment events to TigerOps.
#!/bin/bash
# Harness Shell Script step — TigerOps deployment event
# Add as a step after your Kubernetes Apply or deployment step
# Reference TIGEROPS_API_KEY from Harness Secrets Manager
curl -s -X POST https://ingest.atatus.net/api/v1/events \
-H "Authorization: Bearer ${TIGEROPS_API_KEY}" \
-H "Content-Type: application/json" \
-d "{
"event": "deployment",
"service": "<+service.name>",
"environment": "<+env.name>",
"version": "<+artifact.tag>",
"pipeline": "<+pipeline.name>",
"pipeline_url": "<+pipeline.executionUrl>",
"triggered_by": "<+pipeline.triggeredBy.name>"
}"
# ─── Harness Notification Rule (YAML) ────────────────────────────
# Add to your pipeline notification rules:
#
# notificationRules:
# - name: TigerOps All Events
# enabled: true
# pipelineEvents:
# - type: PipelineSuccess
# - type: PipelineFailed
# - type: StageFailed
# - type: StageSuccess
# notificationMethod:
# type: Webhook
# spec:
# webhookUrl: https://ingest.atatus.net/api/v1/harness/events
# headers:
# Authorization: Bearer <+secrets.getValue("tigerops_api_key")>Common Questions
Which Harness modules does TigerOps integrate with?
TigerOps integrates with Harness CD (deployment events and CV results), Harness FF (feature flag events), Harness CI (build metrics via webhooks), and Harness STO (scan result metrics). Each module integration can be enabled independently.
How does TigerOps serve as a Harness CV health source?
TigerOps exposes a Prometheus-compatible remote-read endpoint. In Harness, you add this as a custom health source in your monitored service configuration. Harness CV queries TigerOps metrics during the analysis window and TigerOps returns the requested time series.
Can TigerOps trigger a Harness rollback when it detects a metric anomaly?
Yes. TigerOps can call the Harness Pipeline REST API to trigger a rollback pipeline when its AI correlation engine links a metric anomaly to a recent Harness deployment. Configure the Harness API key and rollback pipeline ID in TigerOps settings.
Does TigerOps work with Harness NextGen (NG) and Harness FirstGen (CG)?
TigerOps supports both Harness NextGen (current platform) via the NG webhook notification rules and API, and Harness FirstGen via the CG webhook notification rules. The integration configuration differs slightly between the two platforms.
How are Harness feature flag events correlated with metric anomalies?
When a feature flag is toggled in Harness FF, TigerOps records a change event with the flag name, project, environment, and targeting rule change. The AI correlation engine then scans for metric anomalies that begin within the post-change window on services that consume that flag.
Extend Harness CV with TigerOps Intelligence
CV metric source, feature flag correlation, and deployment verification analytics. Integrate in under 10 minutes.