Splunk Enterprise Security

Problem on Changing Syslog Sourcetype

element1314
New Member

The problem is on changing syslog sourcetype into another one.
I read all splunk answer about it. I am following the instruction that i have been learn from there.
But it is still not success. All new source from udp:514 are still ingest under sourcetype=syslog

What did I do as below:
1. Create a new folder under apps with "splunk" account full access
2. Create a new props.conf and transform.conf under \newapp\local\
3. Props.conf

[syslog]
TRANSFORMS-force_sourcetype_for_newapp = force_sourcetype_for_newapp
  1. Transforms.conf

    [force_source_for_newapp]
    DEST_KEY = MetaData:Sourcetype
    REGEX = newapp
    FORMAT = sourcetype::newapp

Any idea what going wrong?

0 Karma

sduff_splunk
Splunk Employee
Splunk Employee

Change REGEX = newapp to REGEX = .

In your example, the sourcetype renaming would only happen to events that contain "newapp". REGEX=. means that it will apply to any events that pass through this transform.

Also, in props, you call it force_sourcetype_for_newapp, and in transforms, you call it force_source_for_newapp. They should be the same.

Overall, your file should look like this.

props.conf

[syslog]
TRANSFORMS-force_sourcetype_for_newapp = force_sourcetype_for_newapp

transforms.conf

[force_sourcetype_for_newapp]
DEST_KEY = MetaData:Sourcetype
REGEX = .
FORMAT = sourcetype::newapp

Have you restarted your Splunk instance after this change?

0 Karma
Get Updates on the Splunk Community!

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI! Discover how Splunk’s agentic AI ...

[Puzzles] Solve, Learn, Repeat: Dereferencing XML to Fixed-length events

This challenge was first posted on Slack #puzzles channelFor a previous puzzle, I needed a set of fixed-length ...

Stay Connected: Your Guide to December Tech Talks, Office Hours, and Webinars!

What are Community Office Hours? Community Office Hours is an interactive 60-minute Zoom series where ...