Log problems communicating with Elasticsearch

[esnible]

Signed-off-by: Ed Snible snible@us.ibm.com

Log problems talking to ElasticSearch.

Inspired by #3443

In the case tested, Jaeger v3 API returns a 500 error to the client with no log for the maintainers. A server shouldn't return a 500 error, thus it is worth logging when we do.

I considered adding logic to deal with #3443 by validating the request and not sending it to ElasticSearch, but I am not ready to do that. I will follow up on the Issue.

[codecov]

Codecov Report

Merging #3451 (da94fe6) into main (5ea0544) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #3451      +/-   ##
==========================================
- Coverage   96.47%   96.45%   -0.02%     
==========================================
  Files         262      262              
  Lines       15307    15308       +1     
==========================================
- Hits        14768    14766       -2     
- Misses        456      458       +2     
- Partials       83       84       +1     

Impacted Files	Coverage Δ
plugin/storage/es/spanstore/reader.go	100.00% <100.00%> (ø)
cmd/query/app/static_handler.go	95.80% <0.00%> (-1.80%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5ea0544...da94fe6. Read the comment docs.