Skip to content

Migrate Security Solutions to new Alerting APIs #95842

Open

Description

As part of the effort to update the Alerting terminology, the Alerting team has created new HTTP APIs using the rules terminology and deprecated the existing HTTP APIs that reference alerts.

The new APIs are documented here: https://www.elastic.co/guide/en/kibana/master/alerting-apis.html
The deprecated APIs are documented here: https://www.elastic.co/guide/en/kibana/master/alerts-api.html and will remain until 8.0 when they will be removed.

This issue is to remove usage of the legacy APIs from Security Solutions.
Note that in addition to route changes, API parameters have also been converted to snake case to conform to the style guide

Note, it doesn't look like security solutions is using the HTTP APIs inside the plugin, but there are two scripts that currently call the legacy API:

  • 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    Team: SecuritySolutionSecurity Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.Team:SIEMv8.0.0

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions