Splunk Search

Conditional field alias / rename

tmarlette
Motivator

I'm attempting to rename a field of windows data that will be put into a datamodel, however There seems to be a catch. While the sourcetype remains the same for both CPU and Memory, the field 'Value' using perfmon data is consistent.

Here are my two searches, 1 for CPU 1 for memory.

CPU:

index=perfmon tag=process_perf sourcetype="Perfmon:Process counter="% Processor Time"

Memory

 index=perfmon tag=process_perf sourcetype="Perfmon:Process counter="Private Bytes"

With both of these searches, the field Value has the values for each perfmon counter. What i'm trying to do is rename the Value field IFthe counter field is cpu specific. So something like IF counter="% Processor Time" THEN | rename Value as process_cpu. This is to make it generic so I can do the same thing for linux machines with my linux data.

I've looked at EVAL and match but I didn't see a way to recognize a field value, and then change another fields value. Any suggestions are appreciated.

Tags (2)
0 Karma
1 Solution

mayurr98
Super Champion

Try something like this if you want process_cpu field to have only Values of counter="% Processor Time"

<your_base_search> | eval process_cpu=case(counter="% Processor Time",Value)

Let me know if this helps you!

View solution in original post

mayurr98
Super Champion

Try something like this if you want process_cpu field to have only Values of counter="% Processor Time"

<your_base_search> | eval process_cpu=case(counter="% Processor Time",Value)

Let me know if this helps you!

micahkemp
Champion

Maybe:

| eval process_cpu=if(counter="% Processor Time", Value, NULL), Value=if(counter="% Processor Time", NULL, Value)
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!

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas

Watch Now Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas     Do you ever feel ...