Migrate Uptime to new Alerting APIs

[ymao1]

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 Uptime.
Note that in addition to route changes, API parameters have also been converted to snake case to conform to the style guide

[elasticmachine]

Pinging @elastic/uptime (Team:uptime)

[elasticmachine]

Pinging @elastic/apm-ui (Team:apm)

[mikecote]

We will need this done, merged and backported before 7.15.0 feature freeze so we can remove the code in the 7.16/8.0 release cycle.

[dominiqueclarke]

We are using 3 soon to be deprecated apis. The routes are defined in x-pack/plugins/uptime/common/constants/rest_api.ts and used in x-pack/plugins/uptime/public/state/api/alerts.ts.

POST /api/alerts/alert
DELETE /api/alerts/alert/{id}
GET /api/alerts/_find

We will need to update them according to the specs laid out in #90377

• POST /api/alerts/alert => /api/alerting/rule
• GET /api/alerts/_find => /api/alerting/rules/_find
• DELETE /api/alerts/alert/{id} => /api/alerting/rule/{id}

[dominiqueclarke]

@mikecote Do you have new Rule types defined for the new snake case rule parameters. I see the Alert type at x-pack/plugins/alerting/common/alert.ts, but I can't find a corresponding new type for the new terminology and schema.

[mikecote]

@dominiqueclarke

@mikecote Do you have new Rule types defined for the new snake case rule parameters. I see the Alert type at x-pack/plugins/alerting/common/alert.ts, but I can't find a corresponding new type for the new terminology and schema.

Not at this time, our first pass at the terminology change was to rename anything user-facing and breaking (like HTTP APIs). The renaming in the code will happen at a future time and most likely be done all at once as a search and replace. You can keep using AlertType TS definitions for now 👍