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!

Quick connection discovery mode for forwarders

When a Splunk forwarder loses connectivity to its indexers, it does not always reconnect immediately. In many ...

Build and Launch AI Agents from Your Splunk Workflows

  Register We’ve all been there: juggling alerts, runbooks, and endless manual searches. What if you could ...

Splunk Cloud Application Management in Terraform

Register   On Tuesday, August 4 at 11AM PDT / 2PM EDT, we’re diving into how you can bring Infrastructure as ...