-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Alerting] JIRA connector to append comments to existing tickets #77319
Comments
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
I'm not completely familiar with the Jira connector, but the main problem with this kind of workflow is that the alert has to "remember" the id of the Jira ticket that was originally created. But we don't really have a way of doing that today. We don't really process the output of action execution in any meaningful way, and make it available back to the alert. We have some ways of doing that - alert state and instance state - but this state is "forgotten" if the alert is ever disabled. And in general seems a bit too fragile to me. This sounds like a scenario that the "cases" integration should probably handle, which provides a more complete life cycle story for incident management systems like this. |
Pinging @elastic/security-threat-hunting-cases (Team:Threat Hunting:Cases) |
Pinging @elastic/response-ops (Team:ResponseOps) |
Pinging @elastic/response-ops-cases (Feature:Cases) |
Describe the feature:
From https://discuss.elastic.co/t/alerts-with-the-combination-of-multiple-metrics/247653
The text was updated successfully, but these errors were encountered: