-
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
[RAM] Add new privilege for observability serverless #168034
Labels
Feature:Alerting/RulesManagement
Issues related to the Rules Management UX
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
v8.12.0
Comments
XavierM
added
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Feature:Alerting/RulesManagement
Issues related to the Rules Management UX
v8.12.0
labels
Oct 4, 2023
Pinging @elastic/response-ops (Team:ResponseOps) |
github-project-automation
bot
moved this to Awaiting Triage
in AppEx: ResponseOps - Rules & Alerts Management
Oct 10, 2023
XavierM
moved this from Awaiting Triage
to In Progress
in AppEx: ResponseOps - Rules & Alerts Management
Oct 10, 2023
1 task
XavierM
moved this from In Progress
to In Review
in AppEx: ResponseOps - Rules & Alerts Management
Oct 18, 2023
XavierM
added a commit
that referenced
this issue
Oct 31, 2023
## Summary FIX => #168034 ### Checklist - [ ] [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: mgiota <[email protected]> Co-authored-by: kibanamachine <[email protected]>
XavierM
moved this from In Review
to Done
in AppEx: ResponseOps - Rules & Alerts Management
Nov 1, 2023
delanni
pushed a commit
to delanni/kibana
that referenced
this issue
Nov 6, 2023
## Summary FIX => elastic#168034 ### Checklist - [ ] [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: mgiota <[email protected]> Co-authored-by: kibanamachine <[email protected]>
maryam-saeidi
added a commit
that referenced
this issue
Nov 10, 2023
Closes #170327 Relates to #168034 ## Summary This PR enables the custom threshold and inventory rules in Serverless. |Custom threshold rule|Inventory rule| |---|---| |![image](https://github.com/elastic/kibana/assets/12370520/35468ded-d936-4bb1-b16b-0bcfe987e0f1)|![image](https://github.com/elastic/kibana/assets/12370520/1d1a65e0-78f5-4550-a620-9342b28ec5a9)| Related PR: [Add the query delay mechanism to the inventory rule type and change consumer to Observability](#170628)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Feature:Alerting/RulesManagement
Issues related to the Rules Management UX
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
v8.12.0
In order to enable the Elasticsearch query and generic threshold to function effectively in an observability serverless project, we want to add a new Kibana feature privilege specifically tailored for observability within serverless environments. This new privilege will encompass all rule types accessible to users within the serverless project.
To ensure this observability feature is only registered in serverless projects, we intend to introduce a new configuration attribute within the observability YAML serverless config file. Consequently, when APM and SLO register their respective rule types within a serverless context, they will need to update their producer to be classified under "observability."
Our next step will involve modifying the new scope selector to exclusively utilize the observability feature and it will be hidden from our users' view. This adjustment will be guided by an API that informs us about the feature access associated with our rule types, providing us with the necessary insights to fine-tune our scope settings accordingly.
The text was updated successfully, but these errors were encountered: