EUC Metric Additions - Incomplete Setup Instructions; or incomplete placeholder table deployment. #392
Description
During the addition of the EUC Metrics to the EUC Dashboard you encounter a situation where upon following the instructions you get issues with the dataset in Quicksight importing.
Essentially the placeholder table (created by default) contains entries such as account_name which are not present in the query you are told to execute here:
https://docs.aws.amazon.com/guidance/latest/cloud-intelligence-dashboards/euc-dashboard.html
Under:
So you recieve:
COLUMN_NOT_FOUND: line 2:595: Column 'account_name' cannot be resolved or requester is not authorized to access requested resources
When you attempt to reimport the dataset post SQL query update.
That I can see there are two options here:
- Either update the instructions to include that you will need to map the account_map to the euc_metric_view yourself as part of the setup. [this is what we have done but I do not think this is the ideal path]
- Update the original deployment of the placeholder template to not have fields such as account_name but to instead pre-join the account_map to the placeholder table on the original euc_metrics_view.linked_account_id = account_map.account_id in the Quicksight dataset so it is in place from the start. It'll do nothing as it'll be joining on null, but it streamlines later deployment.
For me option 2 seems the sensible approach because it will mean any customisation users have done to their account map will have those fields present in the first SPICE import of the euc_metric_view placeholder table - so then by simply updating the query as per the current instructions would not cause the import to fail and would not require you to go into the dataset and save and republish it to update the columns in QuickSight. There is less instructions to write/follow then, and less steps the user could get wrong.
Option 1 has been really painful, QuickSight also complained the data set had changed too much on the WorkSpaces Metric page (but there did not appear to be any filters or columns in use which was not in the data set, and I manually validated all column types had stayed the same). In the end I did a cid-cmd update --force --recursive to reinstall the EUC dashboard but did not change the datasets and kept them the same and it came to life.
Side note the text above the SQL query on the instructions web page reads:
"Run the following query to update eucdashboard-metrics view in Amazon Athena, replacing the cur table name based on version of cur running."
It should read:
"Run the following query to update euc_metrics_view view in Amazon Athena, replacing the cur table name based on version of cur running."
It's a great dashboard btw - very useful. :)