There are a few issues with the current pipeline/field processing for Azure Platform Logs:
-
Missing event.kind: "pipeline_error" on Pipeline Failure
Issue: Logs are missing the event.kind: "pipeline_error" field when pipelines fail.
-
Missing azure.subscription_id in Some Logs
Issue: azure.subscription_id is missing in certain logs.
Cause: Microsoft uses the non-standard field azure.platformlogs.ResourceId instead of azure.subscription_id.
-
Inconsistent Casing for azure.subscription_id
Issue: azure.subscription_id appears in mixed cases across logs.
-
Incorrect Data Type for azure.platformlogs.durationMs
Issue: The field azure.platformlogs.durationMs contains float values, which causes processors expecting integers to fail.
There are a few issues with the current pipeline/field processing for Azure Platform Logs:
Missing event.kind: "pipeline_error" on Pipeline Failure
Issue: Logs are missing the event.kind: "pipeline_error" field when pipelines fail.
Missing azure.subscription_id in Some Logs
Issue: azure.subscription_id is missing in certain logs.
Cause: Microsoft uses the non-standard field azure.platformlogs.ResourceId instead of azure.subscription_id.
Inconsistent Casing for azure.subscription_id
Issue: azure.subscription_id appears in mixed cases across logs.
Incorrect Data Type for azure.platformlogs.durationMs
Issue: The field azure.platformlogs.durationMs contains float values, which causes processors expecting integers to fail.