<div dir="ltr">Hi all,<div><br></div><div>I believe we&#39;ve identified a limitation in the values returned by the /api/connections interface, and was looking to see if anyone else can confirm this behavior.</div><div><br>
</div><div>It appears that when any field returned in the API request to /api/connections reaches approximately 4294967296 (2^32), the statistics counter is dramatically reset, affecting the integrity of counter data in the next request.</div>
<div><br></div><div>For example, see this selected subset of response for two sequential requests to /api/connections:</div><div><br></div><div>{&quot;recv_oct&quot;:4294345813,&quot;recv_cnt&quot;:134449509,&quot;send_oct&quot;:525608688,&quot;send_cnt&quot;:43620989,&quot;send_pend&quot;:0,&quot;state&quot;:&quot;running&quot;,&quot;last_blocked_by&quot;:&quot;none&quot;,&quot;last_blocked_age&quot;:&quot;infinity&quot;,&quot;channels&quot;:1,&quot;recv_oct_details&quot;:{&quot;rate&quot;:161293.3401346077,&quot;interval&quot;:5002984,&quot;last_event&quot;:1377291327321},&quot;send_oct_details&quot;:{&quot;rate&quot;:2854.2965558154897,&quot;interval&quot;:5002984,&quot;last_event&quot;:1377291327321},&quot;type&quot;:&quot;network&quot;,&quot;node&quot;:&quot;rabbit@localhost&quot;,&quot;name&quot;:&quot;<a href="http://10.123.123.50:28676">10.123.123.50:28676</a> -&gt; <a href="http://10.123.123.50:5672">10.123.123.50:5672</a>&quot;,&quot;address&quot;:&quot;10.123.123.50&quot;,&quot;port&quot;:5672,&quot;peer_address&quot;:&quot;10.123.123.50&quot;,&quot;peer_port&quot;:28676,&quot;ssl&quot;:false,&quot;peer_cert_subject&quot;:&quot;&quot;,&quot;peer_cert_issuer&quot;:&quot;&quot;,&quot;peer_cert_validity&quot;:&quot;&quot;,&quot;auth_mechanism&quot;:&quot;PLAIN&quot;,&quot;ssl_protocol&quot;:&quot;&quot;,&quot;ssl_key_exchange&quot;:&quot;&quot;,&quot;ssl_cipher&quot;:&quot;&quot;,&quot;ssl_hash&quot;:&quot;&quot;,&quot;protocol&quot;:&quot;AMQP 0-9-1&quot;,&quot;user&quot;:&quot;webservice&quot;,&quot;vhost&quot;:&quot;webservice&quot;,&quot;timeout&quot;:10,&quot;frame_max&quot;:131072,&quot;client_properties&quot;:{}}<br>
</div><div><br></div><div>{&quot;recv_oct&quot;:14977,&quot;recv_cnt&quot;:134453219,&quot;send_oct&quot;:525623280,&quot;send_cnt&quot;:43622201,&quot;send_pend&quot;:0,&quot;state&quot;:&quot;running&quot;,&quot;last_blocked_by&quot;:&quot;none&quot;,&quot;last_blocked_age&quot;:&quot;infinity&quot;,&quot;channels&quot;:1,&quot;recv_oct_details&quot;:{&quot;rate&quot;:-858689105.5064446,&quot;interval&quot;:5001031,&quot;last_event&quot;:1377291332322},&quot;send_oct_details&quot;:{&quot;rate&quot;:2917.798349980234,&quot;interval&quot;:5001031,&quot;last_event&quot;:1377291332322},&quot;type&quot;:&quot;network&quot;,&quot;node&quot;:&quot;rabbit@localhost&quot;,&quot;name&quot;:&quot;<a href="http://10.123.123.50:28676">10.123.123.50:28676</a> -&gt; <a href="http://10.123.123.50:5672">10.123.123.50:5672</a>&quot;,&quot;address&quot;:&quot;10.123.123.50&quot;,&quot;port&quot;:5672,&quot;peer_address&quot;:&quot;10.123.123.50&quot;,&quot;peer_port&quot;:28676,&quot;ssl&quot;:false,&quot;peer_cert_subject&quot;:&quot;&quot;,&quot;peer_cert_issuer&quot;:&quot;&quot;,&quot;peer_cert_validity&quot;:&quot;&quot;,&quot;auth_mechanism&quot;:&quot;PLAIN&quot;,&quot;ssl_protocol&quot;:&quot;&quot;,&quot;ssl_key_exchange&quot;:&quot;&quot;,&quot;ssl_cipher&quot;:&quot;&quot;,&quot;ssl_hash&quot;:&quot;&quot;,&quot;protocol&quot;:&quot;AMQP 0-9-1&quot;,&quot;user&quot;:&quot;webservice&quot;,&quot;vhost&quot;:&quot;webservice&quot;,&quot;timeout&quot;:10,&quot;frame_max&quot;:131072,&quot;client_properties&quot;:{}}</div>
<div><br></div><div>The recv_oct counter reaches approximately 4294967296 between the first and second requests, causing it to reset for the second request. This also causes the recv rate to report an incorrect value. We&#39;re unsure if this is a more widespread issue at this time.</div>
<div><br></div><div>Please let me know if additional information is required to reproduce this behavior.</div><div><br></div><div>Thanks,</div><div>Dustin Doiron<br>Weebly.com</div></div>