-
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
[Serverless Search] Remove unwanted alterting rule and connector types #162105
[Serverless Search] Remove unwanted alterting rule and connector types #162105
Conversation
Pinging @elastic/uptime (Team:uptime) |
Could you (if not done already) check with each team owning those individual plugins that the config changes done in this PR is fine with them? |
I'm checking with the teams whose configs I changed (uptime, monitoring and infra). Disabling Observability and SecuritySolution plugins in Serverless Search doesn't need that check, it's aligned with the product direction for Serverless Search. Users wanting to use Observability or SecuritySolution in Serverless should spin up a Serverless Observability or Serverless Security project instead of a Serverless Search one. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@elasticmachine merge upstream |
merge conflict between base and head |
💚 Build Succeeded
Metrics [docs]Public APIs missing comments
Page load bundle
History
To update your PR or re-run it, just comment with: |
@@ -14,6 +14,7 @@ export interface InfraConfig { | |||
group_by_page_size: number; | |||
}; | |||
}; | |||
enabled: boolean; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this flag need to be exposed to the client public config for any reason or is it only necessary server side?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It’s only necessary on the server side, Kibana will pick it up and skip initializing the entire plug-in (server and client).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
infra config LGTM!
elastic#162105) ## Summary This moves alerting in Serverless Search to the Stack Management alerting page, and removes To remove these rule types, I had to disable the observability, securitySolution, uptime, monitoring and infra plugins and make sure that their server plugins (not just the frontend plugins) respected the `enabled: false` flag.
Summary
This moves alerting in Serverless Search to the Stack Management alerting page, and removes
To remove these rule types, I had to disable the observability, securitySolution, uptime, monitoring and infra plugins and make sure that their server plugins (not just the frontend plugins) respected the
enabled: false
flag.