[receiver/azureeventhub] Better handling of timestamp parsing

[tesharp]

Component(s)

receiver/azureeventhub

What happened?

Description

Trying to use the azureventhub receiver to read diagnostic logs from Azure but its receiving a lot of timestamp parsing errors. It seems like the diagnostic records in event hub are either missing timestamp or have a different format in some cases. Would be good with some better handling, for instance option to ignore and set current time.

Steps to Reproduce

Set up diagnostic logs and send to event hub

Expected Result

Able to parse all logs

Actual Result

Many many error message with Invalid timestamp

Collector version

v0.85.0

Environment information

Environment

OS: Ubuntu 20.04

OpenTelemetry Collector configuration

receivers:
  azureeventhub:
    connection: $CONNECTION_STRING
    format: "azure"
    storage: file_storage/logs

Log output

azureeventhubreceiver@v0.85.0/azureresourcelogs_unmarshaler.go:106      Invalid Timestamp       {"kind": "receiver", "name": "azureeventhub", "data_type": "logs", "time": ""}
azureeventhubreceiver@v0.85.0/azureresourcelogs_unmarshaler.go:106      Invalid Timestamp       {"kind": "receiver", "name": "azureeventhub", "data_type": "logs", "time": "10/10/2023 13:26:34"}

Additional context

No response

[github-actions]

Pinging code owners:

• receiver/azureeventhub: @atoulme @djaglowski

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

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• receiver/azureeventhub: @atoulme @djaglowski

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

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• receiver/azureeventhub: @atoulme @djaglowski

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

[nslaughter]

I just noticed this, because I needed to use this receiver. I will look it up and see if we should copy the parser used in Azure's SDK or import it. Our code currently uses ISO8601, whereas they use RFC3339 and explicitly allow for a further variation with the T or Z.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• receiver/azureeventhub: @atoulme @djaglowski @cparkins

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

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.

[atoulme]

@nslaughter are you interested in fixing this issue?

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• receiver/azureeventhub: @atoulme @cparkins

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