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.

Sign up for GitHub

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

Jump to bottom

[RAC] Populate alert status field with allowed values #108607

Closed
marshallmain opened this issue Aug 13, 2021 · 2 comments
Closed

[RAC] Populate alert status field with allowed values #108607

marshallmain opened this issue Aug 13, 2021 · 2 comments
Labels
bug Fixes for quality problems that affect the customer experience Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Theme: rac label obsolete

Comments

@marshallmain
Copy link
Contributor

Per the latest Alerts as Data schema definition, the alert status field kibana.alert.status is expected to be populated with either active or recovered. A number of places in Kibana are populating this field with open or closed. We need to audit each of these places, determine if the intent is to represent the workflow status kibana.alert.workflow_status (which does allow the values open, acknowledged, and closed) or the "system" status kibana.alert.status in which case we need to update the field value to either active or recovered.

A bonus would be enforcing these allowed values with Typescript types.
@botelastic botelastic bot added the needs-team Issues missing a team label label Aug 13, 2021
@marshallmain marshallmain added bug Fixes for quality problems that affect the customer experience Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Detections and Resp Security Detection Response Team Theme: rac label obsolete and removed needs-team Issues missing a team label labels Aug 13, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detections-response (Team:Detections and Resp)

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@marshallmain marshallmain mentioned this issue Aug 18, 2021
Merged
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Fixes for quality problems that affect the customer experience Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Theme: rac label obsolete
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@elasticmachine @marshallmain