root-cause-analysis

Correlate Ansible Automation Platform job logs with Splunk OpenShift pod logs.

9|10|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/redhat-et/rhdp-rca-plugin --skill root-cause-analysis-redhat-et
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: root-cause-analysis
Source: https://github.com/redhat-et/rhdp-rca-plugin/tree/main/experiments/combine_rca_context/v1
Command: npx skills add https://github.com/redhat-et/rhdp-rca-plugin --skill root-cause-analysis-redhat-et

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python-dotenv, and includes scripts (resource) components.

What problem does it solve?

Investigate failed Ansible Automation Platform jobs by automatically correlating local AAP job logs with Splunk OpenShift pod logs and repository configuration to quickly identify root causes and actionable fixes.

Core Features & Use Cases

  • Automated Log Parsing: Parse AAP job files (.json, .json.gz and transformed variants) to extract job metadata, failed tasks, timestamps, GUIDs, namespaces, and pod references.
  • Splunk Correlation: Query Splunk using namespace, GUID, or time windows to fetch OCP logs and error events and extract correlated pods and messages.
  • Timeline & Evidence: Build an interleaved timeline of AAP events and Splunk errors to produce confidence-scored correlation and evidence.
  • Configuration & Code Context: Fetch AgnosticV configuration and AgnosticD workload code from GitHub to map failed tasks to repository files and variable precedence for precise root-cause reasoning.
  • Actionable Summary: Produce a schema-backed summary with failed task details, correlation proof, root cause, confidence, and specific file-level recommendations.

Quick Start

Run the root-cause-analysis by pointing the skill to a job log or job ID so it parses the job, queries Splunk for correlated logs, builds a timeline, and saves analysis outputs for review.

Frequently Asked Questions about root-cause-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I correlate Ansible Automation Platform job logs with Splunk OpenShift pod logs for root cause analysis?

You can correlate failed AAP job logs with Splunk OpenShift pod logs by parsing local job files for metadata and timestamps, querying Splunk via REST API using namespace or GUID, and building an interleaved timeline to produce evidence-backed root cause summaries.

What is the best way to diagnose failed RHDP deployments using AgnosticD and AgnosticV configurations?

Diagnose failed RHDP deployments by fetching AgnosticV configuration and AgnosticD workload code from GitHub, mapping failed AAP tasks to repository files and variable precedence for precise root-cause reasoning and file-level recommendations.

Does root cause analysis work with compressed Ansible Automation Platform job log files?

Yes, automated log parsing supports AAP job files in .json, .json.gz, and transformed variants, extracting job metadata, failed tasks, timestamps, GUIDs, namespaces, and pod references to initiate the Splunk correlation process.

Can I query Splunk logs using namespace and time windows to find OpenShift pod errors?

Yes, you can query Splunk using namespace, GUID, or time windows to fetch OpenShift logs and error events, extracting correlated pods and messages to build an interleaved timeline with confidence-scored correlation evidence.

What limitations exist when correlating AAP job failures with Splunk data for infrastructure incidents?

This root cause analysis is applicable to RHDP deployments and requires local AAP job logs and Splunk data access. It relies on GitHub retrieval for AgnosticD and AgnosticV configurations, limiting its use to those specific repository structures.