Skip to content
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

Additions to the Monitoring API #7621

Closed
7 of 10 tasks
acchen97 opened this issue Jul 8, 2017 · 4 comments
Closed
7 of 10 tasks

Additions to the Monitoring API #7621

acchen97 opened this issue Jul 8, 2017 · 4 comments

Comments

@acchen97
Copy link
Contributor

acchen97 commented Jul 8, 2017

Next round of per plugin stats for the monitoring API:

Elasticsearch output metrics example payload:

{
  "bulk_requests": {
     "responses": {  # counts per top level status code returned in the bulk response
       200: 346300,
       201: 712,
       404: 61,
       429: 36
       # other status codes ...
     },
     "successes": 346819,  # successful bulk requests with no errors (sum of 200 and 201 minus partial_successes)
     "failures": 23,         # no http response from ES. will be retried. see point 1 above for causes
     "partial_successes": 134,  # bulk request successful (status 20X) but contains errors
     "drops": 5,   # bulk request dropped
  },
  "documents": {
       "successes": 173409500,
       "retryable_failures": 450,
       "non_retryable_failures": 12
  },
  "sniffing_count": 621
}
@pemontto
Copy link

pemontto commented Jul 9, 2017

I would really like to see something like 1, 5 and 15 log rate per second. Currently I have to query multiple times and store the number of processed logs to calculate the rate over time. Unless I'm missing something entirely.

@acchen97
Copy link
Contributor Author

@pemontto have you checked out the Logstash Monitoring UI? It's an X-Pack feature, but under the Basic license so therefore free to all users alike.

https://www.elastic.co/guide/en/x-pack/current/monitoring-logstash.html

@suyograo suyograo removed the api label Sep 14, 2017
@jsvd
Copy link
Member

jsvd commented Jan 15, 2018

I'm adding here an entry to desirable metrics for the http output: logstash-plugins/logstash-output-http#82

@jsvd
Copy link
Member

jsvd commented May 4, 2018

beats input already provides a count for concurrent and peak connection counts, the only thing missing is the count per beat type, which required extra metadata in the lumberjack protocol, so closing this, want we can reopen an issue on the beats input repo for a specific requirement.

@jsvd jsvd closed this as completed May 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants