Help & User Guide
Quick reference for knowing which DBA Copilot feature to use in each situation.
Oracle — when to use each feature
AWR / ASH Analysis
Use it when: the system is slow, you want to analyse performance over a specific period, or you need to identify the most expensive queries and wait events.
What you get: root cause of the problem, top queries, top wait events, optimisation recommendations.
Query Advisor
Use it when: you want to optimise specific queries without a direct database connection.
What you get: query analysis, index suggestions, optimised rewrite, estimated improvement.
Database Profile
Use it when: you want to track your database performance over time.
What you get: evolution of key metrics, progressive degradation detection, period comparisons.
Investigations
Use it when: there is an active incident or you want to document and resolve a problem collaboratively.
What you get: AI chat workspace, attachments, incident timeline and automatic postmortem.
AI Memory (RAG)
What it is: DBA Copilot automatically indexes every resolved investigation. When a new problem appears, the AI searches for similar past cases and uses them as context.
What you get: responses enriched with your own historical cases — "In March you had this same pattern in COREP_AH, the root cause was a missing index."
Note: RAG activates automatically when there are resolved investigations in your organization. No configuration needed.
Supported file types
When creating an investigation you can attach:
- Oracle: AWR (.html/.txt), ASH, Statspack, Alert Log, Trace Files (.trc)
- PostgreSQL: PostgreSQL logs, EDB PWR/DRITA
- MongoDB: mongod.log, profiler, serverStatus, dbStats, collStats, currentOp, mongostat, mongotop, rs.status, $indexStats
- Application: Java application logs, JVM GC logs
- System: SAR reports, OS logs (syslog/dmesg)
- Custom: any text file
Tip: Time-based filtering
When attaching log files, you can specify a time range (from / to) to focus the analysis on the relevant period. This reduces noise and improves diagnosis accuracy — especially useful for large log files.
PostgreSQL — when to use each feature
Query Advisor (offline)
Use it when: you have pg_stat_statements output and want to identify the most problematic queries.
What you get: query cost ranking, index suggestions, execution plan analysis.
Investigations
Use it when: there is a performance problem and you want to analyse it with AI by attaching logs and execution plans.
What you get: AI-guided diagnosis with PostgreSQL-specific recommendations.
AI Memory (RAG)
What it is: DBA Copilot automatically indexes every resolved investigation. When a new problem appears, the AI searches for similar past cases and uses them as context.
What you get: responses enriched with your own historical cases — "In March you had this same pattern in COREP_AH, the root cause was a missing index."
Note: RAG activates automatically when there are resolved investigations in your organization. No configuration needed.
Recommended workflow for an investigation
-
1
Identify the time window
When did it start? How long did it last? Is it still active?
-
2
Collect evidence
Oracle: AWR for the period + Alert Log. PostgreSQL: logs for the period + pg_stat_statements.
-
3
Create an investigation in DBA Copilot
Describe the problem and attach the collected files.
-
4
Analyse with AI
The chat will guide you to dig deeper into the root causes. The assistant will automatically reference similar past cases from your organization's history if available.
-
5
Document and close
Generate the postmortem once the issue is resolved.