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
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!

Laser Bananas and Edge Hubs: Exploring Operational Technology (OT) Data Through a ...

  OT is a different environment to traditional IT and can have interesting challenges when interfacing the ...

Event Series: Mastering AI Tokenomics and Splunk Agent Observability

Beyond the Black Box: Correlating AI Performance and Tokenomics with Splunk Agent Observability   As ...

span_metrics: The OpenTelemetry-Idiomatic Way to See Inside Your Services

You open a trace in Splunk Observability Cloud and everything looks fine. One root span, order-pipeline, with ...