WARNING: Version 5.x has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
A web debugging proxy such as Fiddler is a useful way to capture HTTP traffic from a machine, particularly whilst developing against a local Elasticsearch cluster.
To capture traffic against a remote cluster is as simple as launching Fiddler! You may want to also filter traffic to only show requests to the remote cluster by using the filters tab
The .NET Framework is hardcoded not to send requests for
localhost through any proxies and as a proxy
Fiddler will not receive such traffic.
This is easily circumvented by using
ipv4.fiddler as the hostname instead of
With Fiddler running, the requests and responses will now be captured and can be inspected in the Inspectors tab
As before, you may also want to filter traffic to only show requests to
ipv4.fiddler on the port
on which you are running Elasticsearch.