https://docs.openshift.com/container-platform/4.16/observability/monitoring/troubleshooting-monitoring-issues.html 

Add new section to this page "troubleshooting alertmanager configurations" 

Detail how a user can compare the contents of the alertmanager secrets against the "running config" 

extract the secret: 
$ oc -n openshift-monitoring get secret alertmanager-main --template='{{ index .data "alertmanager.yaml" }}' | base64 --decode > alertmanager.yaml 

Pull the running config from the API:
$ oc exec -n openshift-monitoring alertmanager-main-0 – amtool config show --alertmanager.url http://localhost:9093   

In the case of user workload alertmanager configs being enabled - detail how this is a way of viewing user alertmanager config from different namespace combinded into a single config 

how do we feel about links to tools hosted externally? 
The following web based tool is invaluble in "visualizing" the alertmanager routing trees
enabling a user to test there own config inorder to see which routes a notification is leaving via

https://prometheus.io/webtools/alerting/routing-tree-editor/