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!

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