Splunk Search

Field Extractions off host name

daniel333
Builder

Hello,

Our naming convention has a relatively strict set of rules on it.

e.g.
datacenter+envionmentnumber+securityzone+role+increment.
NY0099HTTPD001

Right now, I find myself add an extraction in EVERY source type I do to break that up as key value pairs for users. Is there a way to do this globally?

Tags (1)
0 Karma

Raghav2384
Motivator

Adding to what @acharlieh has mentioned, if you mention the extraction under default stanza, it should take precedence and apply to every sourcetype.
Example

The following stanza extracts an ip address from _raw

EXTRACT-extract_ip = (?\d{1,3}.\d{1,3}.\d{1,3}.\d{1,3})
[foo]
.......

[bar]

Hope this helps. Thanks!
Raghav

0 Karma

acharlieh
Influencer

Not in the UI, but I would think you could define a named REPORT outside of all stanzas in props.conf, or define it in a wild carded stanza:

http://docs.splunk.com/Documentation/Splunk/latest/admin/Propsconf

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!

Monitoring AI Agents with Splunk Observability Cloud

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...

[Puzzles] Solve, Learn, Repeat: Tiling

This puzzle (first published here) is based on finding groups of tessellated tiles (inspired by floor tiles I ...

SOK it to Me: Top 3 Benefits of Using Splunk Operator on Kubernetes that’ll Make ...

    Thursday, July 9, 2026  |  11:00AM–12:00PM PDT Duration: 1 hour (includes Q&A) Managing can feel like a ...