Burrow email alert not working
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4k
- Forks
- 818
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 1
Description
I have setup burrow in an EKS container. I have setup SES for smtp and registered email addresses in SES. The variables in the template are being replaced fine. The service runs fine . However the email notification isn't working. I am using the below section in burrow.toml. The templates are the same as in the source. I have not changed that. I have also tried with [emailnotifier "xx*xy.com"] + [smtp] sections in the config but did not get it working:
`[notifier.myplace]
class-name="email"
interval=60
threshold=1
send-close=true
template-open="/etc/burrow/default-email.tmpl"
template-close="/etc/burrow/default-email.tmpl"
server="$smtp_server"
port=25
from="$from_email_address"
to="$to_email_address"
auth-type="plain"
username="$smtp_username"
password="$smtp_password"
noverify=true
[notifier.myplace."headers"]
Content-Type="application/json"`
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the email notifier using the provided burrow.toml section in the EKS environment, with the SES SMTP settings and default email templates. Trace the notifier configuration and SMTP delivery path to identify why no notification is sent; done means an alert email is delivered successfully with the configured template and headers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go, kubernetes
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100