Refactor receiver configs and update transformation logic

logzio · Apr 8, 2024 · 09c94ef · 09c94ef
1 parent 5a9c841
commit 09c94ef
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/resources/otel/processors/transform_application.yaml b/resources/otel/processors/transform_application.yaml
@@ -5,4 +5,4 @@ transform/application:
       statements: 
         - flatten(body["event_data"], depth=1)
         - flatten(body["event_data"], depth=2)
-        - replace_all_patterns(body["event_data"], "key", "data.([0-9]).", "data_$$1")
+        - replace_all_patterns(body["event_data"], "key", "^data.([0-9A-Za-z]+).", "data_$${1}_") # Transforms 'data.<dynamic_part>.' keys. If <dynamic_part> is not empty, it formats as 'data_0_TargetUserName:"Administrator"'. Otherwise, it appears as 'data_0_:"Administrator"'.
diff --git a/resources/otel/receivers/windowseventlog_application.yaml b/resources/otel/receivers/windowseventlog_application.yaml
@@ -36,5 +36,5 @@ receiver:
   windowseventlog/application/NAME:
     channel: Application
     exclude_providers: []
-    attributes:
+    resource:
       type: