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

[Security Solution] Check usages of deprecated bulk APIs to decide whether we can delete them #130963

Closed
3 tasks
Tracked by #193184
xcrzx opened this issue Apr 26, 2022 · 3 comments
Closed
3 tasks
Tracked by #193184

[Security Solution] Check usages of deprecated bulk APIs to decide whether we can delete them #130963

xcrzx opened this issue Apr 26, 2022 · 3 comments
Labels
Feature:Rule Management Security Solution Detection Rule Management area Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.

Comments

@xcrzx
Copy link
Contributor

xcrzx commented Apr 26, 2022

In 8.2, some of the detection bulk APIs were deprecated:

See #127756 for more information.

After collecting enough telemetry data on the usage of the deleted APIs (ticket for adding telemetry: #129484), we'll need to decide what to do with the deprecated endpoints. Some options could be:

  • If no one uses the deprecated endpoints, we will be able to just remove them.
  • If some users still use them but there is a replacement, we'd need to communicate and motivate those users to switch to it.
  • If some users still use them and there is no replacement, we'd need to build it and motivate those users to switch to it.
@xcrzx xcrzx added Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Feature:Rule Management Security Solution Detection Rule Management area Team:Detection Rule Management Security Detection Rule Management Team labels Apr 26, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detections-response (Team:Detections and Resp)

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@xcrzx xcrzx mentioned this issue Apr 26, 2022
Closed
9 tasks
@banderror banderror mentioned this issue Oct 31, 2023
Merged
@yctercero yctercero mentioned this issue Dec 13, 2023
Merged
@banderror
Copy link
Contributor

Usage collected and shared in https://github.com/elastic/dev/issues/2772 (internal). The endpoints are going to be removed as part of #193184.

@banderror banderror mentioned this issue Oct 23, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature:Rule Management Security Solution Detection Rule Management area Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@xcrzx @banderror @elasticmachine