Default

1. Check in using the :eyes: emoji on the chatbot message.

2. Find the Root Cause for the issue using the Dashboard

   1. Check Metrics to look for the problematic service.

      1. Start from the top of the tech stack and move down until you find the offending service. (Dashboard is ordered with the services at the top of the stack at the top of the page.) This gives you an idea of what might have went wrong.

   2. Check Logs to root cause the specific problem that caused the alarm

      1. Document the root cause (with the corresponding error message if applicable) in the chatbot alert thread.

      2. If root cause is not clear, tag @Jeremy Yau in the thread and he will help take a look.

3. Propose Mitigating Action in the thread

   1. If no Mitigating Action required, mark chatbot message with a ❎,

   2. If code change is required to take Mitigating Action

      1. Create a GitHub ticket for the Mitigating Action to track progress on the fix.

      2. Once GitHub ticket is created, comment the link to the Jira ticket in the thread and then mark Issue as Resolved by marking chatbot message with a ✅.

      3. Depending on urgency, code change can be done either immediately, or put into the backlog to be prioritized by the PM.

   3. If other mitigating action is required, reach out to @Jeremy Yau.