Codefresh Integration
GitOps pipeline metrics, Argo workflow health, and deployment frequency for Codefresh. Trace every deployment from pipeline trigger through Argo CD sync to production metric impact.
How It Works
Enable Codefresh Pipeline Trigger Webhooks
Configure a TigerOps webhook in Codefresh under Account Settings > Integrations > Webhooks. Select pipeline trigger events and step completion events to begin forwarding execution metadata.
Connect Argo CD via TigerOps Monitor
Deploy the TigerOps Argo CD monitor to your cluster. It scrapes Argo CD controller metrics and application sync statuses and forwards them to TigerOps alongside your Codefresh pipeline events.
Add TigerOps Freestyle Step
Insert a TigerOps freestyle step in your Codefresh YAML pipelines to emit deployment change events with enriched metadata — image tag, environment, and triggering Git event — at pipeline completion.
Correlate Pipeline Events with App Health
TigerOps links Codefresh pipeline completions to downstream Argo CD sync events and service metric changes, giving you an end-to-end delivery trace from Git commit to production health impact.
What You Get Out of the Box
Codefresh Pipeline Execution Metrics
Track Codefresh pipeline duration, step timings, and success and failure rates per pipeline and trigger. TigerOps alerts on duration regressions and surfaces which steps are on the critical path of your pipelines.
Argo CD Application Sync Health
Monitor Argo CD application sync status, health status, and out-of-sync duration. TigerOps alerts when applications stay out-of-sync beyond your threshold and correlates sync failures with upstream pipeline events.
Argo Workflow Execution Tracking
Track Argo Workflows workflow run duration, template step failures, and workflow queue depth. TigerOps provides a historical view of workflow performance trends and failure patterns across workflow templates.
Deployment Frequency & DORA Metrics
Compute deployment frequency, change lead time, change failure rate, and MTTR from Codefresh and Argo CD events. TigerOps visualizes DORA metric trends over time per service and team.
GitOps Image Update Tracking
Monitor Argo CD Image Updater events when image tags are automatically updated in Git. TigerOps correlates image update commits with the Argo CD sync that follows, giving you a complete image delivery trace.
Pipeline Resource & Cache Metrics
Track Codefresh pipeline runner resource consumption and Docker layer cache hit rates. TigerOps surfaces build steps with low cache hit rates that are candidates for caching optimization to reduce pipeline duration.
Codefresh Pipeline with TigerOps Freestyle Step
Add a TigerOps notify step to your Codefresh YAML pipeline for enriched deployment events.
# codefresh.yml — TigerOps integration
# Add TIGEROPS_API_KEY to your Codefresh pipeline variables (encrypted)
version: "1.0"
stages:
- build
- test
- deploy
- notify
steps:
BuildImage:
stage: build
type: build
image_name: my-api
tag: "${{CF_SHORT_REVISION}}"
dockerfile: Dockerfile
RunTests:
stage: test
image: "${{BuildImage}}"
commands:
- npm test
DeployToProduction:
stage: deploy
image: codefresh/kubectl
commands:
- kubectl set image deployment/my-api my-api=my-api:${{CF_SHORT_REVISION}}
when:
branch:
only: [main]
NotifyTigerOps:
stage: notify
image: curlimages/curl:latest
commands:
- |
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": "my-api",
"environment": "production",
"version": "${{CF_SHORT_REVISION}}",
"pipeline": "${{CF_PIPELINE_NAME}}"
}"
when:
steps:
- name: DeployToProduction
on: [success]Common Questions
Does TigerOps support both Codefresh Classic and Codefresh GitOps (formerly Argo CD)?
Yes. TigerOps integrates with Codefresh Classic pipelines via webhook notifications and with Codefresh GitOps (powered by Argo CD) via the TigerOps Argo CD monitor and Codefresh GitOps Runtime events.
How does TigerOps monitor Argo CD alongside Codefresh pipelines?
TigerOps deploys a lightweight monitor to your cluster that scrapes the Argo CD application controller Prometheus endpoint. It correlates Argo CD sync events with Codefresh pipeline completion events using Git commit SHA as the linking key.
Can TigerOps track Argo Rollouts alongside Argo CD and Codefresh?
Yes. TigerOps monitors Argo Rollouts via the Prometheus metrics endpoint exposed by the rollouts-controller. Canary step completion, traffic weights, and rollback events are correlated with Codefresh pipeline events and APM metrics.
Which Codefresh triggers does TigerOps capture?
TigerOps captures Git triggers (push, PR), Cron triggers, Docker Hub and registry triggers, and Helm chart repository triggers via the Codefresh webhook API. Each trigger type is labeled in TigerOps for filtering.
How does TigerOps compute change lead time for Codefresh GitOps pipelines?
TigerOps computes change lead time as the elapsed time from Git commit timestamp to the Argo CD sync completion event that deploys that commit to production. This requires both Codefresh pipeline webhooks and the Argo CD monitor to be configured.
End-to-End Delivery Tracing from Code to Production
Codefresh pipeline metrics, Argo CD sync health, and DORA analytics in one place. Connect in under 10 minutes.