Sample Reports

Open complete, error-only, and incremental pgBadger reports from the local site snapshot

Reference

The example content was generated by pgBadger 11.8 in May 2022. The original examples are stored with this site, so report navigation, charts, styles, and scripts remain available without reaching the upstream server.

Example	What it demonstrates	Local copy
Complete report	PostgreSQL activity together with PgBouncer statistics	Open the complete report
Incremental report	Calendar index, weekly aggregation, and daily pages	Open the incremental index
Errors and events	A report restricted to errors and operational events	Open the error report

Complete report

The complete report is a self-contained HTML document. Use its top navigation to inspect global statistics, queries, sessions, connections, temporary files, checkpoints, autovacuum activity, locks, and PgBouncer-specific charts.

The data is a demonstration fixture, not a current benchmark. Values, PostgreSQL versions, and the embedded pgBadger UI reflect the report generation date.

Incremental hierarchy

The incremental example preserves the full link structure:

report/
├── index.html
├── 2012/
│   ├── week-49/index.html
│   ├── week-50/index.html
│   └── 12/06 … 12/index.html
└── 11/
    ├── pgbadger.min.css
    ├── pgbadger.min.js
    └── bundled chart and UI assets

The top index links to two weekly reports and seven daily reports. All relative links were retained, so moving only index.html would break the example; keep the complete directory tree together.

Security and privacy

Real reports may expose SQL text, bind values, database and user names, application names, client addresses, error details, and workload patterns. Before publishing a report:

use --anonymize when literals are not needed;
apply include/exclude filters before report generation;
inspect the final HTML or exported data, not only the command line;
protect the report location with the same care as operational logs.