Skip to content
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

Missing telemetry to help remove alerting deprecated 7.x features #108716

Closed
mikecote opened this issue Aug 16, 2021 · 6 comments
Closed

Missing telemetry to help remove alerting deprecated 7.x features #108716

mikecote opened this issue Aug 16, 2021 · 6 comments
Assignees
Labels
estimate:medium Medium Estimated Level of Effort Feature:Actions/Framework Issues related to the Actions Framework Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) telemetry Issues related to the addition of telemetry to a feature

Comments

@mikecote
Copy link
Contributor

mikecote commented Aug 16, 2021

How to collect telemetry data: https://github.com/elastic/kibana/tree/master/src/plugins/usage_collection

This issue captures additional points of data we should track to help us understand the impact of removing a feature. Some of these features are already deprecated and the telemetry will help understand when we can remove such features, while others are not deprecated yet but the data can provide better insights on how we can deprecate or remove those features.

Deprecated? Description Telemetry questions GitHub Issue
Yes, but more could be done (server log warning on usage, warning response header) Legacy alert HTTP APIs What percentage of clusters are using the legacy alert HTTP APIs? How many times per cluster? What is the breakdown by endpoint? #90383 #111894
Yes, but more could be done (server log warning on usage, warning response header) Legacy action HTTP APIs What percentage of clusters are using the legacy action HTTP APIs? How many times per cluster? What is the breakdown by endpoint? #90382 #111896
No Removing support for limiting "fields" returned by the find rules HTTP API What percentage of clusters are using the "fields" attribute on the find rules HTTP API? How many times per cluster? #70696 #112009
No, option w/ new terminology not available Renaming alert saved-object type and attributes What percentage of clusters are using our APIs with attributes using the old terminology (ex: alertTypeId instead of ruleTypeId)? How many times per cluster? What is the breakdown by attribute? #102248 and #100068
No, option w/ new terminology not available Renaming action saved-object type and attributes What percentage of clusters are using our APIs with attributes using the old terminology (ex: actionTypeId instead of actionTypeId)? How many times per cluster? What is the breakdown by attribute? #102248 and #100068
Yes Removing deprecated kibana.yml configuration settings - What percentage of clusters are using xpack.actions.whitelistedHosts?
- What percentage of clusters are using xpack.actions.customHostSettings[<index>].ssl.rejectUnauthorized?
- What percentage of clusters are using xpack.actions.rejectUnauthorized?
- What percentage of clusters are using xpack.actions.proxyRejectUnauthorizedCertificates?
- What percentage of clusters are using xpack.alerts.healthCheck?
- What percentage of clusters are using xpack.alerts.invalidateApiKeysTask.interval?
- What percentage of clusters are using xpack.alerts.invalidateApiKeysTask.removalDelay?
- What percentage of clusters are using xpack.task_manager.max_workers values with a value greater than 100?
#76385 and #100289
No, need warnings in such use case Remove legacy RBAC exemption for rule actions What percentage of clusters are using the legacy RBAC exemption for actions? How many times per cluster? https://github.com/elastic/response-ops-team/issues/250
@mikecote mikecote added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework Feature:Actions/Framework Issues related to the Actions Framework telemetry Issues related to the addition of telemetry to a feature labels Aug 16, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

@ymao1
Copy link
Contributor

ymao1 commented Aug 23, 2021

Information about how we might build and use a custom index for our specific telemetry fields in this comment.

@gmmorris gmmorris removed the loe:large Large Level of Effort label Sep 2, 2021
@chrisronline chrisronline self-assigned this Sep 9, 2021
@chrisronline
Copy link
Contributor

chrisronline commented Sep 20, 2021

Update here on adding the telemetry data to help us eventually remove these

Description Status
Legacy alert HTTP APIs #111894
Legacy action HTTP APIs #111896
Removing support for limiting "fields" returned by the find rules HTTP API #112009
Renaming alert/action saved-object type and attributes #112271
Removing deprecated kibana.yml configuration settings #112585
Remove legacy RBAC exemption for rule actions #112355

@chrisronline
Copy link
Contributor

@mikecote All telemetry are now complete for this issue. We should have all this data available soon. Can we close this out?

@gmmorris
Copy link
Contributor

gmmorris commented Oct 7, 2021

@chrisronline yup :) I'll let you have the pleasure.

@chrisronline
Copy link
Contributor

@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
estimate:medium Medium Estimated Level of Effort Feature:Actions/Framework Issues related to the Actions Framework Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) telemetry Issues related to the addition of telemetry to a feature
Projects
None yet
Development

No branches or pull requests

6 participants