Deployment Architecture

Multiple same TA on a single universal forwarder

MikaJustasACN
Path Finder

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!

Tags (1)
0 Karma
1 Solution

MikaJustasACN
Path Finder

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.

View solution in original post

0 Karma

MikaJustasACN
Path Finder

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.

0 Karma

FrankVl
Ultra Champion

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.

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...