High Consumption Instance Database
Incident Report for Take Blip
Resolved
Context: It was identified through our monitoring and high consumption in one of the Instances of the database responsible for the context tables of the bots.

The root cause: The high consumption was due to the increase in requisitions, with a partial impact on one of our clusters.

Customer Impact: Slow Message Exchange on Bots

Action: Scale Up was performed on our Database restoring the environment.

Start date/time: 06/09/2021 10:50 AM
End date/time: 11:23 AM
Posted Sep 06, 2021 - 12:14 GMT-03:00
This incident affected: Channels (BlipChat) and Take Blip Platform (Portal).