when tracing is enabled, log the actual json request

[sporty81]

Was just logging "byte[]" which was no help. This way we can see the command sent to ES. Still doesn't log the response the way it should. Someone need to fix that as well. right now it says "Response stream not captured or already read to completion by serializer" every time for me.

[Mpdreamz]

Hi @sporty81

Thanks for this! Can you sign the Elasticsearch CLA so i can pull your bits in?

http://www.elasticsearch.org/contributor-agreement/

[sporty81]

OK I filled it out. By the way, in case I do future PRs, are they supposed to be done on a certain branch? Thanks!

[Mpdreamz]

I try to do big issues/new features in feature/* branches.

I am very lenient when it comes to PR's though, whatever works for you works for me.

I will in the future introduce a stricter git flow workflow for myself but I'm not to worried about where the PR comes from as long as they are opened against the current develop branch (now master might change to develop in the future).

Thanks for signing 👍

[Mpdreamz]

The only thing I recommend is the EditorConfig visual studio plugin:

http://visualstudiogallery.msdn.microsoft.com/c8bccfe2-650c-4b42-bc5c-845e21f96328

To synchronize indentation and line endings settings per project.