-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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.
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
Alerting and action APIs to follow kibana STYLEGUIDE #59799
Labels
Feature:Alerting
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Comments
mikecote
added
Feature:Alerting
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
labels
Mar 10, 2020
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
Seems like a big hit, guessing mainly be in request/response bodies, which will then bubble down to everything else, heh. TS will help here, I'm sure. |
This issue should be broken down. By route or by layer (query, body, response, objects, etc). |
Should be done at the same time / person as #63130. |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Feature:Alerting
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Styleguide: https:/elastic/kibana/blob/master/STYLEGUIDE.md#api-endpoints
The text was updated successfully, but these errors were encountered: