Getting Data In

props.conf hostname with hyphen

carlosumbc
Loves-to-Learn Lots

We are able to match entries in props.conf using the hostname... unless that hostname has a hyphen. Then, for whatever reason, it never matches. See example below:

[host::server1.example.com]
TRANSFORMS-server1 = route_to_idx1

This works

[host::server-2.example.com]
TRANSFORMS-server2 = route_to_idx2

This doesn't work

0 Karma

MousumiChowdhur
Contributor

Hi @carlosumbc ,

Please use * instead of - and try.

[host::server*2.example.com]
TRANSFORMS-server2 = route_to_idx2

Let me know if that works.

Thank You!

0 Karma

ddrillic
Ultra Champion

@carlosumbc, please keep in mind that we can use wildcards (*) and regex in the host and source stanzas.

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!

How to Break a Kubernetes Pod on Purpose and Let the AI Troubleshooting Agent Find ...

Let's say I've just rolled out a Kubernetes Deployment with a typo in the image tag. Nothing explodes. The pod ...

Splunk Add-on for Microsoft Windows 11.0.3: Parse Once, Search Faster

The updated Splunk Add-on for Microsoft Windows helps customers search Windows events faster by reducing ...

What's New in Splunk Enterprise Security 8.8 and Beyond

Threats move at machine speed. Keeping up should not depend on having the biggest budget, the largest team, or ...