Missing fields in Extended Support Dashboard:
In Extended Support Cost Projection, the last visual in the RDS Extended Support (Cost Projection) shows as “Fields for this visual no longer in analysis”.
There are two missing fields available. I believe the missing fields are account_name and rds_name, since similar fields are available in EKS and OpenSearch tabs.
Is there an update for this dashboard that addresses these missing values in the rds_extended_support_view Athena view?
Welcome to the Quick Sight community!
Could you please check whether the missing column(s) in your analysis are currently part of the excluded fields list in your dataset?
Whenever changes are made to a dataset, such as adding or removing fields, it’s important to follow these steps to ensure they reflect properly in the dashboard:
This process ensures your visuals won’t show “Fields for this visual no longer in analysis” due to outdated field mappings.
Thank you for your suggestion. I’ve confirmed that the fields are not excluded.
I believe the problem is the setting of ManageCUR2|no per the CloudFormation related to Deployment in Global Regions (Deployment in Global Regions - Cloud Intelligence Dashboards on AWS).
We are not yet using CUR 2.0 data for our main dashboards (CID, CUDOS), and I’m not yet ready to migrate.
I believe CUR 2.0 must be required for the RDS extended support resource level dashboard widget? I’m not certain this is the issue - all data is showing for OpenSearch and EKS dashboards.
In eks_extended_support_view View, the following block refers to details such as account_name and cluster_name:
FROM
preprocessed_eks_clusters_inventory
WHERE (collection_date = max_collection_date)
)
, eks_clusters_usage (billing_period, usage_date, payer_account_id, linked_account_id, account_name, region_code, cluster_name, k8s_version, item_description, usage_unit, resource_id, original_usage_type, usage_amount) AS (
Looking in the rds_extended_support_view, I don’t see any similar references that would join account_name or rds_name.
I’m wondering if the issue is that I’m not leveraging CUR 2.0, or whether my rds_extended_support_view can be modified.
Sorry, I’m out of ideas. I would recommend filing a case with AWS Support where we can dive into the details so that we can help you further. Here are the steps to open a support case. If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf. Hope this helps!
It’s been a while since we last heard from you. If you have any further questions, please let us know how we can assist you.
If we don’t hear back within the next 3 business days, we’ll proceed with close/archive this topic.
Thank you!
Since we have not heard back from you, I’ll go ahead and close/archive this topic. However, if you have any additional questions, feel free to create a new topic in the community and link this discussion for relevant information.
Thank you!
