Marginally clarify workaround comments

zmoog · zmoog · commit d0a08b4f7a85 · 2025-09-09T13:12:11.000+02:00
diff --git a/packages/azure/data_stream/events/elasticsearch/ingest_pipeline/default.yml b/packages/azure/data_stream/events/elasticsearch/ingest_pipeline/default.yml
@@ -44,10 +44,11 @@ processors:
       if: 'ctx.tmp_json?.category == null'
       ignore_missing: true
       description: 'Rename the invalid `Category` field to `category` to apply the correct routing rules.'
-  # Unfortunately, some Azure services produce logs with `CategoryValue` field
-  # instead of `Category` field.
+  # Unfortunately, some Azure services generate logs with
+  # `CategoryValue` field instead of `Category` field.
   #
-  # We need to rename it to `category` to apply the correct routing rules.
+  # We need to rename `CategoryValue` as `category` to
+  # apply the correct routing rules.
   # 
   # Refs;
   # - https://github.com/elastic/integrations/issues/15083
diff --git a/packages/azure/data_stream/signinlogs/elasticsearch/ingest_pipeline/default.yml b/packages/azure/data_stream/signinlogs/elasticsearch/ingest_pipeline/default.yml
@@ -46,6 +46,14 @@ processors:
   - drop:
       description: Drop non-SignInLogs.
       if: ctx.azure?.signinlogs?.category == null || !ctx.azure.signinlogs.category.endsWith('SignInLogs')
+    # Unfortunately, some Azure services generate logs with
+    # `created_date_time` field instead of `time` field.
+    #
+    # We need to rename `created_date_time` as `time` to
+    # apply the correct timestamp processing.
+    # 
+    # Refs;
+    # - https://github.com/elastic/integrations/issues/15083  
   - rename:
      field: azure.signinlogs.created_date_time
      target_field: azure.signinlogs.time
