To return expected results, you can:
Reduce the number of search terms.
Each term you use focuses the search further.
Check your spelling.
A single misspelled or incorrectly typed term can change your result.
Try substituting synonyms for your original terms.
For example, instead of searching for "java classes", try "java training"
Did you search for an IBM acquired or sold product ?
If so, follow the appropriate link below to find the content you need.
level=error ts=<timestamp> caller=main.go:314 msg="Loading configuration file failed" file=/etc/config/alertmanager.yml
err="yaml: line 5: did not find expected key"
level=error ts=<timestamp> caller=main.go:314 msg="Loading configuration file failed" file=/etc/config/alertmanager.yml
err="yaml: unmarshal errors:\n line 9: field <field_name> not found in type config.plain"
Check the output of the describe command as well as the pod log.
Use below commands for this:
kubectl -n kube-system describe pods <pod-id>
kubectl -n kube-system logs <pod-id>
If you find above error message in the log, there is a problem in the ConfigMap of your alertmanager.
Display the ConfigMap via
kubectl get cm/monitoring-prometheus-alertmanager -n kube-system -o yaml
You might see a similar output as below:
Above ConfigMap has two problems:
1. You must always ensure that the indent of all fields is appropriate. Otherwise, this could lead to errors.
In above example, the 'group_wait' field needs to be indented to be in line with the other fields.
2. The field 'severity' is not defined and therefore should not exist under alertmanager.yml -> route
The correct ConfigMap should look like this:
