mirror of
https://github.com/elastic/kibana.git
synced 2025-06-28 03:01:21 -04:00
e0e0a26b43
## Summary This PR is updating Discover's rule to be created under the `stackAlerts` consumer and we created an [breaking change issue](https://github.com/elastic/dev/issues/2344) to explain the consequences of this update. We also fix the rule's consumer for all rule types created under the observability rule management to use their producer instead of `alerts`. Also, we add the ability for the ES Query and new Generic Threshold rules type to pick the consumer associated to the rule. The `ensureAuthorized` and the `filter` functions have modified and simplified to support this use case please check the newest unit test added in `x-pack/plugins/alerting/server/authorization/alerting_authorization.test.ts`. There is now a dropdown in the rule form to prompt the user when creating ES Query/Generic threshold rules to select the consumer based on their authorized consumers (we can no longer use `alerts` for these). If there is only 1 option, then the dropdown will not be shown and the option will be chosen automatically. Generic threshold rules will have the following possible consumers: - infrastructure - logs ES query rules will have the following possible consumers: - infrastructure - logs - stackAlerts (only from the stack management rule page) ## To Test: ### Single Consumer: 1. Create a user with only `logs` feature enabled (ensuring `stackAlerts` is not enabled). 2. Navigate to the O11Y rule management page 3. Click the create rule button 4. Assert that both ES query and generic threshold rules are available 5. Click ES query and fill out the relevant information and create the rule 6. Assert that the rule created has `logs` set in the `consumer` field 7. Repeat 5-6 for the generic threshold rule 8. Repeat 2-7 but on the Stack Management rules page 9. Repeat 1-8 for the `infrastructure` feature. ### Multiple Consumers: 1. Create a user with `logs`, `infrastructure` and `apm` features enabled (ensuring `stackAlerts` is not enabled). 2. Navigate to the O11Y rule management page 3. Click the create rule button 4. Assert that both ES query and generic threshold rules are available 5. Click ES query and fill out the relevant information and create the rule 6. A dropdown should prompt the user to select between 1 of the 3 consumers, select 1 7. Assert that the rule was created with the selected consumer 8. Repeat 5-7 for the generic threshold rule 9. Repeat 2-8 but on the Stack Management rules page   ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: Jiawei Wu <74562234+JiaweiWu@users.noreply.github.com> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
17 lines
751 B
TypeScript
17 lines
751 B
TypeScript
/*
|
|
* Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one
|
|
* or more contributor license agreements. Licensed under the Elastic License
|
|
* 2.0 and the Server Side Public License, v 1; you may not use this file except
|
|
* in compliance with, at your election, the Elastic License 2.0 or the Server
|
|
* Side Public License, v 1.
|
|
*/
|
|
|
|
export * from './src/default_alerts_as_data';
|
|
export * from './src/legacy_alerts_as_data';
|
|
export * from './src/technical_field_names';
|
|
export * from './src/alerts_as_data_rbac';
|
|
export * from './src/alerts_as_data_severity';
|
|
export * from './src/alerts_as_data_status';
|
|
export * from './src/alerts_as_data_cases';
|
|
export * from './src/routes/stack_rule_paths';
|
|
export * from './src/rule_types';
|