[SR-Users] websocket:ws_current_connections vs. kamctl fifo ws.dump

[Luis F Urrea]

Hello

I have a question in regards monitoring websocket connections on a
production box.

We ususally trust whatever is indicated through the


$ kamctl fifo get statistics

We've seen that this is what the community contributed munin plugins use.
However when trying to monitor web socket connections and using this output
we've seen completely different results from the output of

$ kamctl fifo get_statistics

websocket:ws_current_connections

Which seem to indicate current websocket connections and the output of

$ kamctl fifo ws.dump

Which seems to indicate current OPEN connections.

Can anybody shed some light as to what are the differences between both if
any, and advice which one is the proper one to monitor for possible file
handle exhaustion.

TIA

[Luis F Urrea]

Any ideas are welcome.

I wanted to try to get input from someone familiar with the websockets
module as these statistics seem rather bogus from the comparison with
netstat connections.

Post by Luis F Urrea
Hello
I have a question in regards monitoring websocket connections on a
production box.
We ususally trust whatever is indicated through the
$ kamctl fifo get statistics
We've seen that this is what the community contributed munin plugins use.
However when trying to monitor web socket connections and using this output
we've seen completely different results from the output of
$ kamctl fifo get_statistics
websocket:ws_current_connections
Which seem to indicate current websocket connections and the output of
$ kamctl fifo ws.dump
Which seems to indicate current OPEN connections.
Can anybody shed some light as to what are the differences between both if
any, and advice which one is the proper one to monitor for possible file
handle exhaustion.
TIA

[Daniel-Constantin Mierla]

I was not checking so far the ws/wss connections, but you can probably
rely on tcp stats, because ws/wss are on top of tcp layer.

You can run the tcp-related rpc commands via kamcmd:

-
http://www.kamailio.org/docs/docbooks/4.1.x/rpc_list/rpc_list.html#core.tcp_info

Cheers,
Daniel

Post by Luis F Urrea
Any ideas are welcome.
I wanted to try to get input from someone familiar with the websockets
module as these statistics seem rather bogus from the comparison with
netstat connections.
Hello
I have a question in regards monitoring websocket connections on a
production box.
We ususally trust whatever is indicated through the
$ kamctl fifo get statistics
We've seen that this is what the community contributed munin
plugins use. However when trying to monitor web socket connections
and using this output we've seen completely different results from
the output of
$ kamctl fifo get_statistics
websocket:ws_current_connections
Which seem to indicate current websocket connections and the output of
$ kamctl fifo ws.dump
Which seems to indicate current OPEN connections.
Can anybody shed some light as to what are the differences between
both if any, and advice which one is the proper one to monitor for
possible file handle exhaustion.
TIA
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[Dunkley, Peter]

websocket:ws_current_connections says how many WebSocket connections are currently open. It is perfectly possible for Kamailio to be doing SIP over both TCP and WebSockets, so counting the number of TCP connections may not tell you how many WebSocket connections are in use as the figure can include both SIP over WebSockets (each WebSocket connection has a TCP connection) and SIP over TCP. A WebSocket connection uses more memory than a TCP connection (additional data structures stored for each connection), so it is useful to be able to know exactly how many WebSocket connections are in use.

ws.dump prints out the details of the top 50 WebSocket connections (in the internal linked list) including useful information like last used time. This is useful for developers during testing, and is not really for anyone just administering the system.


[Loading Image...]

Peter Dunkley
Technical Director

[Acision]<http://www.acision.com/>

[Loading Image...]

t

[phone]

m

[phone]

e

peter.dunkley-***@public.gmane.org<mailto:peter.dunkley-***@public.gmane.org>

[Loading Image...]

Connect with us:

[Facebook]<https://www.facebook.com/pages/Acision/145536588827195> [Twitter] <https://twitter.com/acision> [LinkedIn] <http://www.linkedin.com/company/1270?trk=tyah&trkInfo=tas%3Aacision%2Cidx%3A2-1-2> [Google+] <https://plus.google.com/+acision/posts> [YouTube] <http://www.youtube.com/user/Acision1>


________________________________

Lancaster Court, 8 Barnes Wallis Road, Segensworth East, Fareham, Hampshire PO15 5TU, UK




On 10 Sep 2014, at 19:44, Luis F Urrea <lfurrea-***@public.gmane.org<mailto:***@gmail.com>> wrote:

Any ideas are welcome.

I wanted to try to get input from someone familiar with the websockets module as these statistics seem rather bogus from the comparison with netstat connections.

On Mon, Sep 8, 2014 at 12:09 PM, Luis F Urrea <lfurrea-***@public.gmane.org<mailto:lfurrea-***@public.gmane.org>> wrote:
Hello

I have a question in regards monitoring websocket connections on a production box.

We ususally trust whatever is indicated through the


$ kamctl fifo get statistics

We've seen that this is what the community contributed munin plugins use. However when trying to monitor web socket connections and using this output we've seen completely different results from the output of

$ kamctl fifo get_statistics

websocket:ws_current_connections

Which seem to indicate current websocket connections and the output of

$ kamctl fifo ws.dump

Which seems to indicate current OPEN connections.

Can anybody shed some light as to what are the differences between both if any, and advice which one is the proper one to monitor for possible file handle exhaustion.

TIA

_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.org<mailto:sr-users-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

________________________________
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding.