Observability
pg-collector
AI observability for PostgreSQL
pg-collector captures PostgreSQL telemetry, turns it into structured signals, and gives engineering teams a tight loop for investigation, triage, and capacity planning.
CLI examples
Start the local agent
pg-collector agent startBoot the collector next to your PostgreSQL instance.
Capture against a target
pg-collector capture --dsn $DATABASE_URLAttach to a live instance and normalize telemetry streams.
Diagnose a recent window
pg-collector diagnose --window 15mGenerate a focused diagnostic summary for the last 15 minutes.
What it does
A focused workflow, not a generic platform pitch
Each product page follows the same template so the navigation scales while the content stays readable.
Captures telemetry directly from PostgreSQL and surrounding infrastructure.
Turns low-level metrics and events into investigation-ready timelines.
Creates AI-friendly context so debugging starts with evidence instead of guesswork.
Architecture diagram
pg-collector in the stack
Dark, monospace, and direct. The point is legibility, not decoration.
PostgreSQL
Metrics, logs, query traces, replication state
Collector Agent
Normalizes telemetry and streams structured events
Burnside Pipeline
Adds context, retention, and AI-assisted diagnosis
Alerts + Insights
Operational views, triage prompts, and historical analysis
Key features
What makes this product useful in practice
The feature list stays product-specific while reusing the same card language across the site.
PostgreSQL-native telemetry
Collect signals that match how the database actually behaves in production.
Minimal infrastructure
Run close to the database with a lightweight operational footprint.
AI reasoning layer
Structure telemetry so LLM-driven diagnostics can be grounded in evidence.
Fast incident review
Move from symptom to query, workload, or replication issue without context switching.
Use cases
Where teams get leverage
Simple, concrete use cases are more credible than broad category claims.
Production incident triage
Pinpoint regressions, lock contention, or workload shifts before they cascade.
Capacity planning
Understand when query volume, write pressure, or replication lag crosses safe limits.
Database platform operations
Give platform teams a cleaner operating model across multiple PostgreSQL deployments.
GitHub plus consulting
A clean split between GitHub evaluation and consulting rollout
Each repo should be useful on its own, with Burnside consulting available when teams want help turning it into a production workflow.
Open source
Collector agent and local telemetry workflows
CLI-driven inspection and export
Single-team deployment patterns
Consulting
Managed policy, retention, and multi-environment rollups
Shared operational views for platform and security teams
Commercial support, onboarding, and roadmap partnership
Call to action
Start building with pg-collector
Review the repo, then bring Burnside in when you want help applying it to a real PostgreSQL environment.