-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Add docs for monitoring API changes in Alpha4 #5553
Conversation
GET /_node/stats/pipeline | ||
-------------------------------------------------- | ||
|
||
//REVIEWERS: Note that when you call /_node/stats, it does not return the pipeline stats. You need to specify /_node/stats/pipeline specifically. This makes me wonder if it shouldn't be its own API topic. WDYT? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is intentional. /_node/stats/pipeline
is too verbose (customers have complex plugin configs) to be included in /_node/stats
. Yes it should be a separate API topic.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed. Made this a separate topic called Pipeline Info API.
@dedemorton I added some comments |
174e985
to
d9065d1
Compare
@suyograo I've made the changes that you suggested and retested the REST calls. Let me know if this is ready to merge. |
LGTM |
@jordansissel @andrewvc @suyograo Not sure who needs to review this, but here you go! Please read and respond to the questions that I've added as comments flagged for REVIEWERS. There were a few places where the API calls didn't behave exactly as described in #5475.
This adds changes for monitoring APIs (tracked by doc issue #5148).