workflow-triaging

Classify AEM 6.5/AMS workflow symptoms and map them to runbooks or Splunk searches.

1|Updated Oct 7, 2024
One-click install
npx skills add https://github.com/valithedge/etisalatedge --skill workflow-triaging-valithedge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-triaging
Source: https://github.com/valithedge/etisalatedge/tree/main/.agents/skills/workflow-triaging
Command: npx skills add https://github.com/valithedge/etisalatedge --skill workflow-triaging-valithedge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Classifies workflow symptoms, gathers the right logs and metrics, and maps issues to the appropriate runbooks or Splunk searches for AEM 6.5 LTS and Adobe Managed Services (AMS) to support production operations.

Core Features & Use Cases

  • Symptom classification and mapping to runbooks or Splunk searches
  • Guided log and metric collection (log patterns, error messages, and JMX data)
  • Remediation mapping with runbooks and Splunk queries for AMS and on-prem environments
  • Supports both 6.5 LTS / AMS deployments with consistent triage guidance

Quick Start

Provide a triage for a reported workflow issue by gathering logs for the host, identifying the symptom, and mapping to the appropriate runbook.

Frequently Asked Questions about workflow-triaging

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

FAQPage Schema
How do I triage AEM workflow issues using error logs and JMX metrics?

To triage AEM workflow issues, classify the reported symptoms, collect relevant error logs and JMX metrics, then map those patterns to the correct runbook or Splunk search for remediation guidance.

What is the best way to identify AEM 6.5 LTS workflow symptoms from Splunk logs?

Identifying AEM 6.5 LTS workflow symptoms involves matching specific error log patterns collected from Splunk against known issue classifications to select the appropriate remediation runbook.

Can I use this workflow triage process for Adobe Managed Services environments?

Yes, the workflow triage process supports both AEM 6.5 LTS and Adobe Managed Services environments by providing consistent symptom classification, log pattern guidance, and runbook mapping.

Do I need access to JMX metrics to classify AEM production workflow issues?

Yes, you need access to JMX metrics to quantify workflow health, alongside error logs and Splunk or AMS logs, to accurately classify symptoms and map them to the correct runbooks.

How to map AEM workflow error messages to the correct remediation runbook?

Map AEM workflow error messages to remediation runbooks by gathering host logs, identifying the symptom classification, and selecting the matching runbook or Splunk query provided by the triage guidance.

Why does my AEM workflow triage require specific log patterns and Splunk searches?

AEM workflow triage requires specific log patterns and Splunk searches to accurately classify symptoms, quantify JMX workflow health metrics, and pinpoint the correct production support runbook.