Splunk Search

Transform for sourcetype issue

LiquidTension
Path Finder

I am trying to make a minor update to take some data that is coming in via syslog and change the sourcetype to infoblox_dns and the move it to the network index but having issues getting splunk to recognize it. What am I doing wrong!?

transforms.conf:

[mc_force_sourcetype_for_infoblox_dns]
REGEX = (\d+\.\d+\.\d+\.\d+\s(named|dhcpd|lbsyncd|lbsync_f5)|\[\d+\]\:|\d+\.\d+\.\d+\.\d+\s(lbsync_f5|Available\sLeases|Total\sAddresses|Active\sLeases|Current\sUsage|High\sReset\sMark|High\sTrigger\sMark|Low\sReset\sMark|Low\sTrigger\sMark|Range|Network|Member|kernel|serial_console|/infoblox/one/bin/rotate_syslog)\:)
DEST_KEY = MetaData:Sourcetype
FORMAT = sourcetype::infoblox_dns

[mc_force_index_for_infoblox_dns]
SOURCE_KEY = MetaData:Sourcetype
REGEX = (infoblox_dns)
DEST_KEY = _MetaData:Index
FORMAT = network

Props.conf:
[syslog]
TIME_FORMAT = %b %d %H:%M:%S
TIME_PREFIX = ^
SHOULD_LINEMERGE = false
TRUNCATE = 1000000
KV_MODE = none
ANNOTATE_PUNCT = false
LINE_BREAKER = ([\n\r]+)

TRANSFORMS-2_syslog_sourcetypes = mc_force_sourcetype_for_infoblox_dns
TRANSFORMS-3_syslog_index = mc_force_index_for_infoblox_dns

[splunk@host ~]$ splunk cmd btool transforms list --debug | grep infoblox | less

/opt/splunk/etc/slave-apps/mc_all_syslog_props/local/transforms.conf          [mc_force_index_for_infoblox_dns]
/opt/splunk/etc/slave-apps/mc_all_syslog_props/local/transforms.conf          REGEX = (infoblox_dns)
/opt/splunk/etc/slave-apps/mc_all_syslog_props/local/transforms.conf          [mc_force_sourcetype_for_infoblox_dns]
/opt/splunk/etc/slave-apps/mc_all_syslog_props/local/transforms.conf          FORMAT = sourcetype::infoblox_dns
/opt/splunk/etc/slave-apps/mc_all_syslog_props/local/transforms.conf          REGEX = (\d+\.\d+\.\d+\.\d+\s(named|dhcpd|lbsyncd|lbsync_f5)|\[\d+\]\:|\d+\.\d+\.\d+\.\d+\s(lbsync_f5|Available\sLeases|Total\sAddresses|Active\sLeases|Current\sUsage|High\sReset\sMark|High\sTrigger\sMark|Low\sReset\sMark|Low\sTrigger\sMark|Range|Network|Member|kernel|serial_console|/infoblox/one/bin/rotate_syslog)\:)
0 Karma

Runals
Motivator

2 thoughts depending on how your environment is setup. Out of curiosity have you restarted your indexer(s) after making your change or the one proposed to somesoni2? If that data is being handled by a heavy forwarder the props/transforms will need to be pushed to it.

0 Karma

LiquidTension
Path Finder

I did issue a rolling restart command after pushing the change via the cluster master and that did not resolve the problem. I will give somesoni2's suggest a shot here later today.

0 Karma

somesoni2
Revered Legend

Try this in your transforms.conf

 [mc_force_sourcetype_for_infoblox_dns]
 REGEX = (\d+\.\d+\.\d+\.\d+\s(named|dhcpd|lbsyncd|lbsync_f5)|\[\d+\]\:|\d+\.\d+\.\d+\.\d+\s(lbsync_f5|Available\sLeases|Total\sAddresses|Active\sLeases|Current\sUsage|High\sReset\sMark|High\sTrigger\sMark|Low\sReset\sMark|Low\sTrigger\sMark|Range|Network|Member|kernel|serial_console|/infoblox/one/bin/rotate_syslog)\:)
 DEST_KEY = MetaData:Sourcetype
 FORMAT = sourcetype::infoblox_dns

 [mc_force_index_for_infoblox_dns]
REGEX = (\d+\.\d+\.\d+\.\d+\s(named|dhcpd|lbsyncd|lbsync_f5)|\[\d+\]\:|\d+\.\d+\.\d+\.\d+\s(lbsync_f5|Available\sLeases|Total\sAddresses|Active\sLeases|Current\sUsage|High\sReset\sMark|High\sTrigger\sMark|Low\sReset\sMark|Low\sTrigger\sMark|Range|Network|Member|kernel|serial_console|/infoblox/one/bin/rotate_syslog)\:)
 DEST_KEY = _MetaData:Index
 FORMAT = network
0 Karma

LiquidTension
Path Finder

This unfortunately did not work either after making the change and restarting the indexers. The data is still coming in

index=main, sourcetype=syslog

0 Karma

LiquidTension
Path Finder

Any other ideas or something standing out that I am doing wrong?

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!

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

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