-
Notifications
You must be signed in to change notification settings - Fork 44
Roadmap and Feature Requests
Simon edited this page Apr 9, 2015
·
7 revisions
- E-Mail notifications based on templates
- Enrich alert with fields from search
- Incident enrichment with fields from underlying alert results for more accurate incident filtering (e.g. list all incident related to a specific host)
- Use ITIL naming for impact, urgency and priority
- Fix Per-Result-Alerting
- Improve e-mail notifications
- Multiple recipients
- Add more actions
- Add more default tokes for templates (recipient, sender, user name of current assignee, ...)
- Add user name to user settings
- Code refactoring (OO-style)
- Filter criteria for notifications (e.g. only send notification when priority=high)
- Incident title
- Alert scenario auto_subsequent_resolve
- Incident Export / Batch export
- Enable/disable notifications for built-in users
- Template editor
- Incident suppression rules
- Auto resolve when custom condition is met
- Re-think settings layout
- Configurable priorities and single values in incident posture
- Add detailed permission schema
- Support for capabilities so different Alert Manager roles may be configured
- Respect permissions on alerts and user them in the alert manager
- Define capabilities to control alert manager access
- Integrate well-known Splunk permissions from alerts (saved searches)
- Custom incident handler
- Add custom python code whenever alert events occur, such as create new incident, assign to another user or change status and priority
- Manage external ticketing systems
- Support for customized workflow