Export AWR Report
PMP4PG allows you to export any generated AWR report as a standalone HTML file — fully self-contained, shareable and viewable offline without access to the platform.
Exporting the Report
Once a report has been generated (see Generate a Report →), click the Export HTML button at the top of the report page.
{screenshot: awr-export-button}
The browser downloads the report file automatically:
awr-report_pg-prod-01_snap42-snap44_2025-01-15.html
The filename includes the server name, the begin and end snapshot IDs, and the report date.
Report File Contents
The exported HTML file is completely self-contained:
- All CSS styles are embedded
- All charts are rendered as inline SVG or embedded JavaScript
- No external dependencies, CDN calls or platform connection required
- Can be opened in any modern browser
Sections Included
| Section | Included |
|---|---|
| Report Header (server, snapshots, elapsed time) | ✅ |
| Table of Contents with anchor links | ✅ |
| Load Profile | ✅ |
| Time Model Statistics | ✅ |
| Instance Efficiency Ratios | ✅ |
| Top SQL (all 4 tabs) | ✅ |
| Wait Events Statistics | ✅ |
| Lock Contention Analysis | ✅ |
| Bloat Analysis | ✅ |
| Vacuum Statistics | ✅ |
| WAL Activity & Checkpoint Statistics | ✅ |
{screenshot: awr-exported-report-browser}
Use Cases
| Use Case | How AWR Export Helps |
|---|---|
| Incident report | Attach a complete workload report covering the incident period |
| Change validation | Compare pre- and post-deployment AWR reports side by side |
| Capacity planning | Share workload trends with infrastructure teams |
| Performance audit | Provide an objective workload baseline to auditors |
| Archive | Store periodic AWR reports for compliance or historical reference |
| Collaboration | Share with team members who do not have platform access |
Naming Convention
Reports are automatically named using the following pattern:
awr-report_{hostname}_{begin-snap-id}-{end-snap-id}_{date}.html
Example:
awr-report_pg-prod-01_snap042-snap044_2025-01-15.html