Introduction

One of the many ways of creating incidents at Rootly is through our Slack bot. Our customers rely on this bot to perform various actions as declaring, changing incident status, paging on-call people without leaving Slack.

Project

This project goal is to develop a simple Slack bot and web UI.

• Slack command can receive 2 commands
  • /rootly declare <title>
  • /rootly resolve
• Web UI
  • List incidents created and being able to sort them alphabetically ASC/DESC ( using turbo ). Tailwind CSS / View components is plus but not required.
• Shine in the domain you feel the most skilled with ( Frontend vs Backend ). Or both!

/rootly declare <title>

• This command will open a modal to create a new incident
  • This command works in any channel.
  • A title is required, a description is optional, a severity (sev0, sev1, sev2) is optional.
  • New incident will create a dedicated Slack channel so people can troubleshoot the issue.
  • You will store the new incident created in an incidents table backed by PostgreSQL.
  • You will create a simple UI to display list of incidents with their title, description, severity and the creator.

/rootly resolve

• This command works in a dedicated incident slack channel only.
• Only available in the dedicated Slack incident channel, this will mark the status of the incident as resolved and display back to the channel the time it took the team to get to resolution.

Deployment ( Version 1 )

There are obviously numerous ways to deploy this service and expose it on the internet. This is project is very small and straightforward, i had like you to deploy it on Render using their free plan.

Deployment ( Version 2, only for SRE role )

There are obviously numerous ways to deploy this service and expose it on the internet. Although this is project is very small and straightforward, I’d like for you to deploy it scalably.

For this project, Dockerize the application and use whatever technology (e.g. Kubernetes, AWS ECS, Terraform, etc.) you think is best.

Notes

These are open-ended instructions—you can take it in whatever direction you want. How you display information and UI, in general, is also up to you. In the interest of time, please do not spend too much time on the UI.