Inbound email integration #837
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Conflicts: # engine/requirements.txt
# Conflicts: # engine/requirements.txt
For now I want to make sure that InboundEmail is working with mailgun. Other ESPs stability is for next iteration.
Matvey-Kuk
suggested changes
Mar 13, 2023
| ## Grouping and auto-resolve | ||
|
|
||
| Alert groups will be grouped by email subject and auto-resolved if email message text equals "OK". | ||
| This behaviour can be modified via custom templates. |
There was a problem hiding this comment.
Alert groups will be grouped by email subject and auto-resolved if the email message text equals "OK".
CHANGELOG.md
Outdated
| @@ -5,6 +5,10 @@ All notable changes to this project will be documented in this file. | |||
| The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), | |||
| and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). | |||
|
|
|||
| ## Unreleased | |||
|
|
|||
| - Inbound email integration | |||
There was a problem hiding this comment.
May be refer to this PR? :)
| @@ -50,3 +50,4 @@ opentelemetry-exporter-otlp-proto-grpc==1.15.0 | |||
| pyroscope-io==0.8.1 | |||
| django-dbconn-retry==0.1.7 | |||
| django-ipware==4.0.2 | |||
| django-anymail==8.6 | |||
| @@ -0,0 +1,41 @@ | |||
| --- | |||
There was a problem hiding this comment.
Could you also please add OSS configuration instruction here? https://grafana.com/docs/oncall/latest/open-source/#email-setup
1. Code structure 2. Templates
…dimkerr/inbound-email
Matvey-Kuk
approved these changes
Mar 14, 2023
…dimkerr/inbound-email
brojd
pushed a commit
that referenced
this pull request
Sep 18, 2024
This PR add Inbound Email integration. It designed to support some variety of ESPs, but in prod we will use Mailgun, so locally I tested it only with mailgun ESP. **Important:** To make it work on different clusters I'm planning to provide different email domains for different regions, like ....@us.oncall.grafana.net, ...@eu.oncall.grafana.net --------- Co-authored-by: Innokentii Konstantinov <innokenty.konstantinov@grafana.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR add Inbound Email integration.
It designed to support some variety of ESPs, but in prod we will use Mailgun, so locally I tested it only with mailgun ESP.
Important:
To make it work on different clusters I'm planning to provide different email domains for different regions, like ....@us.oncall.grafana.net, ...@eu.oncall.grafana.net