https://community.splunk.com/t5/Getting-Data-In/Tag-Logs-Based-on-Host/m-p/32038#M5646 <P>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. </P> Fri, 20 Apr 2012 20:37:50 GMT jodros 2012-04-20T20:37:50Z https://community.splunk.com/t5/Getting-Data-In/Tag-Logs-Based-on-Host/m-p/32037#M5645 <P>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.</P> <P>Thanks</P> <PRE><CODE>transforms.conf [app_dev] SOURCE_KEY = MetaData:Host REGEX = (ho*dev) FORMAT = environment::"dev" props.conf [app_dev] REPORT-app_dev = app_dev </CODE></PRE> <P>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.</P> Fri, 20 Apr 2012 14:13:27 GMT https://community.splunk.com/t5/Getting-Data-In/Tag-Logs-Based-on-Host/m-p/32037#M5645 jodros 2012-04-20T14:13:27Z https://community.splunk.com/t5/Getting-Data-In/Tag-Logs-Based-on-Host/m-p/32038#M5646 <P>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. </P> Fri, 20 Apr 2012 20:37:50 GMT https://community.splunk.com/t5/Getting-Data-In/Tag-Logs-Based-on-Host/m-p/32038#M5646 jodros 2012-04-20T20:37:50Z