Getting Data In

Extract key=value into field

splunkville
Observer

[cmd_data=list cm device recusive]

splunk auto extracts just [cmd_data=list]


End result - be able to filter on cmd data and get the full cmd / mutiple values.

 

Will these configs work?

transforms.conf
[full_cmd]
SOURCE_KEY = cmd_data
REGEX = (cmd_data)\S(?<full_cmd>.*)
FORMAT = full_cmd::$1

props.conf
EXTRACT-field full_cmd

Labels (1)
0 Karma

livehybrid
SplunkTrust
SplunkTrust

Hi @splunkville 

No, this will not work because the source key (cmd_data) contains the shortened version which has been broken up due to the space.

Your transforms.conf and props.conf configs need adjustment. To extract the full value after cmd_data=, use this in transforms.conf:

== props.conf ==
[yourSourceytype]
REPORT-full_cmd = full_cmd

== transforms.conf ==
[full_cmd]
REGEX = cmd_data=([^\]]+)\]
FORMAT = full_cmd::$1

The REGEX captures everything after cmd_data= up to the "]". 
 REPORT- in props.conf applies the transform at search time.

🌟 Did this answer help you? If so, please consider:

  • Adding karma to show it was useful
  • Marking it as the solution if it resolved your issue
  • Commenting if you need any clarification

    Your feedback encourages the volunteers in this community to continue contributing

0 Karma
Get Updates on the Splunk Community!

Building Reliable Asset and Identity Frameworks in Splunk ES

 Accurate asset and identity resolution is the backbone of security operations. Without it, alerts are ...

Cloud Monitoring Console - Unlocking Greater Visibility in SVC Usage Reporting

For Splunk Cloud customers, understanding and optimizing Splunk Virtual Compute (SVC) usage and resource ...

Automatic Discovery Part 3: Practical Use Cases

If you’ve enabled Automatic Discovery in your install of the Splunk Distribution of the OpenTelemetry ...