Export libbeat.outputs.acked_events via expvar #3411
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Part of #3422
With this PR, each Beat exports
libbeat.redis.published_and_acked_events
andlibbeat.redis.published_but_not_acked_events
via expvar for Redis.In addition,
libbeat.outputs.acked_events
is exported in order to send one metric for all outputs instead of one metric per output. In the case two outputs are enabled, the number of published events will be double.For example in case Redis and Elasticsearch outputs are enabled, then
libbeat.redis.published_and_acked_events: 48
,libbeat.elasticsearch.published_and_acked_events: 48
andlibbeat.outputs.acked_events: 96
.