[receiver/azureblobreceiver] Support Azure VNET flow logs

[rafaelrodrigues3092]

Component(s)

receiver/azureblob

Is your feature request related to a problem? Please describe.

Azure has a feature to export Azure VNET flow logs to Azure Storage Account (blob).
The data is appended to an "hourly" file, and every hour a new file is created.
The data is in json, but it's not Otel formatted. As such, a translator layer would be needed.

More information on the format of the data here: https://learn.microsoft.com/en-us/azure/network-watcher/vnet-flow-logs-overview?tabs=Americas#sample-log-record

Describe the solution you'd like

Similar to how encoding is used in some other receivers (like kafkareceiver for example), it would be helpful to see an identical solution where different types encodings are supported.

Example of a similar request that would implement identical solution: #39623

Describe alternatives you've considered

Custom application that translates the Azure VNET flow logs to otel-compatible encoding.

Additional context

No response

[github-actions]

Pinging code owners:

• receiver/azureblob: @eedorenko @mx-psi

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[axw]

Sounds sensible to me. Does this rather belong to https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/pkg/translator/azurelogs?

[rafaelrodrigues3092]

Sounds sensible to me. Does this rather belong to https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/pkg/translator/azurelogs?

@axw yes, it should be an azure log translator for sure, but I believe work on the receiver would also be needed to support it?

Thanks

[axw]

/label -needs-triage waiting-for-code-owners

Yes you're right, the receiver is currently hardcoded to decode OTLP/JSON only, so work would be needed there too.

[axw]

/label pkg/translator/azurelogs