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

[BACKPORT] Send TCP metrics for bytes sent and received to server #500

Merged
merged 2 commits into from
Oct 14, 2021

Conversation

mdumandag
Copy link
Contributor

It would be good to send tcp.bytesReceived and tcp.bytesSend
metrics in the metrics blob to the server, so that, someone can
track how much traffic is passing between the server and the client.

I have manually tested the stats exported to Prometheus and verified
that these two new stats are displayed there correctly.

It would be good to send `tcp.bytesReceived` and `tcp.bytesSend`
metrics in the metrics blob to the server, so that, someone can
track how much traffic is passing between the server and the client.

I have manually tested the stats exported to Prometheus and verified
that these two new stats are displayed there correctly.
@codecov-commenter
Copy link

Codecov Report

Merging #500 (b4cddfb) into 5.0.z (ac57ce7) will decrease coverage by 0.35%.
The diff coverage is 81.81%.

Impacted file tree graph

@@            Coverage Diff             @@
##            5.0.z     #500      +/-   ##
==========================================
- Coverage   95.22%   94.87%   -0.36%     
==========================================
  Files         346      346              
  Lines       17680    17696      +16     
==========================================
- Hits        16836    16789      -47     
- Misses        844      907      +63     
Impacted Files Coverage Δ
hazelcast/statistics.py 90.44% <69.23%> (-0.57%) ⬇️
hazelcast/reactor.py 82.01% <100.00%> (-8.04%) ⬇️
...otocol/codec/client_authentication_custom_codec.py 50.00% <0.00%> (-23.81%) ⬇️
hazelcast/listener.py 91.30% <0.00%> (-1.87%) ⬇️
hazelcast/protocol/client_message.py 93.52% <0.00%> (-1.77%) ⬇️
hazelcast/connection.py 91.88% <0.00%> (-1.42%) ⬇️
hazelcast/invocation.py 94.63% <0.00%> (-0.77%) ⬇️
hazelcast/proxy/base.py 97.40% <0.00%> (-0.65%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ac57ce7...b4cddfb. Read the comment docs.

Comment on lines +6 to +10
- '[45].*.z'
pull_request:
branches:
- master
- 4.*.z
- '[45].*.z'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it matter to change this? I think the one in master might be the only file that matters.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, it is using the workflow files in this branch AFAIK

@mdumandag mdumandag merged commit b012a97 into hazelcast:5.0.z Oct 14, 2021
@mdumandag mdumandag deleted the tcp-metrics-5.0.z branch October 14, 2021 10:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants