Is this a BUG REPORT or FEATURE REQUEST?:
Bug
What happened:
When there is an invalid value passed as param [Eg: severity value as "warning" instead of "warn"] , controller will not create wavefront alert and show error in controller logs . Currently we dont see events generated for the error.
What you expected to happen:
We should see error message in the events when we use kubectl kubectl get events .
How to reproduce it (as minimally and precisely as possible):
In Alerts config , pass invalid severity value as "warning" and try to apply it.
Anything else we need to know?:
Environment:
- alert-manager version
- Kubernetes version :
$ kubectl version -o yaml
Other debugging information (if applicable):
$ kubectl logs
Is this a BUG REPORT or FEATURE REQUEST?:
Bug
What happened:
When there is an invalid value passed as param [Eg: severity value as "warning" instead of "warn"] , controller will not create wavefront alert and show error in controller logs . Currently we dont see events generated for the error.
What you expected to happen:
We should see error message in the events when we use kubectl
kubectl get events.How to reproduce it (as minimally and precisely as possible):
In Alerts config , pass invalid severity value as "warning" and try to apply it.
Anything else we need to know?:
Environment:
Other debugging information (if applicable):
$ kubectl logs