-
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
[Response Ops][Alerting] Alerts as data aliases should be hidden #178589
Comments
Pinging @elastic/response-ops (Team:ResponseOps) |
Remembering when we did something very similar for the event log - one issue we had was that the additional processing could take a while, and encounter errors. Can't remember if we made initialization wait through these modifications, and what we do with errors - beyond ignoring them (more or less ... there's not much we can do). I'm thinking we even stopped logging them because they were noisy. Looking through the event log PRs, this one looks particularly relevant: #122882 |
As a note - because these aliases are not hidden, when we execute a ESQL query that uses |
I would really appreciate if this got prioritized 🙏 |
Adding a note to ensure we don't introduce any negative side effects by switching to hidden. |
Hey! Any updates on this one? |
We´ll be discussing this today, @stratoula ... hoping to revert soon |
Alerts as data indices are created as hidden but their aliases are not, leading to some inconsistencies. We should be able to create new aliases as hidden by setting
is_hidden: true
here but we should also add a call to update existing aliases to hidden during resource installation.The text was updated successfully, but these errors were encountered: