Getting Data In

Tag Logs Based on Host

jodros
Builder

There are several servers with universal forwarders loaded that are sending logs to our Splunk environment. These servers are all running the same applications, however some are production and some are development. There is nothing in the logs themselves to differentiate between prod and dev. The idea I had would be to key in on the Metadata:Host field to make this determination. However this is not working. Below is my config. Let me know what I am doing wrong.

Thanks

transforms.conf
[app_dev]
SOURCE_KEY = MetaData:Host
REGEX = (ho*dev)
FORMAT = environment::"dev"

props.conf
[app_dev]
REPORT-app_dev = app_dev

I am able to use actual tags to accomplish this, but was hoping to "tag" logs with a field extraction so that my field could be called "environment" and the values could be either "dev" or "prod". The code provided above is only for dev, but prod is similar.

Tags (2)
0 Karma
1 Solution

jodros
Builder

It appears that I will need to utilize the tags.conf file for what I need. This is somewhat cumbersome since it does not support wildcards or regex.

View solution in original post

0 Karma

jodros
Builder

It appears that I will need to utilize the tags.conf file for what I need. This is somewhat cumbersome since it does not support wildcards or regex.

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!

Data Management Digest – August 2026

MichelleCorpora_1-1788182384472.png Welcome to the August 2026 edition of Data Management Digest! August was a ...

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 ...