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!

[Puzzles] Solve, Learn, Repeat: Matching cron expressions

This puzzle (first published here) is based on matching timestamps to cron expressions.All the timestamps ...

Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas

Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas     Cisco Live 2026 is almost here, and this ...

Data Management Digest – May 2026

Welcome to the May 2026 edition of Data Management Digest!   As your trusted partner in data innovation, the ...