mirror of
https://github.com/elastic/kibana.git
synced 2025-04-25 10:23:14 -04:00
545732caad
# Backport This will backport the following commits from `main` to `8.x`: - [[ResponseOps][Rules] Add solution field to rule types (#212079)](https://github.com/elastic/kibana/pull/212079) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Umberto Pepato","email":"umbopepato@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-12T16:19:58Z","message":"[ResponseOps][Rules] Add solution field to rule types (#212079)\n\nWe need to add a `solution` field to rule types in order to provide a\nroot-level categorization based on the Kibana solution/area that owns\neach rule type. This will serve as a more reliable alternative to\nprevious attempts at `featureId`-based filtering.\n\n## Summary\n\n- Adds a `solution` field to rule type objects, accepting the values\n`observability`, `security` and `stack`.\n- Categorizes existing rule types.\n- Updates tests with the new field.\n\n## Verification steps\n\n1. Check that the rule types you own have been categorized under the\ncorrect solution\n2. Create rules in multiple areas of Kibana\n3. Check that those rules show up correctly in their UIs and work\ncorrectly\n\n## References\n\nCloses #212017","sha":"f8a3051605a5663d99253ee698d441ac32fe3868","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:obs-ux-infra_services","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0"],"title":"[ResponseOps][Rules] Add solution field to rule types","number":212079,"url":"https://github.com/elastic/kibana/pull/212079","mergeCommit":{"message":"[ResponseOps][Rules] Add solution field to rule types (#212079)\n\nWe need to add a `solution` field to rule types in order to provide a\nroot-level categorization based on the Kibana solution/area that owns\neach rule type. This will serve as a more reliable alternative to\nprevious attempts at `featureId`-based filtering.\n\n## Summary\n\n- Adds a `solution` field to rule type objects, accepting the values\n`observability`, `security` and `stack`.\n- Categorizes existing rule types.\n- Updates tests with the new field.\n\n## Verification steps\n\n1. Check that the rule types you own have been categorized under the\ncorrect solution\n2. Create rules in multiple areas of Kibana\n3. Check that those rules show up correctly in their UIs and work\ncorrectly\n\n## References\n\nCloses #212017","sha":"f8a3051605a5663d99253ee698d441ac32fe3868"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212079","number":212079,"mergeCommit":{"message":"[ResponseOps][Rules] Add solution field to rule types (#212079)\n\nWe need to add a `solution` field to rule types in order to provide a\nroot-level categorization based on the Kibana solution/area that owns\neach rule type. This will serve as a more reliable alternative to\nprevious attempts at `featureId`-based filtering.\n\n## Summary\n\n- Adds a `solution` field to rule type objects, accepting the values\n`observability`, `security` and `stack`.\n- Categorizes existing rule types.\n- Updates tests with the new field.\n\n## Verification steps\n\n1. Check that the rule types you own have been categorized under the\ncorrect solution\n2. Create rules in multiple areas of Kibana\n3. Check that those rules show up correctly in their UIs and work\ncorrectly\n\n## References\n\nCloses #212017","sha":"f8a3051605a5663d99253ee698d441ac32fe3868"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|---|---|---|
| .. | ||
| 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.