Add Environment tag into email subject or body for alerts
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 22h 21m
- Merged PRs (30d)
- 586
Description
### Problem Statement
The current email notification system for issue tracking is ineffective for production monitoring. Notifications are received for all environments (Development [D], Testing [T], Acceptance [A], and Production [P]) without the ability to configure separate email notifications per environment. This results in an overwhelming number of notifications, making it difficult to prioritize and respond to production-related issues promptly.
### Solution Brainstorm
1. Environment Flagging: Add an environment flag (e.g., [D], [T], [A], [P]) to the email subject or body. This allows users to set up Outlook filters to prioritize notifications affecting the production environment.
2. Priority Tagging: Introduce a priority tagging system within the notifications, where issues affecting production are tagged as high priority, ensuring they stand out in the user's inbox.
### Product Area
Alerts
Contributor guide
Research direction
No file, test, or entry point is named in the issue. Start by tracing the alert email notification flow and how environment information is available, then clarify whether the intended outcome is an environment tag, priority tag, or configurable per-environment notifications; done means the selected behavior is represented in alert emails and verified for the listed environments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100