Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alerting: Simplify contact point template selection #87390

Closed
2 tasks
gillesdemey opened this issue May 6, 2024 · 0 comments · Fixed by #87689
Closed
2 tasks

Alerting: Simplify contact point template selection #87390

gillesdemey opened this issue May 6, 2024 · 0 comments · Fixed by #87689
Assignees
Labels
area/alerting Grafana Alerting area/frontend internal for issues made by grafanistas
Milestone

Comments

@gillesdemey
Copy link
Member

Problem

Currently selecting a template for either the body / subject of a contact point is rather error-prone.

As can be seen in the screenshot below you have to

  1. use the correct Go template syntax
  2. use the correct name of the template defined in the notification template – and these may not be the same (which is confusing).
image

Potential solution

Ideally we'd allow for the user to make a selection from a list of templates (from a combination of notification templates – keep in mind that a "notification template" can embed multiple "templates" – yes, this is confusing).

Approach

We can approach this in two phases;

  • Allow selection from a list of templates
  • Preview the selected template contents (optionally a rendered preview but TBD how that would work in the context of a contact point)

Important note

Let's keep in mind that – for any reason – the user might still want to manually fill in a value here, for example when a fixed value or inline template needs to be defined.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/alerting Grafana Alerting area/frontend internal for issues made by grafanistas
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants