Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am trying to understand CouchDB network traffic with Wireshark and find it very difficult.

A simple transaction with plain-text content seems to result in many lines in Wireshark, most of them being not more than unparsed binary data:

44270 > terabase [PSH ACK] Seq=1411 Ack=2369 Win=16195 Len=27 [...]

Packet data is decoded up to the TCP level, but not at the CouchDB level.

Is there any Wireshark plugin to understand CouchDB traffic ?

share|improve this question
up vote 3 down vote accepted

CouchDB traffic is just HTTP traffic to a JSON API; even if Wireshark doesn't catch the fact that it's HTTP, the traffic should still be really quite readable.

A TCP ACK packet (the one pasted in your question) is never going to be terribly enlightening, though; you're interested in the data within the TCP connection. Try right-clicking one of the packets and "Follow TCP stream" - a window will come up with all of the data from the connection, color-coded by request and response.

share|improve this answer
+1. What I do is go into the Wireshark config in the http protocol, and add 5984 in the list of ports. Then Wireshark will provide further parsing, showing HTTP verbs, responses, etc. – jhs Feb 7 '12 at 11:00
Nice! jhs' comment would be an acceptable answer too. – Nicolas Raoul Feb 8 '12 at 5:43

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.