All Apps and Add-ons

Splunk Add-on for Microsoft Cloud Services _TCP_ROUTING

melvinfuglem
Explorer

I am running Splunk Add-on for Microsoft Cloud Services on a Splunk Heavy Forwarder and I'm trying to forward the azure audit log to two splunk instances. The problem is that it only forwards it to the default output. I have tried this:

mscs_azure_audit_inputs.conf
[AZURE_AUDIT]
account = AZURE
index = AZURE_AUDIT
interval = 300
start_time = 2019-10-19T13:00:34+02:00
subscription_id =
disabled = 0
_TCP_ROUTING = splunk1, splunk2

I have tried props.conf and transforms.conf with targeting sourcetype, source and host.
props.conf
[host::hostname]
TRANSFORMS-routing = azureauditlog_to_splunks

transforms.conf
[azureauditlog_to_splunks]
SOURCE_KEY = _MetaData:Index
REGEX = (?i)azure_audit
DEST_KEY = _TCP_ROUTING
FORMAT = splunk1, splunk2

I have tried adding _TCP_ROUTING to to the inputs.conf, but it creates a new input.

[mscs_azure_audit://AZURE_AUDIT]
_TCP_ROUTING = splunk1, splunk2

[mscs_azure_audit]
_TCP_ROUTING = splunk1, splunk2

I'm starting to run out of ideas. Anyone have any ideas?

0 Karma
Get Updates on the Splunk Community!

Splunk Observability Synthetic Monitoring - Resolved Incident on Detector Alerts

We’ve discovered a bug that affected the auto-clear of Synthetic Detectors in the Splunk Synthetic Monitoring ...

Video | Tom’s Smartness Journey Continues

Remember Splunk Community member Tom Kopchak? If you caught the first episode of our Smartness interview ...

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

3-2-1 Go! How Fast Can You Debug Microservices with Observability Cloud? Learn how unique features like ...