You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our environment, we have 8 different vcenter servers due to different HCI implementations and requirements. We have all VMs imported in Icinga2 and have linked their VM object (from vspheredb) in the host asset. So one click from an alert brings you to the corresponding entry in the vspheredb module.
Right now, the VM entry only shows the host and the vcenter path where it is running on. It would be fantastic if it would also link the vcenter server where it was scanned from. If possible in a link that directly opens the (https) url to it. So one click brings you to the management interface.
Current Behavior
Only the host and the vcenter path are shown.
Possible Solution
Add a link below the host entry to show something like this: <vcenter_name>
The text was updated successfully, but these errors were encountered:
A link to to the MOB is already there, a VMRC link has been implemented in #141. I'd love to also link to the HTML5 UI, do you have an idea of how such links would look like?
Expected Behavior
In our environment, we have 8 different vcenter servers due to different HCI implementations and requirements. We have all VMs imported in Icinga2 and have linked their VM object (from vspheredb) in the host asset. So one click from an alert brings you to the corresponding entry in the vspheredb module.
Right now, the VM entry only shows the host and the vcenter path where it is running on. It would be fantastic if it would also link the vcenter server where it was scanned from. If possible in a link that directly opens the (https) url to it. So one click brings you to the management interface.
Current Behavior
Only the host and the vcenter path are shown.
Possible Solution
Add a link below the host entry to show something like this:
<vcenter_name>
The text was updated successfully, but these errors were encountered: