saltstack / saltstack/salt

[FEATURE REQUEST] Email Notification for Failed Minions in Salt Orchestrate

Open
#67,881 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature needs-triage
Dominant language
Python
Stars
15.7k
Forks
5.6k
Avg merge
2d 44m
Merged PRs (30d)
80

Description

Description:
I use Salt Runner Orchestrate to deploy Highstate across my infrastructure. To ensure that my systems are kept up to date, I schedule this process to run daily via crontab.

However, there is currently no built-in way to get feedback on whether the deployment was successful or if any minions failed. I would like to receive an email notification when a Minion encounters an error during the Highstate run.

I've searched the documentation and existing issues, but haven't found a straightforward solution for this. If such a feature doesn't exist, it would be a valuable addition to Salt.

Suggested solution:

  • An option to configure email notifications for failed minions in Salt Orchestrate.
  • Alternatively, a way to easily extract the results of failed minions and trigger custom alerting mechanisms.

Is there a recommended way to achieve this or would this be a potential feature for future releases?

Thanks for your time and consideration!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names Salt Runner Orchestrate and daily crontab execution but no source files or tests. Start by reviewing the Salt Orchestrate documentation and the existing failed-minion result handling, then determine whether notification configuration or result extraction is the intended scope. Done should include an agreed behavior for failed-minion alerts and a documented, tested implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.