Getting Data In

does universalforwarder support SEDCMD?

crazyeva
Contributor

timeformat is not desired, I tried SEDCMD to correct it(12-hour format with 'am','pm')

props.conf of INDEXER:
SEDCMD-timechar=s/XXXXX/AM/g s/YYYYY/PM/g
TIME_FORMAT=%d-%m-%y %I.%M.%S.%9N %p

but '%p' is not recognized, as SEDCMD has not been effective in the same props.conf.

I wonder if i can put SEDCMD to UNIVERSALFORWARDER, and TIME_FORMART remain on INDEXER?

Tags (1)
1 Solution

gfuente
Motivator

Hello

SEDCMD happens at the parsing stage, so it applies in a heavy forwarder or in a indexer.

Regards

View solution in original post

gfuente
Motivator

Hello

SEDCMD happens at the parsing stage, so it applies in a heavy forwarder or in a indexer.

Regards

crazyeva
Contributor

'TIME_FORMAT=%d-%m-%y %I.%M.%S.%9N %p' is correct when i manully modified source data with AM/PM
and 'SEDCMD' part is also effective of replacing XXYY with AM/PM
But they do not work together.

0 Karma

gfuente
Motivator

If your config is correct it should work on the indexer, or you can use a heavy forwarder too. Anyway try it locally in the indexer until it works, then move your configs into the production enviroment.

0 Karma

crazyeva
Contributor

thank you!
do you have any idea to solve my problem:
timestamp form '22-1-14 09.30.00.000000000 \A\C' in which '\A\C' means PM

0 Karma
Get Updates on the Splunk Community!

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...

Detecting Remote Code Executions With the Splunk Threat Research Team

REGISTER NOWRemote code execution (RCE) vulnerabilities pose a significant risk to organizations. If ...