MTAR T3D Sessions: Why Monitoring Isn’t Enough: The Case for Full Postgres Logging
Failed to add items
Add to basket failed.
Add to Wish List failed.
Remove from Wish List failed.
Follow podcast failed
Unfollow podcast failed
-
Narrated by:
-
By:
About this listen
Welcome back to More Than a Refresh Presents: T3D Sessions.In this episode, Command Prompt Founder Joshua “JD” Drake talks with Justin Graf, Senior DBA & Engineer at Command Prompt, about a topic every Postgres team needs to understand: why monitoring alone isn’t enough—and why full logging is essential for diagnosing database problems. Justin explains how organizations often rely solely on monitoring tools like PGStatStatements, CloudWatch, or Datadog, without realizing that these tools can’t show query parameters, historical performance shifts, or the root cause behind sudden CPU spikes. Without full logging, teams end up blind during outages, wasting hours trying to detect issues that proper logs would have revealed immediately.