Ansible Integration
Surface configuration change events and automatically tie them to performance regressions. Monitor playbook execution, detect configuration drift, and correlate every Ansible run with infrastructure metrics.
How It Works
Install the TigerOps Callback Plugin
Add the tigerops callback plugin to your Ansible configuration. The plugin captures playbook start, task results, host facts, and completion events without modifying your existing playbooks.
Configure the Webhook Endpoint
Set your TigerOps ingest endpoint and API key in ansible.cfg or as environment variables. Events are forwarded in real time as each task completes across all targeted hosts.
Tag Playbooks with Change Metadata
Add tigerops_tags variables to your playbooks to annotate change events with environment, service name, and change ticket ID. TigerOps uses these to scope correlation searches automatically.
Correlate Changes with Metrics
TigerOps automatically overlays Ansible change events on your infrastructure and application dashboards, flagging metric anomalies that occur within configurable windows after each deployment.
What You Get Out of the Box
Playbook Execution Tracking
Full visibility into playbook duration, task-level pass/fail counts, host reach rates, and retry attempts. Historical playbook run timelines are stored and searchable by tag or inventory group.
Performance Regression Correlation
TigerOps automatically correlates Ansible change events with CPU, memory, latency, and error rate anomalies on affected hosts, surfacing likely regressions within seconds of playbook completion.
Configuration Drift Detection
Track idempotency violations by monitoring tasks that report "changed" on repeated runs. TigerOps alerts when drift is detected and shows which hosts and tasks are drifting from the desired state.
Task Failure Analysis
Capture failed task output, error messages, and host context automatically. TigerOps groups failures by module type and inventory group to surface systemic issues across your fleet.
Inventory & Host Metrics
Monitor host reachability, SSH connection times, and fact-gathering durations across your dynamic or static inventory. Identify hosts causing playbook slowdowns before they block CI pipelines.
Change Event Timeline
A unified change event feed shows every Ansible run with its target inventory, changed task count, duration, and triggering user or pipeline. Overlay this on any TigerOps dashboard for instant context.
Ansible Callback Plugin Setup
Enable the TigerOps callback plugin in your Ansible configuration to start forwarding change events.
# ansible.cfg — TigerOps callback plugin configuration
# pip install tigerops-ansible
[defaults]
# Enable the TigerOps callback alongside any existing callbacks
callbacks_enabled = tigerops
[callback_tigerops]
# TigerOps ingest endpoint
endpoint = https://ingest.atatus.net/api/v1/events
api_key = ${TIGEROPS_API_KEY}
# Post-change correlation window (seconds)
correlation_window = 900
# Environment tag applied to all events from this host
environment = production
# Annotate playbook runs with change metadata
# These variables can also be set per-playbook in vars:
default_service = infrastructure
default_team = platform-eng
---
# Example playbook with TigerOps change metadata
- name: Deploy nginx config update
hosts: web_servers
vars:
tigerops_tags:
service: nginx
environment: production
change_id: CHG-4821
team: platform-eng
roles:
- nginxCommon Questions
Does TigerOps require modifications to existing Ansible playbooks?
No. TigerOps uses the Ansible callback plugin architecture, which hooks into playbook execution without any changes to your existing playbooks or roles. You only need to enable the plugin in ansible.cfg and provide your API key.
How does TigerOps correlate an Ansible run with a metric regression?
TigerOps records a change event timestamp and the list of affected hosts when a playbook completes. It then scans the metric time series for those hosts over a configurable post-change window (default 15 minutes) and flags any anomalies using its AI correlation engine.
Can TigerOps monitor Ansible Tower or AWX job executions?
Yes. TigerOps integrates with the Ansible Tower and AWX REST APIs to ingest job execution events, template names, inventory sources, and credential types, providing the same correlation capabilities for controller-driven runs.
What data does the TigerOps callback plugin send?
The plugin sends playbook name, play names, task names and durations, per-host task results (ok/changed/failed/skipped), total host count, and any tigerops_tags variables you define. No variable values or sensitive host facts are transmitted.
Can I use TigerOps to detect configuration drift across a large fleet?
Yes. TigerOps tracks "changed" task counts per host over time. When a playbook that should be fully idempotent starts reporting changes on specific hosts, TigerOps fires a drift alert with the offending host list and task names.
Stop Hunting for What Changed Before the Regression
Automatic change-to-metric correlation, drift detection, and playbook analytics. Set up in under 5 minutes.