harvester · w13915984028 · Feb 2, 2026 · Feb 6, 2026 · akashraj4261 · Mar 10, 2026
diff --git a/docs/troubleshooting/monitoring.md b/docs/troubleshooting/monitoring.md
@@ -692,7 +692,7 @@ cattle-monitoring-system   prometheus-kubevirt-rules            24s  // is missi
 
 ### Root Cause
 
-When KubeVirt is newly installed or upgraded, it generates a new ConfigMap object to store the configuration. A race condition occurs within the KubeVirt operator if the `rancher-monitoring-operator` ServiceAccount object is missing/not synced from the `cattle-monitoring-system` namespace during this process. Consequently, the ServiceMonitor configuration may be excluded from the resulting ConfigMap object. 
+When KubeVirt is newly installed or upgraded, it generates a new ConfigMap object to store the configuration. A race condition occurs within the KubeVirt operator if the `rancher-monitoring-operator` ServiceAccount object is missing/not synced from the `cattle-monitoring-system` namespace during this process. Consequently, the ServiceMonitor configuration may be excluded from the resulting ConfigMap object.
 
 During the upgrade process, KubeVirt may incorrectly determine the monitoring state. Once the ConfigMap object is generated, KubeVirt does not reconcile or regenerate it until the next upgrade, unless a manual trigger is performed.
 
@@ -790,3 +790,37 @@ The workaround involves ensuring that the `rancher-monitoring-operator` ServiceA
 ### Related Issue
 
 [#9674](https://github.com/harvester/harvester/issues/9674)
+
+## The embedded grafana does not provid correct URL path for invite
-## The embedded grafana does not provid correct URL path for invite
+## The embedded grafana does not provide the correct URL path for invite
-## The embedded grafana does not provid correct URL path for invite
+## The embedded grafana does not provide the correct URL path for invite
+
+### Issue Description
+
+1. Be on Harvester Dashboard
+1. Click call-to-action/button to take us to Grafana landing page (rancher-monitoring)
+1. Login
+1. Click the gear-icon/button -> configuration -> then select 'users' tab (x-ref screengrab)
+1. Build a new user, no email
+1. Click the copy invite
+1. Notice that when pasted in the browser it is directing somewhere in-accessible by the user, for example: `http://localhost:3000/invite/3qq7sUO9n7MF3XfRH8YfDWR94pYhli`
-1. Be on Harvester Dashboard
-1. Click call-to-action/button to take us to Grafana landing page (rancher-monitoring)
-1. Login
-1. Click the gear-icon/button -> configuration -> then select 'users' tab (x-ref screengrab)
-1. Build a new user, no email
-1. Click the copy invite
-1. Notice that when pasted in the browser it is directing somewhere in-accessible by the user, for example: `http://localhost:3000/invite/3qq7sUO9n7MF3XfRH8YfDWR94pYhli`
+1. On the Harvester dashboard, click the call-to-action/button to navigate to the Grafana landing page (rancher-monitoring) and log in.
+1. Click the gear-icon/button -> configuration -> then select 'users' tab (x-ref screengrab).
+1. Build a new user, no email.
+1. Click the copy invite.
+1. Notice that when pasted in the browser it is directing somewhere in-accessible by the user, for example: `http://localhost:3000/invite/3qq7sUO9n7MF3XfRH8YfDWR94pYhli`
-1. Be on Harvester Dashboard
-1. Click call-to-action/button to take us to Grafana landing page (rancher-monitoring)
-1. Login
-1. Click the gear-icon/button -> configuration -> then select 'users' tab (x-ref screengrab)
-1. Build a new user, no email
-1. Click the copy invite
-1. Notice that when pasted in the browser it is directing somewhere in-accessible by the user, for example: `http://localhost:3000/invite/3qq7sUO9n7MF3XfRH8YfDWR94pYhli`
+1. On the Harvester dashboard, click the call-to-action/button to navigate to the Grafana landing page (rancher-monitoring) and log in.
+1. Click the gear-icon/button -> configuration -> then select 'users' tab (x-ref screengrab).
+1. Build a new user, no email.
+1. Click the copy invite.
+1. Notice that when pasted in the browser it is directing somewhere in-accessible by the user, for example: `http://localhost:3000/invite/3qq7sUO9n7MF3XfRH8YfDWR94pYhli`
+
+### Root Cause
+
+The `grafana` depolyment on Harvester is sitting behind the ingress controller. A prefix is appended to the URL automatically when user visits the grafana per guided steps from Harvester UI.
+
+However, the generated invite link is not sent to external directly, it is still a localhost based link and can't be accessed from external.
+
+### Workaround
+
+Manually append the prefix like `https://10.115.16.193/api/v1/namespaces/cattle-monitoring-system/services/http:rancher-monitoring-grafana:80/proxy/` to the invite link and remove the `http://localhost:3000`. The final link is `https://10.115.16.193/api/v1/namespaces/cattle-monitoring-system/services/http:rancher-monitoring-grafana:80/proxy/invite/smVzjAUMSx0WKfl0giG1w0zEQ0d6ID`
+
+:::note
+
+1. This workaround also applies to other `grafana` local link, the link can be accessed from external after patching the prefix.
+
+1. When the Harvester cluster is imported to `Rancher Manager`, recommend to use [Role-based Access Control](https://ranchermanager.docs.rancher.com/integrations-in-rancher/monitoring-and-alerting/rbac-for-monitoring) and disable the `grafana` password login.
+
+:::
+
+### Related Issue
+
+[#5298](https://github.com/harvester/harvester/issues/5298)
diff --git a/versioned_docs/version-v1.5/troubleshooting/monitoring.md b/versioned_docs/version-v1.5/troubleshooting/monitoring.md
@@ -790,3 +790,37 @@ The workaround involves ensuring that the `rancher-monitoring-operator` ServiceA
 ### Related Issue
 
 [#9674](https://github.com/harvester/harvester/issues/9674)
+
+## The embedded grafana does not provid correct URL path for invite
+
+### Issue Description
+
+1. Be on Harvester Dashboard
+1. Click call-to-action/button to take us to Grafana landing page (rancher-monitoring)
+1. Login
+1. Click the gear-icon/button -> configuration -> then select 'users' tab (x-ref screengrab)
+1. Build a new user, no email
+1. Click the copy invite
+1. Notice that when pasted in the browser it is directing somewhere in-accessible by the user, for example: `http://localhost:3000/invite/3qq7sUO9n7MF3XfRH8YfDWR94pYhli`
-1. Be on Harvester Dashboard
-1. Click call-to-action/button to take us to Grafana landing page (rancher-monitoring)
-1. Login
-1. Click the gear-icon/button -> configuration -> then select 'users' tab (x-ref screengrab)
-1. Build a new user, no email
-1. Click the copy invite
-1. Notice that when pasted in the browser it is directing somewhere in-accessible by the user, for example: `http://localhost:3000/invite/3qq7sUO9n7MF3XfRH8YfDWR94pYhli`
+1. On the Harvester dashboard, click the call-to-action/button to navigate to the Grafana landing page (rancher-monitoring) and log in.
+1. Click the gear-icon/button -> configuration -> then select 'users' tab (x-ref screengrab).
+1. Build a new user, no email.
+1. Click the copy invite.
+1. Notice that when pasted in the browser it is directing somewhere in-accessible by the user, for example: `http://localhost:3000/invite/3qq7sUO9n7MF3XfRH8YfDWR94pYhli`
-1. Be on Harvester Dashboard
-1. Click call-to-action/button to take us to Grafana landing page (rancher-monitoring)
-1. Login
-1. Click the gear-icon/button -> configuration -> then select 'users' tab (x-ref screengrab)
-1. Build a new user, no email
-1. Click the copy invite
-1. Notice that when pasted in the browser it is directing somewhere in-accessible by the user, for example: `http://localhost:3000/invite/3qq7sUO9n7MF3XfRH8YfDWR94pYhli`
+1. On the Harvester dashboard, click the call-to-action/button to navigate to the Grafana landing page (rancher-monitoring) and log in.
+1. Click the gear-icon/button -> configuration -> then select 'users' tab (x-ref screengrab).
+1. Build a new user, no email.
+1. Click the copy invite.
+1. Notice that when pasted in the browser it is directing somewhere in-accessible by the user, for example: `http://localhost:3000/invite/3qq7sUO9n7MF3XfRH8YfDWR94pYhli`
+
+### Root Cause
+
+The `grafana` depolyment on Harvester is sitting behind the ingress controller. A prefix is appended to the URL automatically when user visits the grafana per guided steps from Harvester UI.
+
+However, the generated invite link is not sent to external directly, it is still a localhost based link and can't be accessed from external.
+
+### Workaround
+
+Manually append the prefix like `https://10.115.16.193/api/v1/namespaces/cattle-monitoring-system/services/http:rancher-monitoring-grafana:80/proxy/` to the invite link and remove the `http://localhost:3000`. The final link is `https://10.115.16.193/api/v1/namespaces/cattle-monitoring-system/services/http:rancher-monitoring-grafana:80/proxy/invite/smVzjAUMSx0WKfl0giG1w0zEQ0d6ID`
+
+:::note
+
+1. This workaround also applies to other `grafana` local link, the link can be accessed from external after patching the prefix.
+
+1. When the Harvester cluster is imported to `Rancher Manager`, recommend to use [Role-based Access Control](https://ranchermanager.docs.rancher.com/integrations-in-rancher/monitoring-and-alerting/rbac-for-monitoring) and disable the `grafana` password login.
+
+:::
+
+### Related Issue
+
+[#5298](https://github.com/harvester/harvester/issues/5298)
diff --git a/versioned_docs/version-v1.6/troubleshooting/monitoring.md b/versioned_docs/version-v1.6/troubleshooting/monitoring.md
@@ -790,3 +790,37 @@ The workaround involves ensuring that the `rancher-monitoring-operator` ServiceA
 ### Related Issue
 
 [#9674](https://github.com/harvester/harvester/issues/9674)
+
+## The embedded grafana does not provid correct URL path for invite
+
+### Issue Description
+
+1. Be on Harvester Dashboard
+1. Click call-to-action/button to take us to Grafana landing page (rancher-monitoring)
+1. Login
+1. Click the gear-icon/button -> configuration -> then select 'users' tab (x-ref screengrab)
+1. Build a new user, no email
+1. Click the copy invite
+1. Notice that when pasted in the browser it is directing somewhere in-accessible by the user, for example: `http://localhost:3000/invite/3qq7sUO9n7MF3XfRH8YfDWR94pYhli`
-1. Be on Harvester Dashboard
-1. Click call-to-action/button to take us to Grafana landing page (rancher-monitoring)
-1. Login
-1. Click the gear-icon/button -> configuration -> then select 'users' tab (x-ref screengrab)
-1. Build a new user, no email
-1. Click the copy invite
-1. Notice that when pasted in the browser it is directing somewhere in-accessible by the user, for example: `http://localhost:3000/invite/3qq7sUO9n7MF3XfRH8YfDWR94pYhli`
+1. On the Harvester dashboard, click the call-to-action/button to navigate to the Grafana landing page (rancher-monitoring) and log in.
+1. Click the gear-icon/button -> configuration -> then select 'users' tab (x-ref screengrab).
+1. Build a new user, no email.
+1. Click the copy invite.
+1. Notice that when pasted in the browser it is directing somewhere in-accessible by the user, for example: `http://localhost:3000/invite/3qq7sUO9n7MF3XfRH8YfDWR94pYhli`
-1. Be on Harvester Dashboard
-1. Click call-to-action/button to take us to Grafana landing page (rancher-monitoring)
-1. Login
-1. Click the gear-icon/button -> configuration -> then select 'users' tab (x-ref screengrab)
-1. Build a new user, no email
-1. Click the copy invite
-1. Notice that when pasted in the browser it is directing somewhere in-accessible by the user, for example: `http://localhost:3000/invite/3qq7sUO9n7MF3XfRH8YfDWR94pYhli`
+1. On the Harvester dashboard, click the call-to-action/button to navigate to the Grafana landing page (rancher-monitoring) and log in.
+1. Click the gear-icon/button -> configuration -> then select 'users' tab (x-ref screengrab).
+1. Build a new user, no email.
+1. Click the copy invite.
+1. Notice that when pasted in the browser it is directing somewhere in-accessible by the user, for example: `http://localhost:3000/invite/3qq7sUO9n7MF3XfRH8YfDWR94pYhli`
+
+### Root Cause
+
+The `grafana` depolyment on Harvester is sitting behind the ingress controller. A prefix is appended to the URL automatically when user visits the grafana per guided steps from Harvester UI.
+
+However, the generated invite link is not sent to external directly, it is still a localhost based link and can't be accessed from external.
+
+### Workaround
+
+Manually append the prefix like `https://10.115.16.193/api/v1/namespaces/cattle-monitoring-system/services/http:rancher-monitoring-grafana:80/proxy/` to the invite link and remove the `http://localhost:3000`. The final link is `https://10.115.16.193/api/v1/namespaces/cattle-monitoring-system/services/http:rancher-monitoring-grafana:80/proxy/invite/smVzjAUMSx0WKfl0giG1w0zEQ0d6ID`
+
+:::note
+
+1. This workaround also applies to other `grafana` local link, the link can be accessed from external after patching the prefix.
+
+1. When the Harvester cluster is imported to `Rancher Manager`, recommend to use [Role-based Access Control](https://ranchermanager.docs.rancher.com/integrations-in-rancher/monitoring-and-alerting/rbac-for-monitoring) and disable the `grafana` password login.
+
+:::
+
+### Related Issue
+
+[#5298](https://github.com/harvester/harvester/issues/5298)
diff --git a/versioned_docs/version-v1.7/troubleshooting/monitoring.md b/versioned_docs/version-v1.7/troubleshooting/monitoring.md
@@ -790,3 +790,37 @@ The workaround involves ensuring that the `rancher-monitoring-operator` ServiceA
 ### Related Issue
 
 [#9674](https://github.com/harvester/harvester/issues/9674)
+
+## The embedded grafana does not provid correct URL path for invite
+
+### Issue Description
+
+1. Be on Harvester Dashboard
+1. Click call-to-action/button to take us to Grafana landing page (rancher-monitoring)
+1. Login
+1. Click the gear-icon/button -> configuration -> then select 'users' tab (x-ref screengrab)
+1. Build a new user, no email
+1. Click the copy invite
+1. Notice that when pasted in the browser it is directing somewhere in-accessible by the user, for example: `http://localhost:3000/invite/3qq7sUO9n7MF3XfRH8YfDWR94pYhli`
-1. Be on Harvester Dashboard
-1. Click call-to-action/button to take us to Grafana landing page (rancher-monitoring)
-1. Login
-1. Click the gear-icon/button -> configuration -> then select 'users' tab (x-ref screengrab)
-1. Build a new user, no email
-1. Click the copy invite
-1. Notice that when pasted in the browser it is directing somewhere in-accessible by the user, for example: `http://localhost:3000/invite/3qq7sUO9n7MF3XfRH8YfDWR94pYhli`
+1. On the Harvester dashboard, click the call-to-action/button to navigate to the Grafana landing page (rancher-monitoring) and log in.
+1. Click the gear-icon/button -> configuration -> then select 'users' tab (x-ref screengrab).
+1. Build a new user, no email.
+1. Click the copy invite.
+1. Notice that when pasted in the browser it is directing somewhere in-accessible by the user, for example: `http://localhost:3000/invite/3qq7sUO9n7MF3XfRH8YfDWR94pYhli`
-1. Be on Harvester Dashboard
-1. Click call-to-action/button to take us to Grafana landing page (rancher-monitoring)
-1. Login
-1. Click the gear-icon/button -> configuration -> then select 'users' tab (x-ref screengrab)
-1. Build a new user, no email
-1. Click the copy invite
-1. Notice that when pasted in the browser it is directing somewhere in-accessible by the user, for example: `http://localhost:3000/invite/3qq7sUO9n7MF3XfRH8YfDWR94pYhli`
+1. On the Harvester dashboard, click the call-to-action/button to navigate to the Grafana landing page (rancher-monitoring) and log in.
+1. Click the gear-icon/button -> configuration -> then select 'users' tab (x-ref screengrab).
+1. Build a new user, no email.
+1. Click the copy invite.
+1. Notice that when pasted in the browser it is directing somewhere in-accessible by the user, for example: `http://localhost:3000/invite/3qq7sUO9n7MF3XfRH8YfDWR94pYhli`
+
+### Root Cause
+
+The `grafana` depolyment on Harvester is sitting behind the ingress controller. A prefix is appended to the URL automatically when user visits the grafana per guided steps from Harvester UI.
+
+However, the generated invite link is not sent to external directly, it is still a localhost based link and can't be accessed from external.
+
+### Workaround
+
+Manually append the prefix like `https://10.115.16.193/api/v1/namespaces/cattle-monitoring-system/services/http:rancher-monitoring-grafana:80/proxy/` to the invite link and remove the `http://localhost:3000`. The final link is `https://10.115.16.193/api/v1/namespaces/cattle-monitoring-system/services/http:rancher-monitoring-grafana:80/proxy/invite/smVzjAUMSx0WKfl0giG1w0zEQ0d6ID`
+
+:::note
+
+1. This workaround also applies to other `grafana` local link, the link can be accessed from external after patching the prefix.
+
+1. When the Harvester cluster is imported to `Rancher Manager`, recommend to use [Role-based Access Control](https://ranchermanager.docs.rancher.com/integrations-in-rancher/monitoring-and-alerting/rbac-for-monitoring) and disable the `grafana` password login.
+
+:::
+
+### Related Issue
+
+[#5298](https://github.com/harvester/harvester/issues/5298)