Upgrade DataPrepper component (#30)

/lgtm

Author: LHozzan

chart/templates/opensearch/os-data-prepper-sec.yaml

@@ -40,7 +40,7 @@ stringData:
           # With 64 as batch size each worker thread could process upto 3200 spans (64 * 50)
           batch_size: 256
       processor:
-        - otel_trace_raw:
+        - otel_traces:
       sink:
         - opensearch:
             index_type: custom
@@ -57,7 +57,7 @@ stringData:
         pipeline:
           name: "entry-pipeline"
       processor:
-        - service_map_stateful:
+        - service_map:
           # The window duration is the maximum length of time the data prepper stores the most recent trace data to evaluvate service-map relationships.
           # The default is 3 minutes, this means we can detect relationships between services from spans reported in last 3 minutes.
           # Set higher value if your applications have higher latency.

chart/values.yaml

@@ -253,7 +253,7 @@ data_prepper:
   # -- Used image name.
   image: opensearchproject/data-prepper
   # -- Used component version.
-  imageTag: "2.0.1"
+  imageTag: "2.3.1"
   # -- Replicas count for DataPrepper pods.
   replicas: 1
   # -- Set JVM parameters `-Xms` and `-Xmx`, basicaly set JVM memory size. Consider this value as a half of total pod memory.