-
Notifications
You must be signed in to change notification settings - Fork 69
Really hard to find the APIs you are looking for in anomaly detection section #1231
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
Comments
I transferred this issue from the Elasticsearch specification repository, as this is where all docs issues are recorded. |
@sophiec20 on #3-4, should the list be alphabetical or curated by most common APIs? I've been having a discussion with folks on how to address #1 this week. Looking into #2 (summary is being used for different things). |
@swallez for #3, how does the order of operations get determined in the JSON spec file? Bump just generates based on that order. How can we change the ordereing? Does that need to be in the TS somehow? |
@timto-elastic the order is the alphabetical order of endpoint identifiers, as can be seen in this directory. I don't think we have any other information available right now that would allow defining another stable order. We should consider adding files similar (or even identical) to the doc system's |
thanks @swallez. I like the toc.yml idea. I think there are definitely things we can do to structure the nav better. It would be great if there were a way to control that. |
https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-ml-anomaly
It's very difficult to find the APIs you need
Delete forecast
has becomeDelete forecast from a job
andGet records
has becomeGet anomaly records for an anomaly detection job
cc @valeriy42
The text was updated successfully, but these errors were encountered: