All Apps and Add-ons

Add-on for Microsoft Forefront Threat Management Gateway: TMG logs not parsed based on tmg sourcetype

prithvi08
Engager

I have installed universal forwarder on TMG server to monitor tmg specific log files. Added the following to inputs.conf under /etc/system/local

[monitor://C:\ISALOG*]
disabled = false
sourcetype = microsoft:forefront:tmg:proxy
index = tmg

I have installed the TMG add on for splunk and have the sourcetypes to parse the data. The forwarded data from universal forwarder are parsed based on default sourcetype. most of the fields are not parsed. i understand universal forwarder are capable of only forwarding the data. In splunk server, how do i set the receiving log files to be parsed based on a specific source-type.? i have many other logs coming in through the same port from different universal forwarders.

0 Karma

prithvi08
Engager

Thanks a lot .. I guess i might have overlooked that part.

0 Karma

harsmarvania57
Ultra Champion

Please let us know if my comment resolved your issue then I’ll convert it into answer.

0 Karma

harsmarvania57
Ultra Champion

Hi @prithvi08,

Based on documentations https://splunkbase.splunk.com/app/3011/#/details, you need to install this Add-on on Splunkforwarder as well because microsoft:forefront:tmg:proxy uses INDEXED_EXTRACTIONS which applies on forwarder not on indexers.

0 Karma
Get Updates on the Splunk Community!

New in Observability - Improvements to Custom Metrics SLOs, Log Observer Connect & ...

The latest enhancements to the Splunk observability portfolio deliver improved SLO management accuracy, better ...

Improve Data Pipelines Using Splunk Data Management

  Register Now   This Tech Talk will explore the pipeline management offerings Edge Processor and Ingest ...

3-2-1 Go! How Fast Can You Debug Microservices with Observability Cloud?

Register Join this Tech Talk to learn how unique features like Service Centric Views, Tag Spotlight, and ...