mirror of
https://github.com/elastic/kibana.git
synced 2025-06-27 18:51:07 -04:00
092cc0d098
## Summary Resolves: https://github.com/elastic/kibana/issues/166301 Adds support for solution/category filtering to maintenance windows by adding a new property: `category_ids`. Selecting one or more solutions when creating/updating a maintenance window will cause the maintenance window to only suppress rule types belonging to said solutions. In order to achieve filtering by solution/category, we are adding a new field to the rule types schema called `category`. This field should map to the feature category that the rule type belongs to (`observability`, `securitySolution` or `management`). Our initial plan was to use feature IDs or rule type IDs to accomplish this filtering, we decided against using rule type IDs because if a new rule type gets added, we need to change the API to support this new rule type. We decided against feature IDs because it's a very anti-serverless way of accomplishing this feature, as we don't want to expose feature IDs to APIs. We decided on app categories because it works well with serverless and should be much easier to maintain if new rule types are added in the future. This means the `rule_types` API has to be changed to include this new field, although it shouldn't be a breaking change since we're just adding a new field. No migrations are needed since rule types are in memory and maintenance windows are backwards compatible. ![image]( |
||
|---|---|---|
| .. | ||
| common | ||
| public | ||
| server | ||
| jest.config.js | ||
| kibana.jsonc | ||
| README.md | ||
| tsconfig.json | ||
Alerting Example
This example plugin shows you how to create a custom Rule Type, create rules based on that type and corresponding UI for viewing the details of all the rules within the custom plugin.
To run this example, use the command yarn start --run-examples.