pgBadger is a powerful tool to optimize your PostgreSQL servers. Using your server log files, pgBadger will analyze the SQL traffic and produce a profusion of statistics (longest queries, read/write ratio, etc.). This is very helpful but the amount of data generated is so big that the pgbadger reports are hard to read and useful stats are often drown in the flood... Check out this sample pgBadger report to see the mess !

Since my previous blog post, we've been working hard to redefine the pgBadger user experience and create a new report template.

Here's the first draft of this new prototype (For now the draft is just static HTML code, we hope we'll have a live demo in the forthcoming weeks).

As you can we followed a few basic principles :

  • Split the big HTML tables in smaller tables and use tab navigation to switch :


  • Leave some blank spaces to make the report easier to read :


  • Hide big tables behind graphs, when possible :


  • Put "full details" in popup windows that can you can hide/show when you need it :


  • Emphasize "key values" using a bigger font size :


As you can see, there's nothing either out of the ordinary or very original here. But this new design will surely be easier to read and be more insightful. We hope it will attract new users, while being more helpful for the existing user base.

If you have any comment or ideas, please join the pgBadger mailing list and get involved !

blog comments powered by Disqus