-
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
[Alerting] Deprecated config telemetry #112609
[Alerting] Deprecated config telemetry #112609
Conversation
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
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.
code LGTM, but I added a comment about using the old and new allowHosts settings in a config and not getting a warning about it - feels like something we should do unless I'm misunderstanding something
It looks like |
424cc3d
to
eb12721
Compare
@ymao1 Great point, I'll fix that up |
@Bamieh Would you mind looking at the implementation of this and letting me know if you think it'll work on the telemetry side of things? |
@@ -54,10 +55,61 @@ export { ACTION_SAVED_OBJECT_TYPE } from './constants/saved_objects'; | |||
|
|||
export const plugin = (initContext: PluginInitializerContext) => new ActionsPlugin(initContext); | |||
|
|||
// Use a custom copy function here so we can perserve the telemetry provided for the deprecated config | |||
// See https://github.com/elastic/kibana/issues/112585#issuecomment-923715363 | |||
function renameFromRootAndTrackDeprecatedUsage( |
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.
I dont believe this is needed. please let me know if this comment makes sense: #112585 (comment)
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.
Thanks for this clarification!
After syncing with @Bamieh in #112609 (comment), I think what we need here can be accomplished with much less code. I'm going to close this out and reopen a new PR with the changes necessary. |
💔 Build Failed
Failed CI StepsTest FailuresKibana Pipeline / jest / Jest Tests.x-pack/plugins/alerting/server.config validation alerting defaultsStandard Out
Stack Trace
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
Resolves #112585
This adds usage telemetry for:
xpack.actions.whitelistedHosts
(We had to slightly refactor how this deprecation worked as a result of [Alerting] Add telemetry for config deprecation #112585 (comment))xpack.actions.rejectUnauthorized
xpack.actions.proxyRejectUnauthorizedCertificates
xpack.alerts.healthCheck
xpack.alerts.invalidateApiKeysTask.interval
xpack.alerts.invalidateApiKeysTask.removalDelay
xpack.task_manager.max_workers
To test, add these configs to your kibana.yml, then hit the stats HTTP API (
https://localhost:5601/api/stats?extended
), and look forkibana_config_usage
key, such as:(kibana.yml for the above)