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!

Celebrating Fast Lane: 2025 Authorized Learning Partner of the Year

At .conf25, Splunk proudly recognized Fast Lane as the 2025 Authorized Learning Partner of the Year. This ...

Tech Talk Recap | Mastering Threat Hunting

Mastering Threat HuntingDive into the world of threat hunting, exploring the key differences between ...

Observability for AI Applications: Troubleshooting Latency

If you’re working with proprietary company data, you’re probably going to have a locally hosted LLM or many ...