Getting Data In

How to associate a value generated by a host with a field/event outside of the source?

ohlafl
Communicator

This is an overview of how my system produces a certain value:

alt text

Usually each area has a set of hosts, but there are also a few hosts that do not. In this case, one host that is not part of an area is generating a value that I need to associate with an area.

The name of the area can be found in the name of the source generated by the host such as source=/log/areaName/rest_of_path. Would it be possible to create an association using just SPL or must the flow be top down like area -- host -- value? How should I structure my search logic?

The purpose of this is to be able to list the Value by Area so that each Area will have one Value.

0 Karma

woodcock
Esteemed Legend

If I understand you correctly, you need thecoalesce command and can use it like this:

... | rex field=source "/[^/]+/(?<areaName>)[^/]+/" | eval areaName=coalesce(areaName, host) | stats values(Value) by areaName

Or, since every event will have a source so the rex command will have false positives for the "null" case above, maybe you need the if command like this:

... | rex field=source "/[^/]+/(?<areaName>)[^/]+/" | eval areaName=if(myTestHere(areaName), areaName, host) | stats values(Value) by areaName

ohlafl
Communicator

This would seem about right, yes, I do however get an error with the rex:

Error in 'rex' command: Encountered the following error while compiling the regex '/[^/]+/(?<areaName)[^/]+/': Regex: syntax error in subpattern name (missing terminator) 

I am not very familiar with regex, excuse my noobishness.

0 Karma

woodcock
Esteemed Legend

Sorry, I had a typo in my RegEx but I fixed it. Try 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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...