topic Re: Multiple same TA on a single universal forwarder in Deployment Architecture

Multiple same TA on a single universal forwarder

MikaJustasACN — Wed, 24 Oct 2018 14:42:01 GMT

Hi All,

I have a question on how this should be approached. Stage:

There are multiple A type servers where wmi.conf is used to pull selected services related to application A.
There are multiple B type servers where wmi.conf is used to pull selected services related to application B.

Each server type has its own server class, and server classes use the same Windows TA but with a different wmi.conf. Everything is working well. Now, I hit a server type A with application A AND application B together on it, thus, I simply added to both server classes.

Outcome: I get application A logs but not application B. How to go around it? I don't want to create a special server class C where this happens, as this is only a portion of scope and management of such server classes would become horrible.

Windows TA is a copy of each other, just wmi.conf is changed.

Thank you for your help!

Re: Multiple same TA on a single universal forwarder

MikaJustasACN — Thu, 25 Oct 2018 08:17:02 GMT

After triple checking everything, noticed that I have not changed the stanza name... of course with the same stanza name it will not work 🙂 Though interesting how Splunk decides the precedence of one stanza over the other.

Re: Multiple same TA on a single universal forwarder

FrankVl — Thu, 25 Oct 2018 09:04:31 GMT

Glad you solved it already 🙂

One suggestion: don't copy the entire windows TA. Just deploy the default TA everywhere and create small separate add-ons that contain the local wmi.conf.