-
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
[event log] can't find events since action/alert saved object are now hidden #70086
Labels
Feature:Alerting
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Comments
pmuellr
added
Feature:Alerting
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
labels
Jun 26, 2020
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
6 tasks
1 task
pmuellr
added a commit
to pmuellr/kibana
that referenced
this issue
Jul 9, 2020
resolves elastic#70086 Configures the saved object client for the event log to access the recently hidden action and alert saved objects. We didn't have tests for action/alert event log activity, so added some now. Also found a buglet that was preventing access to event log data from actions and alerts in non-default spaces.
pmuellr
added a commit
that referenced
this issue
Jul 16, 2020
resolves #70086 Configures the saved object client for the event log to access the recently hidden action and alert saved objects. We didn't have tests for action/alert event log activity, so added some now. Also found a buglet that was preventing access to event log data from actions and alerts in non-default spaces.
pmuellr
added a commit
to pmuellr/kibana
that referenced
this issue
Jul 16, 2020
…#70395) resolves elastic#70086 Configures the saved object client for the event log to access the recently hidden action and alert saved objects. We didn't have tests for action/alert event log activity, so added some now. Also found a buglet that was preventing access to event log data from actions and alerts in non-default spaces.
pmuellr
added a commit
to pmuellr/kibana
that referenced
this issue
Jul 16, 2020
…#70395) resolves elastic#70086 Configures the saved object client for the event log to access the recently hidden action and alert saved objects. We didn't have tests for action/alert event log activity, so added some now. Also found a buglet that was preventing access to event log data from actions and alerts in non-default spaces.
pmuellr
added a commit
that referenced
this issue
Jul 16, 2020
…#72050) resolves #70086 Configures the saved object client for the event log to access the recently hidden action and alert saved objects. We didn't have tests for action/alert event log activity, so added some now. Also found a buglet that was preventing access to event log data from actions and alerts in non-default spaces.
pmuellr
added a commit
that referenced
this issue
Jul 16, 2020
…#72049) resolves #70086 Configures the saved object client for the event log to access the recently hidden action and alert saved objects. We didn't have tests for action/alert event log activity, so added some now. Also found a buglet that was preventing access to event log data from actions and alerts in non-default spaces.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Feature:Alerting
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Since PR #67109 was merged, the event log hasn't been able to return any events since the alert and action saved objects are now hidden. The savedObjectsClient that's created in the event log needs to be tweaked to look for hidden types for actions and alerts.
There is already a "fix" for this in the branch for PR #68437, but I'm thinking it may be better to extract it out of here and put in a separate PR.
There is also issue #63961, which will again change the way actions/alerts are pre-checked for access before returning the event log - somehow we need to allow actions/alerts to do their own lookup (to find the preconfigured actions), and also to allow them to use their own internal code including RBAC to make a determination if the action/alert is ok.
I think we probably can't wait for issue #63961 to be implemented, so the quick hack of adding hidden type support in #68437 is probably the way to go.
The text was updated successfully, but these errors were encountered: