You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
Minutes and resolveAfterMinutes are declared as int since wavefront allows only integer values. This should be fine for single alert creation but if users wants to use go lang template to variablize based on the requirements kubectl or open api will throw an error since go lang template {{ .foo }} is a string and not an integer.
Allow Minutes and resolveAfterMinutes as custom data type StringOrInt? - May be, depends on the requirement we can figure it out
What you expected to happen:
Minutes and resolveAfterMinutes can also parameterized using Go Lang template with AlertsConfig supplying the data
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
alert-manager version
Kubernetes version :
$ kubectl version -o yaml
Other debugging information (if applicable):
- controller logs:
$ kubectl logs
The text was updated successfully, but these errors were encountered:
Is this a BUG REPORT or FEATURE REQUEST?:
Feature
What happened:
Minutes and resolveAfterMinutes are declared as int since wavefront allows only integer values. This should be fine for single alert creation but if users wants to use go lang template to variablize based on the requirements kubectl or open api will throw an error since go lang template {{ .foo }} is a string and not an integer.
Allow Minutes and resolveAfterMinutes as custom data type StringOrInt? - May be, depends on the requirement we can figure it out
What you expected to happen:
Minutes and resolveAfterMinutes can also parameterized using Go Lang template with AlertsConfig supplying the data
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
Other debugging information (if applicable):
$ kubectl logs
The text was updated successfully, but these errors were encountered: