Getting Data In

Splunk Otel Multiline Configs

dgill
Loves-to-Learn

I'm using the splunk-otel-collector, and attempting to get multi-line java exceptions into a standardly formatted event. Using the example, my values file contains

 

 

 

 

     multilineConfigs:
        - namespaceName:
            value: example
            useRegexp: true
          firstEntryRegex: ^[^\s].*
          combineWith: ""

 

 

The rendered configMap contains

 

        - combine_field: attributes.log
          combine_with: ""
          id: example
          is_first_entry: (attributes.log) matches "^[^\\s].*"
          max_log_size: 1048576
          output: clean-up-log-record
          source_identifier: resource["com.splunk.source"]
          type: recombine

 

With that config, the logs continue to split . Then I change the value to

 

 

 

combineWith: "\t"

 

 

 

 

the following happens with the logs:

 

Screenshot 2024-10-08 at 2.36.59 PM.png

 

Has anyone experienced this and worked around it?

0 Karma

PaulPanther
Motivator

If you use 

combineWith: "\t"

the log entries are correctly splitted or not?

Could you remove the combinedWith parameter from the config and deploy it again?

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Laser Bananas and Edge Hubs: Exploring Operational Technology (OT) Data Through a ...

  OT is a different environment to traditional IT and can have interesting challenges when interfacing the ...

Event Series: Mastering AI Tokenomics and Splunk Agent Observability

Beyond the Black Box: Correlating AI Performance and Tokenomics with Splunk Agent Observability   As ...

span_metrics: The OpenTelemetry-Idiomatic Way to See Inside Your Services

You open a trace in Splunk Observability Cloud and everything looks fine. One root span, order-pipeline, with ...