Splunk Enterprise

Splunk Add-on for SolarWinds - Alerts input not working

Splunking
Engager

We have a standalone Splunk Enterprise environment running Splunk 8.2.x.   We have loaded the Splunk Add-on for SolarWinds  (latest version -- just downloaded it about two weeks ago).    We are trying to get all three SolarWinds inputs (Alerts, Query, Inventory) to work in the Splunk Add-on for SolarWinds.  The Query and Inventory Inputs work fine but the Alerts are not working  (we are getting no data returned even though SolarWinds is producing alerts on its console).  My questions are these:

1.  Has anyone else experienced this problem and found a solution?

2.  Does anyone know which logs in either Splunk or SolarWinds that we can look at to help debug this issue?

Thanks for your help.

Labels (1)
0 Karma
1 Solution

Splunking
Engager

We resolved this issue ourselves.    The needed Splunk logs  for each SolarWinds Alert can be found at $SPLUNK_HOME/var/log/splunk. When looking at the solarwinds_alerts log,  we noticed that the initial_start_time was set to the future --  it was set to 2022-02-28T00:00:00.0  instead of 2022-01-28T00:00:00.0.  We changed the  initial_start_time to 2022-01-28T00:00:00.0 in the GUI, restarted splunk, and tested again.  Still no alerts being generated.   We then rebooted the server and the alerts were still not being generated after reboot.   When we looked at the log file again it kept identifying the original  incorrect initial_start_time in the log though it was displayed correctly with a time of 2022-01-28T00:00:00.0  in the GUI.   Finally, we created a new alert with the correct initial_start_time of 2022-01-28T00:00:00.0 and everything worked.   The original alert still does not work.

View solution in original post

Tags (1)

Splunking
Engager

We resolved this issue ourselves.    The needed Splunk logs  for each SolarWinds Alert can be found at $SPLUNK_HOME/var/log/splunk. When looking at the solarwinds_alerts log,  we noticed that the initial_start_time was set to the future --  it was set to 2022-02-28T00:00:00.0  instead of 2022-01-28T00:00:00.0.  We changed the  initial_start_time to 2022-01-28T00:00:00.0 in the GUI, restarted splunk, and tested again.  Still no alerts being generated.   We then rebooted the server and the alerts were still not being generated after reboot.   When we looked at the log file again it kept identifying the original  incorrect initial_start_time in the log though it was displayed correctly with a time of 2022-01-28T00:00:00.0  in the GUI.   Finally, we created a new alert with the correct initial_start_time of 2022-01-28T00:00:00.0 and everything worked.   The original alert still does not work.

Tags (1)

ilhwan
Path Finder

Are you saying that the add-on is not worth using?

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...