The route  monitoring/alertmanagerconfig is part of the console and should not be handled by the monitoring plugin

Comment

Reviewing tests, it looks like the Monitoring plugin is hijacking the traffic to  monitoring/alertmanagerconfig.

Steps to reproduce:

• on 4.19, go to "<cluster-console-url>/monitoring/alertmanagerconfig"
• You get redirected to alerts

Expected behavior

• on 4.19, when navigating to "<cluster-console-url>/monitoring/alertmanagerconfig" the alert manager configuration page should load, not redirect to alerts