All Apps and Add-ons

Puppet Report Viewer Alert action script returned error code=5

dbot2001
Path Finder

Getting an error code=5 whenever running an alert action from Puppet Report Viewer

action=puppet_generate_detailed_report - Alert action script returned error code=5

First time setup, how do I troubleshoot this?

 

Labels (2)
Tags (1)
0 Karma

dbot2001
Path Finder

It appears transaction_uuid is required.  Not sure if this is supposed to come from alert metadata, but adding it to Splunk results e.g.

| eval transaction_uuid="bolttest_" . host . "_" .strftime(now(),"%s")

seems to work

0 Karma

dbot2001
Path Finder

The transaction_uuid field added to the results works for bolt task, I haven't figured out how any of the other alert actions are to be used

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 ...