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
[Stack monitoring] remove support for monitoring.cluster_alerts.allowedSpaces #123229
[Stack monitoring] remove support for monitoring.cluster_alerts.allowedSpaces #123229
Conversation
Pinging @elastic/infra-monitoring-ui (Team:Infra Monitoring UI) |
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.
Generally LGTM, commented for leadership weigh-in. I see auto-merge is off, so I'll ✅ incase it's useful for merge later.
@@ -149,7 +149,7 @@ | |||
"signature": [ | |||
"{ ui: { elasticsearch: ", | |||
"MonitoringElasticsearchConfig", | |||
"; enabled: boolean; container: Readonly<{} & { logstash: Readonly<{} & { enabled: boolean; }>; apm: Readonly<{} & { enabled: boolean; }>; elasticsearch: Readonly<{} & { enabled: boolean; }>; }>; logs: Readonly<{} & { index: string; }>; metricbeat: Readonly<{} & { index: string; }>; debug_mode: boolean; debug_log_path: string; ccs: Readonly<{} & { enabled: boolean; }>; max_bucket_size: number; min_interval_seconds: number; show_license_expiration: boolean; }; tests: Readonly<{} & { cloud_detector: Readonly<{} & { enabled: boolean; }>; }>; kibana: Readonly<{} & { collection: Readonly<{} & { interval: number; enabled: boolean; }>; }>; agent: Readonly<{} & { interval: string; }>; licensing: Readonly<{} & { api_polling_frequency: moment.Duration; }>; cluster_alerts: Readonly<{} & { enabled: boolean; allowedSpaces: string[]; email_notifications: Readonly<{} & { enabled: boolean; email_address: string; }>; }>; }" |
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.
Interesting how the field ends up in the API definition as well.
@@ -58,7 +58,6 @@ export const configSchema = schema.object({ | |||
}), | |||
}), | |||
cluster_alerts: schema.object({ | |||
allowedSpaces: schema.arrayOf(schema.string(), { defaultValue: ['default'] }), |
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.
@smith mentioned we might want to keep this as an unused/deprecated value https://github.com/elastic/kibana/blob/6693ef371f887eca639b09c4c9b15701b4ebabd4/docs/developer/architecture/core/configuration-service.asciidoc#handle-plugin-configuration-deprecations
Though I think @jasonrhodes mentioned it wasn't actively used to begin with. Maybe fine to remove it directly.
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.
Flagged the setting as unused
which sounds like a better ux
@elasticmachine merge upstream |
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.
Still LGTM
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: cc @klacabane |
💔 All backports failed
How to fixRe-run the backport manually:
Questions ?Please refer to the Backport tool documentation |
…edSpaces (elastic#123229) * remove allowed space setting * set allowedSpaces as unused setting * mock unused function in deprecation tests Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> (cherry picked from commit 24f0425) # Conflicts: # api_docs/monitoring.json
Summary
Closes #120261
Remove support for monitoring.cluster_alerts.allowedSpaces configuration setting which is used during SM alert creation.
Testing
[2022-01-24T13:54:14.101+01:00][WARN ][config.deprecation] You no longer need to configure "monitoring.cluster_alerts.allowedSpaces".