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.

Sign up for GitHub

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

Jump to bottom

[Alerting] Add telemetry for HTTP API calls with legacy terminology #112271

Closed
chrisronline opened this issue Sep 15, 2021 · 1 comment · Fixed by #112173
Closed

[Alerting] Add telemetry for HTTP API calls with legacy terminology #112271

chrisronline opened this issue Sep 15, 2021 · 1 comment · Fixed by #112173
Assignees
@chrisronline
Labels
estimate:small Small Estimated Level of Effort 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
Kibana Alerting

Comments

@chrisronline
Copy link
Contributor

chrisronline commented Sep 15, 2021 •
edited
Loading

We need to answer the following questions for both alerting APIs:

  • 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?
@chrisronline chrisronline 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 Sep 15, 2021
@elasticmachine
Copy link
Contributor

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

@chrisronline chrisronline self-assigned this Sep 15, 2021
@chrisronline chrisronline added this to In Progress in Kibana Alerting Sep 15, 2021
@chrisronline chrisronline mentioned this issue Sep 15, 2021
Merged
@chrisronline chrisronline changed the title [Alerting] [Actions] Add telemetry for HTTP API calls with legacy terminology [Alerting] Add telemetry for HTTP API calls with legacy terminology Sep 15, 2021
@chrisronline chrisronline removed the Feature:Actions/Framework Issues related to the Actions Framework label Sep 15, 2021
@chrisronline chrisronline moved this from In Progress to In Review in Kibana Alerting Sep 15, 2021
@chrisronline chrisronline added Feature:Actions/Framework Issues related to the Actions Framework and removed Feature:Actions/Framework Issues related to the Actions Framework labels Sep 16, 2021
@chrisronline chrisronline mentioned this issue Sep 20, 2021
Closed
Kibana Alerting automation moved this from In Review to Done (Ordered by most recent) Sep 20, 2021
@gmmorris gmmorris added the estimate:small Small Estimated Level of Effort label Oct 4, 2021
@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
Assignees

@chrisronline chrisronline

Labels
estimate:small Small Estimated Level of Effort 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
No open projects
Kibana Alerting
Done (Ordered by most recent)
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Alerting] Add telemetry for HTTP API calls with legacy terminology chrisronline/kibana
4 participants
@chrisronline @gmmorris @kobelb @elasticmachine