Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backend: Add database schema for storing incidents (or notice) data #28

Closed
aldy505 opened this issue May 23, 2024 · 0 comments · Fixed by #31
Closed

Backend: Add database schema for storing incidents (or notice) data #28

aldy505 opened this issue May 23, 2024 · 0 comments · Fixed by #31

Comments

@aldy505
Copy link
Member

aldy505 commented May 23, 2024

On Railway status page (https://status.railway.app/) they call it "notice" instead of "incident", since not everything is an incident anyway. Maybe we should convert our wording into that.

But.. we still need a database schema for storing those notices. It should include this data (as minimum):

  • Title -> the title of the notice
  • Timestamp -> Event timestamp
  • Status -> must be one of "investigating" | "identified" | "monitoring" | "resolved" | "scheduled". If the timestamp is in the future, the status must only be "scheduled"
  • Level (or severity) -> Informational, Warning, Error, Fatal

Some examples on how we would display this on the frontend:

image

image

Incident detail:
image
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant