Alerting

Data Routing to an Index based on Sourcetype

bhavneeshvohra
Engager

Hello Everyone,

I am integrating logs from trend micro portable security  via HEC.

As per the user guide of trend micro they need a HEC token that should have access to 5 indexes namely(sacnnedlog,detectedlog,applicationinfo,updateinfo,assetinfo) the names should not be changed as it will not be able to send logs .

So I have created a HEC token with sourctype=trendmicro and have given access to all 5 indexes created on HF.

Now the catch is in our splunk environment we cannot have 5 indexes for one source thus we have created 5 indexes at HF (same name as above) and we are trying to route all logs for sourcetype trendmicro to an index named app_trendmicro (created on Cluster master).

 i have used following props and transforms

In props:-

[trendmicro]

TRANSFORMS-routing = trendmicro_routing

In transforms:-

[trendmicro_routing]

DEST_KEY = _MetaData:Index
REGEX = .
FORMAT = app_trendmicro

however we are  not able to receive logs and getting error in internal index  as

Received event for unconfigured/disabled/deleted index

 

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!

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

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...