log-fetcher

Fetch remote Ansible ETL transform logs via SSH by job number or time window.

9|10|Updated Mar 17, 2026

Search Tags:#automation #logs #ansible #ssh #rsync #root-cause-analysis #log-fetching

Ready to run

npx skills add https://github.com/redhat-et/rhdp-rca-plugin --skill log-fetcher

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: log-fetcher
Source: https://github.com/redhat-et/rhdp-rca-plugin/tree/main/skills/logs-fetcher
Command: npx skills add https://github.com/redhat-et/rhdp-rca-plugin --skill log-fetcher

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Collecting remote Ansible / AAP2 ETL logs for incident investigation is time-consuming and error-prone when done manually; this skill automates locating and transferring the exact transform log files you need to a local analysis directory.

Core Features & Use Cases

Fetch by time or mode: Select processed, ignored, or all transform files within a time window, sorted and limited as needed.
Fetch by job number: Provide one or more job identifiers to find matching transform files and transfer them reliably.
Operational use case: Use this to quickly gather relevant ETL artifacts for root cause analysis of failed jobs, correlate logs with Splunk or GitHub context, and feed downstream parsing steps.

Quick Start

Run the log fetcher by ensuring your SSH profile connects without a password and then execute the provided scripts to retrieve logs by time range or job number.

Frequently Asked Questions about log-fetcher

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

FAQPage Schema

How do I fetch remote Ansible logs via SSH for incident investigation?▼

You fetch remote Ansible logs via SSH by running automated scripts that locate and transfer specific transform log files to a local directory. This retrieves ETL artifacts needed to investigate failed jobs using job numbers or time windows.

Can I retrieve AAP2 ETL transform files by job number?▼

Yes, you can retrieve AAP2 ETL transform files by providing one or more job identifiers. The scripts find matching transform files on the remote Ansible server and transfer them reliably to your local analysis directory.

Do I need rsync and passwordless SSH to collect remote Ansible logs?▼

Yes, you need rsync installed on your client system and an SSH profile configured for passwordless access. Fetching remote Ansible logs requires SSH connectivity to the remote host and specific environment variables set.

How do I filter collected ETL logs by time window and file mode?▼

You filter collected ETL logs by specifying a time range and selecting a mode such as processed, ignored, or all transform files. The retrieved logs are sorted and limited according to your parameters.

What is the best way to automate log retrieval for AAP2 root cause analysis?▼

Automating log retrieval for AAP2 root cause analysis is best done by using scripts to fetch exact transform files via SSH. This eliminates manual collection errors and feeds downstream parsing steps or Splunk correlation.

Why does fetching Ansible logs require REMOTE_DIR and REMOTE_HOST environment variables?▼

Fetching Ansible logs requires REMOTE_DIR and REMOTE_HOST environment variables to establish the SSH connection and locate the exact directory containing the ETL transform files on the remote server.