The console is reporting my used SPICE capacity as 158.94GB (the aggregate Metric for SPICECapacityConsumedInMB is reporting a similar figure 163,788MB which is equivalent to 159.94GB), however when I sum the IngestionSizeInBytes of the latest of ingestions for each dataset in my account it only sums to 93.70GB, what could be the cause of the discrepancy and if the lower number is correct how do I resolve this?
Hello @swoo992, welcome to the QuickSight community.
Are you certain that you are viewing all datasets that have been ingested into your account? Whether you are an admin or not, there could easily be datasets created by other users that are not being shared with you.
If you are an admin user you can check the manage assets page to see if there are datasets ingested into SPICE that are not showing on your specific datasets page. Click the little user icon at the top right of the page and select the Manage QuickSight option. Then, in the navigation options on the left side of the screen, select Manage Assets.
Here you can click the Datasets button to find all of the datasets currently within your QuickSight account. You are able to share them with your user so you can figure out where the remaining SPICE capacity is being stored. Let me know if that helps!
Thank you @DylanM, I have checked and there are 97 datasets in total reported by the Manage Assets page and I’ve summed the IngestionSizeInBytes across 87 datasets, the missing 10 datasets were DIRECT_QUERY ones and therefore had no ingestions.
My calculation using IngestionSizeinBytes today reports 93.45GB, compared to the SPICE capacity page reporting 159.62GB
Is it possible that I’ve ended up with an orphaned dataset somehow, possibly referenced by a dashboard or an analysis preventing the SPICE capacity being reclaimed?
1 Like
Hello @swoo992, this is not the first time I have seen something like this, and I am not sure what resources could be utilizing that storage. If you want to find out more information about what is responsible for the remaining SPICE usage, it may be best to submit a support ticket.
Here are the steps for opening a support ticket - Creating support cases and case management - AWS Support . 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
They should be able to provide you with more information. I hope that helps!
@DylanM Thank you for the help, I will raise a support ticket and see how that goes.
1 Like
Hello @swoo992, sometimes it can take a bit to get a response, but they should be able to provide the information you are looking for. I’ll archive this topic for our support team as well. If you need further assistance after receiving information, please post a new question in the community and link this topic to provide relevant information. That will ensure you are at the top of the priority list for a response from one of our QuickSight experts. Thank you!