Open dannyamaya opened 2 months ago
Pinging code owners for receiver/azureeventhub: @atoulme @cparkins. See Adding Labels via Comments if you do not have permissions to add labels yourself.
@cparkins could we ingest the data point without setting the start timestamp?
@atoulme I think this issue may actually be a type mismatch.
@dannyamaya When specifying the Diagnostic Settings for Databricks are there options under 'Metrics' or only 'Logs'?
According to the documentation only Logs are available: https://learn.microsoft.com/en-us/azure/azure-monitor/reference/supported-metrics/metrics-index
Also when I looked I could only see 'Logs'. If this is truly logs data attaching the Event Hub to a log receiver should resolve the issue as it does not require a time grain.
Yes, you're right Databricks can't support metrics by the date of this post so that's probably why otel can't handle those messages and shows that error, my bad, thanks for clarifying.
No worries, it's probably not exactly clear that the mapping is done by the pipeline data type from the documentation. But that is how I wrote it to work.
Describe the bug Messages from databricks sent through Event Hubs doesn't has the Time Grain value, you get this error for every new message.
Steps to reproduce Activate the diagnostic tool for Databricks connect it to a eventhub and then to an Otel instance.
What did you expect to see? Message should arrive with no problem, time grain parameter should be optional with a default value.
What did you see instead?
What version did you use? Latest Otel.
What config did you use?
Environment Azure App service running Otel with Latest Otel Version.
Additional context I already tried running Otel in pure Linux & Kubernetes.