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

Deprecate the alert HTTP APIs #90379

Closed
mikecote opened this issue Feb 5, 2021 · 5 comments
Closed

Deprecate the alert HTTP APIs #90379

mikecote opened this issue Feb 5, 2021 · 5 comments
Assignees
@ymao1
Labels
Feature:Alerting Project:UnifiedAlertingArchitectureAndExperience Alerting team project for developing a unified alerting experience. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@mikecote
Copy link
Contributor

mikecote commented Feb 5, 2021 •
edited
Loading

This is the second step of #90375. We should deprecate the alert HTTP APIs that use the old terminology and request solution/application teams to switch over to the new APIs by 7.last. Don't forget docs and release notes.

For details on the introduction of the terminology see notes under #90375 (comment)
@mikecote mikecote added blocked Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Project:UnifiedAlertingArchitectureAndExperience Alerting team project for developing a unified alerting experience. labels Feb 5, 2021
@elasticmachine
Copy link
Contributor

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

This was referenced Feb 5, 2021
Open
Closed
Open
@YulNaumenko YulNaumenko self-assigned this Mar 8, 2021
@YulNaumenko YulNaumenko removed their assignment Mar 9, 2021
@dhurley14 dhurley14 mentioned this issue Mar 22, 2021
Open
@mikecote mikecote removed the blocked label Mar 30, 2021
@ymao1 ymao1 self-assigned this Mar 30, 2021
@ymao1
Copy link
Contributor

ymao1 commented Mar 30, 2021

Similar to the deprecate actions HTTP APIs issue, this issue is to contact the teams using the deprecated alert HTTP APIs to ask them to migrate by 7.last. The actual deprecation and docs was done in this issue

@ymao1
Copy link
Contributor

ymao1 commented Mar 30, 2021

Usages of /api/alerts/... within the codebase

  • x-pack/plugins/observability/public/services/get_observability_alerts.ts
  • x-pack/plugins/security_solution/server/lib/detection_engine/scripts/get_alert_instances.sh
  • x-pack/plugins/security_solution/server/lib/detection_engine/scripts/get_alert_types.sh
  • x-pack/plugins/uptime/common/constants/rest_api.ts

@ymao1
Copy link
Contributor

ymao1 commented Mar 31, 2021

Opened issues for Uptime and Security:

@ymao1
Copy link
Contributor

ymao1 commented Apr 2, 2021

Closing this issue as the APIs are officially marked as deprecated and two follow up issues have been opened for Security Solutions & Uptime

@ymao1 ymao1 closed this as completed Apr 2, 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

@ymao1 ymao1

Labels
Feature:Alerting Project:UnifiedAlertingArchitectureAndExperience Alerting team project for developing a unified alerting experience. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@kobelb @mikecote @ymao1 @elasticmachine @YulNaumenko