Monitoring API feature backlog

[acchen97]

Backlog for tracking potential monitoring API enhancements/fixes.

• Add basic input plugin stats (in/out/duration_in_millis) for initial 12 plugins Add basic input plugin stats to monitoring API #5769

• Add stats for Beats input

• Elasticsearch output stats, should add at least track ES response codes (200, 404, 501, etc.)

• Dissect filter - add matches/failures

• Date filter - add matches/failures

• Add # of concurrent ES bulk requests Monitoring # of concurrent bulk requests #6544

• Add persistent node ID to uniquely identify a node Persistent node ids #5646 (5.1)

• Calculate and track estimated bytes ingested (potential limitation for certain input plugins) (5.1)

• Active/current operations are not counted in duration_in_millis Metrics: Active/current operations are not counted in duration_in_millis #5683 (5.1)

[martinduris]

hi,
with this improvements -> will i be able to track how logstash is doing ?
Something like average time for message process, average amount of processed bytes, ... to detect problem with ingesting and react to it (prepare new logstash instance, optimalizations etc. ..).

(i have asked similar question here : https://discuss.elastic.co/t/logstash-5-x-monitoring-api-performance-check/68701)

Thank you very much !

EDIT : look here : #6182 ... :-)

[acchen97]

@senty yes, we have a monitoring API.

Starting with our 5.2 release, Logstash also now has a monitoring UI. Here's some documentation. Please check it out!

[acchen97]

Closing in favor of #6831.