Getting Data In

How do I redirect to another indexer using wildcards in my props.conf?

daniel333
Builder

All,

I have the following props.conf / transforms.conf setup. Trying to set aside PCI into it's own set of indexers. However, redirection only works with a fully qualified hostname. Wildcards don't seem to work. Is there something I am missing?

transforms.conf

REGEX=.
DEST_KEY=_TCP_ROUTING
FORMAT=pci-group

props.conf
doesn't work

[host::myvery.*]
TRANSFORMS-routing=pciRoutingbeta

doesn't work

[(?::){0}myvery*]
TRANSFORMS-routing=pciRoutingbeta

doesn't work

[(?::){0}myvery.*]
TRANSFORMS-routing=pciRoutingbeta

does work!

[host::myverylongservername]
TRANSFORMS-routing=pciRoutingbeta
0 Karma

lguinn2
Legend

I'm glad that you are figuring out the wildcards/regex for props.conf.

However, it would be easier - and more efficient - if you could do this routing at input time, instead during parsing.
You can specify the tcp routing in inputs.conf as well. It would look like this:

inputs.conf (on the hosts that you want to route in a special way)

[monitor:///therightfiles]
_TCP_ROUTING = pciRoutingbeta
0 Karma

sk314
Builder

did you try host::myvery*?

0 Karma

TStrauch
Communicator

try sk314´s way. this is explained in props.conf documentation.

0 Karma
Get Updates on the Splunk Community!

Welcome to the Splunk Community!

(view in My Videos) We're so glad you're here! The Splunk Community is place to connect, learn, give back, and ...

Tech Talk | Elevating Digital Service Excellence: The Synergy of Splunk RUM & APM

Elevating Digital Service Excellence: The Synergy of Real User Monitoring and Application Performance ...

Adoption of RUM and APM at Splunk

    Unleash the power of Splunk Observability   Watch Now In this can't miss Tech Talk! The Splunk Growth ...