CI/CDService Hook + TigerOps task extension

Azure DevOps Pipelines Integration

Pipeline run metrics, agent pool utilization, and release gate event monitoring for Azure DevOps. Optimize your Azure pipeline capacity and correlate every release with production health.

Monitor Azure Pipelines Book a Demo

Setup

How It Works

Add a Service Hook to Azure DevOps

In your Azure DevOps organization, go to Project Settings > Service Hooks and create a new subscription using the Web Hooks service. Select Pipeline run state changed and Run stage state changed events and point them to your TigerOps endpoint.

Configure the TigerOps Task Extension

Install the TigerOps extension from Azure DevOps Marketplace. Add the TigerOps Notify task to your YAML pipelines to emit enriched deployment change events with service, environment, and release version metadata.

Enable Agent Pool Metrics Collection

Provide an Azure DevOps PAT with Agent Pools read permission to TigerOps. The API poller tracks agent pool capacity, running job counts, queue depths, and agent provisioning times across all your pools.

Correlate Releases with Production Metrics

TigerOps overlays Azure DevOps release and pipeline events on your APM and infrastructure dashboards, automatically flagging metric regressions that follow each release deployment.

Capabilities

What You Get Out of the Box

Pipeline Run Duration & Success Rates

Track pipeline run duration, stage timing, and success and failure rates per pipeline definition and branch. TigerOps histograms detect duration regressions and compare performance across branches and YAML template versions.

Agent Pool Utilization Monitoring

Monitor Microsoft-hosted and self-hosted agent pool utilization — running vs. queued job counts, parallel job consumption, and agent provisioning latency. TigerOps alerts when pool capacity limits are causing build queuing.

Release Gate Event Tracking

Ingest release gate evaluation results — Azure Monitor, REST API, and work item gate outcomes — as structured events. TigerOps tracks gate pass and fail rates and how long releases wait for gate approvals.

Parallel Job Concurrency Metrics

Track how many parallel jobs your Azure DevOps organization is consuming at peak and whether you are hitting your concurrent job limits. TigerOps visualizes parallelism utilization over time to inform capacity planning.

Deployment to Environment Events

Monitor Azure DevOps Environment deployment events — Kubernetes, virtual machines, and AKS — with deployment status, approval state, and deployment duration per environment and stage.

DORA Metrics from Azure DevOps

Compute deployment frequency, change lead time, change failure rate, and MTTR from Azure DevOps pipeline and release events correlated with incident data from your alerting integrations.

Configuration

Azure Pipelines YAML with TigerOps Task

Add the TigerOps task to your Azure Pipelines YAML to emit deployment events and track stage metrics.

azure-pipelines.yml

# azure-pipelines.yml — TigerOps integration
# Add TIGEROPS_API_KEY as a secret pipeline variable

trigger:
  branches:
    include: [main]

pool:
  vmImage: ubuntu-latest

stages:
  - stage: Build
    jobs:
      - job: BuildAndTest
        steps:
          - task: NodeTool@0
            inputs:
              versionSpec: "20.x"
          - script: npm ci && npm test
            displayName: "Install & Test"

  - stage: Deploy
    dependsOn: Build
    condition: succeeded()
    jobs:
      - deployment: DeployProduction
        environment: production
        strategy:
          runOnce:
            deploy:
              steps:
                - script: ./scripts/deploy.sh
                  displayName: "Deploy"

                # TigerOps Notify task (install from Marketplace)
                - task: TigerOpsNotify@1
                  displayName: "Notify TigerOps"
                  inputs:
                    apiKey:      "$(TIGEROPS_API_KEY)"
                    service:     my-api
                    environment: production
                    version:     "$(Build.SourceVersion)"
                  condition: succeeded()

FAQ

Common Questions

Does TigerOps support both Classic Pipelines and YAML Pipelines in Azure DevOps?

Yes. TigerOps receives events from both Classic Build pipelines, Classic Release pipelines, and YAML multi-stage pipelines via Service Hooks. The TigerOps task extension works in YAML pipelines. For Classic Release pipelines, use the Service Hook webhook.

How does TigerOps access Azure DevOps agent pool metrics?

TigerOps uses the Azure DevOps REST API with a PAT scoped to Agent Pools (read) permission. It polls the distributedtask/pools and distributedtask/queues endpoints every minute to collect pool capacity, agent status, and job queue depth.

Can TigerOps monitor Azure Pipelines running on Azure Arc-enabled servers?

Yes. Self-hosted agents running on Arc-enabled servers or any on-premises machine register with Azure DevOps agent pools. TigerOps monitors them via the agent pool API the same way as any other self-hosted agent.

How do release gates integrate with TigerOps metrics?

You can configure an Azure DevOps release gate that calls the TigerOps query API to check whether service metrics are within acceptable bounds before allowing a release to proceed. This lets TigerOps data directly influence release promotion decisions.

Does TigerOps support multi-organization Azure DevOps setups?

Yes. Configure a Service Hook and PAT in each Azure DevOps organization and provide them to TigerOps. Metrics and events from all organizations are aggregated with an organization label dimension, allowing per-organization filtering in dashboards.

Get Started

Optimize Azure Pipelines and Eliminate Deployment Blind Spots

Agent pool analytics, release gate metrics, and DORA tracking for Azure DevOps. Set up in under 10 minutes.

Start Free Talk to an Engineer