Getting Data In

Why Splunk could not get the description for this event?

hrawat
Splunk Employee
Splunk Employee

Issue happens after windows server is restarted. Restarting splunk universal forwarder fixes the issue.

Either the component that raises this event is not installed

Labels (2)
0 Karma
1 Solution

hrawat
Splunk Employee
Splunk Employee
0 Karma

hrawat
Splunk Employee
Splunk Employee

There are two workarounds.

1. Use 'Delayed Start' for the Splunk Forwarder service. (https://community.splunk.com/t5/Getting-Data-In/Why-quot-FormatMessage-error-quot-appears-in-indexed...). However it's hard to configure thousands of DCs.

2. Configure  interval as cron schedule instead.

interval = [<decimal>|<cron schedule>]

 

[WinEventLog]

interval=* * * * *

 


By default wineventlog interval is 60 sec. That means as soon as splunk is restarted, wineventlog (or any modinput) is immediately started. Subsequently every 60( configured interval) splunk checks if modinput is still running. If not, re-launch modinput.
Instead of setting interval 60 sec, if we use cron schedule to run every minute, then splunk is not going to launch modinput immediately. So essentially the idea is to convert interval setting from decimal to cron schedule to introduce a delay.

0 Karma
Get Updates on the Splunk Community!

Observe and Secure All Apps with Splunk

  Join Us for Our Next Tech Talk: Observe and Secure All Apps with SplunkAs organizations continue to innovate ...

Splunk Decoded: Business Transactions vs Business IQ

It’s the morning of Black Friday, and your e-commerce site is handling 10x normal traffic. Orders are flowing, ...

Fastest way to demo Observability

I’ve been having a lot of fun learning about Kubernetes and Observability. I set myself an interesting ...