Product Version: 5.5
Expires on: 365 days from publish date
Updated: December 13, 2013
How to import and what are the prerequisites for using Liquidware Labs' Dashboards?
These are the 5 dashboards included in the Dashboard zip file. There is one bin file for each each dashboard.
- FIT UX Overview
- Strat UX Heat Map
- Stratusphere Explorer
- Strat Comparison
- Strat UX :: Pool
Each dashboard bin file is imported one at a time using the ‘Import function’ on the dashboard page in vCops.
The vCops export/import dashboard function is very particular in needing all the components in vCops before it will allow you to import the dashboard. The LWL custom dashboards have been made as generic as possible but there are still pre-requisites.
When Dashboard will not import. Error: ‘key data missing’ in vCops. List of items to check:
Each Dashboard has specific pre-requisites:
A) All of them require the LWL vCops adapter to be installed and running successfully.
B) The below have additional requirements.
- Strat UX Heat Map – Requires Machine Groups to be enabled in Stratusphere UX and valid machine groups being exported to vCops
- FIT UX Overview – Requires Intersection enabled in Stratusphere UX and valid intersection data being sent to vCOps
- Strat UX :: Pool – Requires Intersection enabled in Stratusphere UX and valid intersection data being sent to vCOps
Note: For Intersection it needs both Machine Groups and Users Groups enabled and sending valid data to vCops.
C. Checking Stratusphere UX
Step 1) In Administration go to ‘VCenter Ops Connector’ page to check the various check boxes.
Step 2) Enabling the overall checkboxes is not enough to get data in vCops. Specific user groups and/or machine groups set to export to vCops. If you are using Intersection then you need both machine and user groups. Also users need logging into the machines.
Click the user group and machine group links under the vcops tab in the admin side and then closing a machine group (usually same name as the view resource pool which is sweet) and then going Back and selecting the user group link and closing the group like 'domain users' group.
Step 2) Verify that there is CID data reporting for the machines and/or users in the groups enabled for vCops. For User Groups there needs to be Login data to occur to get data sent to vCops. The best place to look is the vCops Preview Inspector. That will show what the vCops adapter is currently sending.
D. vCops Side
The best place to go to see if you are getting Machine, User and Intersection data is Environment Overview. Then put ‘liquidware’ in the Search box. That will show all the Resource Kinds created by our adapter provided the user named it with Liquidware in the name as per the documentation.
Machine and User Group Resource Kinds.
You should see a resource kind in the list for each Machine Group and User Group that was enabled in vCops. It should be the same name. If you just see the _ALL resource kinds then data is not really being sent to vCops from UX and the Intersection dashboards won’t import.
Intersection Resource Kinds
These are the format user_name:Machine_Group
If those don’t exist in vCops then you won’t be able to import the two dashboards that require Intersection
If they do not exist but everything was enabled in Stratusphere UX then go back and check if CID data is being created, especially login records for the user. Without that the intersection resource kind won’t be created in vCops.