The product was born out of our shared vision that understanding and being able to troubleshoot performance problems in the database world shouldn't be as hard as it is nowadays. More than once we've seen a project going belly-up during normal operation with no talented DBAs being available on short notice.
There are plethora of reasons why this can happen, be it missed opportunities for indexes, growth of data sets, features being deployed without looking at performance implications or hardware issues.
When confronted with such situations for a skilled DBA the approach is usually the same:
- Get a picture of what's going on in the database
- Understand the problems the client wants to address
- Work out the most efficient solution to get there, be it application changes, schema improvements or hardware upgrades
More often than not there's not sufficient instrumentation to get a good understanding what's going on with a database right away and especially with scaling issues not having historic data to compare to is a huge challenge.
Not having this data is similar to being called to a huge factory that has a production halt, no documentation and plans at hand, being tasked with making sure that production can start again ASAP. "How does this work?" - "Has this ever worked?" - "Is this even important?" and other thoughts pop up in the mind of the DBA during the stressful hours (or even days) to come.
With pganalyze we want to give you a tool which allows you to get a good insight in what's going on in your database, provide you with the historic data you need for context and offer a good foundation for efficient consulting in performance and scaling questions.