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!

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...

Level Up Your Workflow: Mastering Splunk Cloud Management via Terraform

Tech Talk Recap   From Chaos to Control: Scaling Splunk Cloud with Infrastructure as Code Managing apps in ...