-
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
add Kibana version to eventLog ECS log entries #56771
Comments
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
I think this can be a constant keyword field. |
Related PR |
going to remove and re-add this issue to the alerting project, so it will be re-triaged; we recently chatted about this, and realized we'll want this in by 8.0, and maybe earlier, to help with versions-specific queries when the saved object id's change for share-ability |
we may want to keep |
Yes, if we end up going with
Seems highly likely that we'd be making use of |
@pmuellr my main concern with |
good point! you win :-) |
Wanted to note that RAC is probably going to be adding a Kibana version field as well - but they might not right now, since it technically wouldn't be needed for the "first release" (you can check that version by lack of the field). So we probably want to wait till that's settled, so we use the same field name. |
Marking as blocked to give time to align with the approach for alert data indices. |
I came across this as well as an option: https://www.elastic.co/guide/en/elasticsearch/reference/master/version.html |
I realized we probably want the Kibana version added to the eventLog ECS log entries. Will probably need to go in the top-level custom
kibana
object property.There may be a few other bits we want in there as well. Should poke around what other Kibana-specific properties are available, to see if we want it added.
The text was updated successfully, but these errors were encountered: