Splunk Search

Search with placeholder

ammannpa
New Member

I would like to filter the following messages in a way that i would get only the events where "DISK "?" Status : Online, Spun Up" AND "DISK "?" State : Warning" does match. The problem is that the placeholder "?" should be the same Number.

Therefore the search should only return the DISK 3 Error but not the DISK 4 one. Since the Index of the DISK could have different Numbers, i have to work with a placeholder but i don't know how.

2013-03-23 04:00:26 h0000.domain.org [1.1.1.1]:
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (1364007626) 157 days, 20:54:36.26 SNMPv2-MIB::snmpTrapOID.0 = OID: SNMPv2-SMI::enterprises.393.3.9.1.8 SNMPv2-SMI::enterprises.393.3.9.1.8 = STRING: "DISK 3 Slot Number : 2.DISK 3 Enclosure ID : 8.DISK 3 Status : Online, Spun Up.DISK 3 Serial Number : 52888162g8hgt28927gst SN12.DISK 3 Capacity : 1.819 TB .DISK 3 State : Warning.DISK 3 Type : SATA.DISK 3 Foreign state : None.DISK 3 ErrorStatus : 3..DISK 4 Slot Number : 3.DISK 4 Enclosure ID : 8.DISK 4 Status : Unconfigured(good).DISK 4 Serial Number : 73HGSU7623h3482jdu2b SN12.DISK 4 Capacity : 1.819 TB .DISK 4 State : Warning.DISK 4 Type : SATA.DISK 4 Foreign state : None.DISK 4 ErrorStatus : 3.." SNMPv2-SMI::enterprises.393.3.9.1.1 = STRING: "host01"

Tags (1)
0 Karma

ShaneNewman
Motivator

I would create a props.conf and transforms.conf for this sourcetype and do the field extractions that way. It looks like you may either need to setup these events to be broken out into transactions or segments. Once you do that you can use regex to extract the disk number in each segment/transaction, then use something like:

where disk_spunup=disk_warning

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!

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...

Splunk Developers: Construct Your Future at the .conf26 Builder Bar

Calling all Splunk architects, platform admins, and app developers: the site is open, and the blueprints are ...

Quick connection discovery mode for forwarders

When a Splunk forwarder loses connectivity to its indexers, it does not always reconnect immediately. In many ...