-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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 necessary privileges to apps using alerting #60135
Comments
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
Some notes while I work on this ... The following files need changes
Metrics is under infra, which also includes logs, so it's not as 1-1 as uptime. To repro not being able to see alerts with these users now, I created the following role and user: role: alerting_uptime_metrics
user: al (erting)
Logged in as this user, the Alerts and Actions management app does not appear. In order to create an index threshold alert, you'll need to have an index pattern for the index to read from. I'm using |
resolves elastic#60135 See the reference issue for how to configure Kibana to test this manually. There are no automated tests for this ATM. The basic test scenario is to create a role with just the Uptime space privilege, make sure it get to the Alerts and Actions management app, make sure you can create an action (server log), and alert (index threshold), and that the alert and action run successfully. Then repeat with just the Metrics space privilege.
resolves elastic#60135 See the reference issue for how to configure Kibana to test this manually. There are no automated tests for this ATM. The basic test scenario is to create a role with just the Uptime space privilege, make sure it get to the Alerts and Actions management app, make sure you can create an action (server log), and alert (index threshold), and that the alert and action run successfully. Then repeat with just the Metrics space privilege.
resolves #60135 See the reference issue for how to configure Kibana to test this manually. There are no automated tests for this ATM. The basic test scenario is to create a role with just the Uptime space privilege, make sure it get to the Alerts and Actions management app, make sure you can create an action (server log), and alert (index threshold), and that the alert and action run successfully. Then repeat with just the Metrics space privilege.
) resolves elastic#60135 See the reference issue for how to configure Kibana to test this manually. There are no automated tests for this ATM. The basic test scenario is to create a role with just the Uptime space privilege, make sure it get to the Alerts and Actions management app, make sure you can create an action (server log), and alert (index threshold), and that the alert and action run successfully. Then repeat with just the Metrics space privilege.
) resolves elastic#60135 See the reference issue for how to configure Kibana to test this manually. There are no automated tests for this ATM. The basic test scenario is to create a role with just the Uptime space privilege, make sure it get to the Alerts and Actions management app, make sure you can create an action (server log), and alert (index threshold), and that the alert and action run successfully. Then repeat with just the Metrics space privilege.
…62188) resolves #60135 See the reference issue for how to configure Kibana to test this manually. There are no automated tests for this ATM. The basic test scenario is to create a role with just the Uptime space privilege, make sure it get to the Alerts and Actions management app, make sure you can create an action (server log), and alert (index threshold), and that the alert and action run successfully. Then repeat with just the Metrics space privilege.
…62189) resolves #60135 See the reference issue for how to configure Kibana to test this manually. There are no automated tests for this ATM. The basic test scenario is to create a role with just the Uptime space privilege, make sure it get to the Alerts and Actions management app, make sure you can create an action (server log), and alert (index threshold), and that the alert and action run successfully. Then repeat with just the Metrics space privilege.
Right now SIEM is the only app with alerting and actions privileges. Until features privileges is fully supported, we should add permissions to:
This snippet shows how it is done for SIEM, we would do the same in other apps:
kibana/x-pack/legacy/plugins/siem/server/plugin.ts
Lines 86 to 144 in 875e2a5
Alerting/Actions management UI capabilities have explicit checks on the SIEM feature, this may need some rework:
kibana/x-pack/plugins/triggers_actions_ui/public/application/lib/capabilities.ts
Lines 13 to 25 in 8951424
The text was updated successfully, but these errors were encountered: