-
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] write event log entries for alert execution and it's actions #61706
Conversation
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
8f409ef
to
981b106
Compare
dcc3c56
to
b472eba
Compare
resolves elastic#55636 Writes eventLog events for alert executions, and the actions executed from that alert execution.
b472eba
to
df94dce
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, other than the message which I feel we should make a big clearer as it is likely to find its way into our UI rather than just begin a log line.
}, | ||
], | ||
}, | ||
"message": "alert: test:1: name-of-alert instanceId: 2 scheduled actionGroup: default action: test:1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we perhaps use quotes around the IDs just to make this a bit more readable?
As we'll likely be displaying this in the UI at some point, it might be worth figuring out how to make these clearer.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ya, I'll add some quotes - I think I had them in for a while, but removed them during some clean up.
We'll have to have a discussion about these message
properties. I'm currently thinking they're useless. Messages like this are supposed to be for humans to help search through the bits, but the current use cases don't include stories like that. We should probably have all the data they need as fields in the docs. Or perhaps easier, feed all the fields into a text field via copy_to
, which gives us the text search capability.
Note today, the message does include info like alert name, type, that is not yet in the actual event doc. Denormalizing those bits is a bullet point in the umbrella issue #62221
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
…ns (elastic#61706) resolves elastic#55636 Writes eventLog events for alert executions, and the actions executed from that alert execution.
resolves #55636
Writes eventLog events for alert executions, and the actions executed from
that alert execution.
First step in getting event logging working with alerts/actions, see umbrella issue #62221
Checklist