Introduction Ansible callback plugins control output formatting, logging, and notifications. When callbacks are misconfigured, you lose visibility into playbook execution, making debugging difficult.

Symptoms - No output from ansible-playbook (blank screen) - Log files not being created - Notification callbacks (Slack, email) not firing - Output format not matching configured callback - Custom callback plugin not loading

Common Causes - Callback plugin not in the configured callback_plugins path - stdout_callback not set in ansible.cfg - Callback plugin has syntax errors - Multiple stdout_callback plugins conflicting - Callback plugin requires dependencies not installed

Step-by-Step Fix 1. **Check configured callbacks**: ```bash ansible-config dump | grep -E "CALLBACK|stdout_callback" ```

  1. 1.Set the stdout callback:
  2. 2.```ini
  3. 3.[defaults]
  4. 4.stdout_callback = yaml
  5. 5.callbacks_enabled = timer, profile_tasks
  6. 6.`
  7. 7.Verify callback plugin is loadable:
  8. 8.```bash
  9. 9.ansible-doc -t callback -l | grep <plugin-name>
  10. 10.`

Prevention - Test callback plugins in development first - Document callback configuration in team wiki - Use callback plugins for CI/CD integration (JUnit, JSON output) - Monitor callback plugin dependencies - Use ansible-config to verify settings