Now, you could build all kinds of logging in to your server (you should probably be doing that anyway!), but it’s often a very iterative, time consuming process to arrive at exactly what kind of logging you need. The first step to seeing what’s going on is to understand what the player is asking for from the cloud queue server, and what the server is telling it. You fire up the cloud queue (CQ) server, point loadCloudQueue at it, and… nothing. You’ve got your contexts and queue versions all set up. Yes! There is nothing better than one to really understand.You’ve read our documentation and built a fantastic cloud queue implementation. After the filter was applied, all packets related to that transaction were filtered and it was possible to the application response times. At the time it was the number identifying the customer. udp contains “string” or tcp contains “texto” : by now you already know…Īrmed with the knowledge of these filters, all that was needed was some kind of reference.ip contains “string”: searches for the string in the content of any IP packet, regardless of the transport protocol.frame contains “string”: searches for a string in all the frame content, independently of being IP, IPv6, UDP, TCP or any other protocol above layer 2.The “contains” operator can be used to find text strings or hexadecimal characters directly with the name of the protocol instead of specific filters like http.host or.

In the middle of so many transactions and a working store, how to find the TCP conection that has the transaction to troubleshoot? The solution The application was developed in-house, didn’t use any of the known application protocols like HTTP or FTP and wasn’t encrypted. Recently, I had to look at a problem of a sales application where users reported that “the network was slow”. While most people think of it at the end of the fight, with me it’s always on top of the list.

Wireshark is my tool of choice for troubleshooting.

Wireshark http address