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

Implement a model and API for events #112

Closed
ddabble opened this issue Aug 10, 2020 · 0 comments · Fixed by #123
Closed

Implement a model and API for events #112

ddabble opened this issue Aug 10, 2020 · 0 comments · Fixed by #123
Assignees
Labels
data model Affects the data model and/or SQL schema discussion Requires developer feedback/discussion before implementation

Comments

@ddabble
Copy link
Contributor

ddabble commented Aug 10, 2020

A "start event" would create/open a new incident, an "end event" would close the incident, and other events would simply provide a log of things connected to the incident. The latter would possibly include acknowledgements (see #72), which could automatically create an event that they're connected to.

The Event model should probably include these fields:

  • A relation to an Incident
  • A relation to the SourceSystem the event came from
  • A timestamp
  • An enum for the type of event (incident_start/incident_end/close/acknowledge/other)
  • A description of the event
@ddabble ddabble added discussion Requires developer feedback/discussion before implementation data model Affects the data model and/or SQL schema labels Aug 10, 2020
@ddabble ddabble self-assigned this Aug 11, 2020
@hmpf hmpf closed this as completed in #123 Aug 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data model Affects the data model and/or SQL schema discussion Requires developer feedback/discussion before implementation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant