-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix grafana vm metrics 404 error in multi cluster #555
Conversation
When accessing vm metrics from Rancher to Harvester to VM, 404 error is return due to wrong appSubUrl
FYI: how to validate the fix quickly. Quick local validation of this issue, without installing a new clusterReplace the nginx related configmap, and replace the grafana POD, then check the result
|
The target of nginx map rule is to filter out multi cluster name. Seems regex Will check if Rancher multi-cluster naming will include any special chars, when not, we can further optimize&simplify the nginx rule. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mergify backport v1.2 |
✅ Backports have been created
|
When accessing vm metrics from Rancher to Harvester to VM, 404 error is return due to wrong appSubUrl
Problem:
When accessing vm metrics from Rancher to Harvester to VM, 404 error is return.
Such a field is returned:
The expected value is:
Solution:
In nginx config, add long match for http referer field, to filter the path like
kubevirt.io.virtualmachine/default/vm2
is matched by nginx rule:
In the Harvester dashboard, the vm metrics is referred as:
is matched by nginx rule:
Related Issue:
harvester/harvester#4343
Test plan:
rancher-monitoring
addon