[EXPORTER] Add HttpHeaders in ElasticsearchLogRecordExporter #3083
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #3080
When using the
ElasticsearchLogRecordExporter
we might need to add some http headers (auth or other required headers by our server). As of today there was no way of doing it for this exporter.This PR aims to add this feature.
Changes
Like for the HttpLogRecordExporter, add the possibility to give custom http headers that will be added to each request. This is done by adding a
std::multimap
in which headers are added and then parsed when the request is being sent.