Getting Data In

Help Solving btool errors from alert_manager app

dpwtheitguy
Loves-to-Learn Lots

All,

I've started seeing the following error message on Splunk 8.2.1 since installing alert_manager app and I'd like to clean it up.

- Error from my deployment server, from btool checks
- Version Splunk 8.2.1
- CentOS7
- I have /etc/deployment-apps/alert_manager/README/alert_manager.conf.spec there. So I assume that's what it's looking for.


# Error
08-10-2021 13:23:41.948 -0700 WARN Application [28063 MainThread] - No spec file for: /opt/splunk/etc/deployment-apps/alert_manager/default/alert_manager.conf\n
08-10-2021 13:23:41.948 -0700 WARN Application [28063 MainThread] - Invalid key in stanza [alert_manager] in /opt/splunk/etc/deployment-apps/alert_manager/default/alert_actions.conf, line 12: param.urgency (value: low).\n


# alert_manager.conf, line 12 under [settings] stanza
auto_close_info = false


# alert_manager.conf.spec, line 40, under [settings] stanza
auto_close_info = [true | false]
* Configure if informational events are automatically resolved
* Defaults to false

 

Any ideas on how I'd troubleshoot this? 

Tags (2)
0 Karma

codebuilder
Influencer

The file needs to be named alert_manager.conf not alert_manager.conf.spec.

alert_manager.conf.spec is a reference file.

----
An upvote would be appreciated and Accept Solution if it helps!
0 Karma

dpwtheitguy
Loves-to-Learn Lots

Thanks for replying. 

The app has both alert_manager.conf and alert_manager.conf.spec in it. Neither of which have any obvious problems that I can see. Nevertheless Splunk btool is complaining. 

0 Karma

codebuilder
Influencer

Remove the /etc/deployment-apps/alert_manager/README directory from your deployment app and try again. The .spec files are reference and contain examples with descriptions of parameter  that are not valid values. That is why you are getting the errors.

Also consider putting any other configs you modified in /etc/deployment-apps/alert_manager/local
Never directly modify configs in the default directory.

----
An upvote would be appreciated and Accept Solution if it helps!
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...