All Apps and Add-ons

Splunk add-on for Zenoss in a Search head clustered environment?

Path Finder

We're running into some issues with the Splunk add-on for Zenoss in our SHC environment, specifically around the credentials that must be stored for the Zenoss environment. Often times, we see the error "sendmodaction - signature="Failed to get password for user xxxx, realm xxxx. Verify credential account exists. User who scheduled alert must have Admin privileges. - 'None' has no attribute 'feed'" in the logs. This seems to happen when...

  1. A previously saved alert that was working is modified, or...
  2. Services on the SHC are restarted, or...
  3. New config bundles are pushed to the SHC from the deployment server.

The add-on (and my configuration of it) works just fine from a single search head (our license master server for example), but that's not really a production solution - it needs to run in the search head cluster. Has anyone been there, done that and have tips? It seems to me like it has something to do with the way the credentials are stored and retrieved within the Add-on.

0 Karma
*NEW* Splunk Love Promo!
Snag a $25 Visa Gift Card for Giving Your Review!

It's another Splunk Love Special! For a limited time, you can review one of our select Splunk products through Gartner Peer Insights and receive a $25 Visa gift card!


Or Learn More in Our Blog >>