When sending a support ticket, it is good to include as much information about the issue as you can. The following article describes what can be sent along with the issue description to let us better understand your problem.
Server and client version
Web Traffic logs. We recommend using a FiddlerCap recorder which will create a SAZ file that we can analyze further:
Close all instances of Internet Explorer (or other browsers)
Run the FiddlerCapSetup.exe file
FiddlerCap will start automatically when the installer completes
Inside FiddlerCap press Clear Cookies button and then the Clear Cache button
Inside FiddlerCap, click the 1. Start Capture button
Record web traffic using your application
To add a screenshot to your capture, press the +Screenshot button inside FiddlerCap
Inside FiddlerCap, click the 2. Stop Capture button
Click the 3. Save Capture button. Save the .SAZ file to your desktop
Debug Info Package. RavenDB supports creating an info package (replication, performance, i/o, storage, memory, etc.) that can be created for the entire cluster or for the current server only. Go to Studio -> Manage Server -> Gather Debug Info
The easiest way to monitor traffic sent to http://localhost or http://127.0.0.1 is to provide a machine name instead of localhost or 127.0.0.1.
For example, if your RavenDB server address is http://localhost:8080, then in an application config file change it to http://[machine-name]:8080. You can also use one of these two aliases instead: http://ipv4.fiddler, http://localhost.fiddler.
For an ASP.NET application you can also configure the proxy server as follows: