[Azure Blob Storage] Gunzip data that has magic header #526
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.
What does this PR do?
Gunzip data of
blobContent
from Azure Blob storage when it has magic header0x1f 0x8b
.Motivation
Currently gzip files in Blob storage are transferred to Datadog as they are and result in garbled logs.
This PR gunzip those files before sending.
Testing Guidelines
Upload the gzipped files to the blob storage and confirm in Datadog Logs whether they are gunzipped.
Additional Notes
Magic header idea is taken from the following
datadog-serverless-functions/aws/logs_monitoring/parsing.py
Lines 185 to 190 in 327bfa6
Types of changes
Check all that apply