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

Allow monitoring of operational statistics #7

Closed
tkowalcz opened this issue Nov 19, 2020 · 0 comments · Fixed by #20
Closed

Allow monitoring of operational statistics #7

tkowalcz opened this issue Nov 19, 2020 · 0 comments · Fixed by #20
Labels
core Relates to Core component

Comments

@tkowalcz
Copy link
Owner

Expose for monitoring statistics such as number of calls, errors, data size, connections stats, timing info etc.

@tkowalcz tkowalcz added the core Relates to Core component label Nov 19, 2020
tkowalcz added a commit that referenced this issue Jan 9, 2021
tkowalcz added a commit that referenced this issue Jan 9, 2021
…on and one that uses AtomicLongs for counting events and Agrona's DistinctErrorLog for storing exceptions. While various counters are being updated by other components and response times are logged we do not provide way of plugging in ones own implementation or reading the counters back (yet).
tkowalcz added a commit that referenced this issue Jan 16, 2021
…to size monitoring array. Added Netty pipeline stage for tracking number of requests in flight. Added monitoring of number of bytes of logs sent. Added thread that dumps stats to stdout.
tkowalcz added a commit that referenced this issue Jan 16, 2021
…uilder if it is > 0 (or else exception is thrown).
tkowalcz added a commit that referenced this issue Jan 22, 2021
…y code. Added closing connection if keepalive is not in force.
@tkowalcz tkowalcz linked a pull request Jan 22, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Relates to Core component
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant