fix(otellogs): fix configuration due to issue

issue: open-telemetry/opentelemetry-log-collection#415
Signed-off-by: Dominik Rosiek <drosiek@sumologic.com>

deploy/helm/sumologic/values.yaml

@@ -4405,7 +4405,10 @@ otellogs:
             type: recombine
             output: extract-metadata-from-filepath
             combine_field: log
-            is_first_entry: $$body.log matches "^\\d{4}-\\d{1,2}-\\d{1,2}.\\d{2}:\\d{2}:\\d{2}.*"
+            is_first_entry: $$body.log matches "^[^\\s]"
+            ## Prefer the following regexp, when https://github.com/open-telemetry/opentelemetry-log-collection/issues/415
+            ## will be resolved
+            # is_first_entry: $$body.log matches "^\\d{4}-\\d{1,2}-\\d{1,2}.\\d{2}:\\d{2}:\\d{2}.*"
 
           ## extract-metadata-from-filepath extracts data from the `file.path` Attribute into the Body, removing the `file.path` attribute.
           ## Input Attributes:
@@ -4508,9 +4511,9 @@ otellogs:
       ## The batch processor accepts spans and places them into batches grouped by node and resource
       batch:
         ## Number of spans after which a batch will be sent regardless of time
-        ## This is set to the same value as in the metadata enricher
+        ## This is set to the 10240, to avoid loosing logs on the start of the collector 
         ## TODO: Figure out what the optimal values should be for different configurations
-        send_batch_size: 256
+        send_batch_size: 10_240
         ## Time duration after which a batch will be sent regardless of size
         timeout: 1s
   daemonset: