WHY
PostgresCPUHigh  is now a critical level alert and SOP needs to be actionable and improved

WHAT
PostgresCPUHigh  is now a critical level alert and SOP needs to be actionable and improved

HOW

• understand the alert
• understand what could be the root causes of the alert firing (consider rapid growth [possible issues with 3scale] issues  vs steady growth [ heavy usage and db is getting out of space])
• write actionable steps to investigate / debug the alert
• write actionable steps to fix the alert (can be that the only way to fix it is to bump the instance type to next level)

DONE
SOP for the alert is improved and is actionable (ping Pat on the review)