- Establish explicit resource links using service configuration, returned identifiers, observed endpoints or trace/request IDs. Similar names and a shared compartment are insufficient. Keep application/resource ID/link evidence/confidence in a small mapping table.
- Collect scoped log evidence through log_query and approved DB/host metrics through db_catalog and db_read. List the correct inventory first. Stop a branch when a prerequisite, resource mapping or operation is unavailable.
- Use the selected absolute UTC window; preserve backend rounding and lag. Distinguish parent CDB and PDB load, DB Management and Operations Insights IDs, rates and cumulative counters.
- Align events by event time, not query execution time. Compare observed ordering, plausible mechanism, dependency mapping and counterevidence. Label temporal overlap as a lead unless stronger evidence supports causation.
- Return a timeline, ranked explanations, uncertainty and one targeted next check per material gap. Missing samples do not establish an idle or healthy resource.
- APM queries, direct SQL, blocking-session actions, arbitrary infrastructure tools and changes are unavailable here. Do not infer their results. Use the error workflow for log details and disclose the native orchestrator limitation. No external notifications or automatic remediation.
Oracle Incident Correlator
Correlate application symptoms with verified database and host evidence in a shared time window. Use for incident relationships, not automatic remediation.
Oracle Incident Correlator by oracle-devrel · cdfc520
npx get-skill add oracle-devrel/oracle-incident-correlator File contents
---name: oracle-incident-correlatordescription: Correlate application symptoms with verified database and host evidence in a shared time window. Use for incident relationships, not automatic remediation.metadata: source: https://skillmd.com/skills/oracle-devrel/oracle-incident-correlator---1. Establish explicit resource links using service configuration, returned identifiers, observed endpoints or trace/request IDs. Similar names and a shared compartment are insufficient. Keep application/resource ID/link evidence/confidence in a small mapping table.2. Collect scoped log evidence through log_query and approved DB/host metrics through db_catalog and db_read. List the correct inventory first. Stop a branch when a prerequisite, resource mapping or operation is unavailable.3. Use the selected absolute UTC window; preserve backend rounding and lag. Distinguish parent CDB and PDB load, DB Management and Operations Insights IDs, rates and cumulative counters.4. Align events by event time, not query execution time. Compare observed ordering, plausible mechanism, dependency mapping and counterevidence. Label temporal overlap as a lead unless stronger evidence supports causation.5. Return a timeline, ranked explanations, uncertainty and one targeted next check per material gap. Missing samples do not establish an idle or healthy resource.6. APM queries, direct SQL, blocking-session actions, arbitrary infrastructure tools and changes are unavailable here. Do not infer their results. Use the error workflow for log details and disclose the native orchestrator limitation. No external notifications or automatic remediation.
oracle-devrel/technology-engineering commit cdfc520b14
Frequently asked questions
Run npx get-skill add oracle-devrel/oracle-incident-correlator in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Correlate application symptoms with verified database and host evidence in a shared time window. Use for incident relationships, not automatic remediation. It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
oracle-devrel (@oracle-devrel) published this skill. Their other Agent Skills are listed on their SkillMD profile.