- Newest
- Most votes
- Most comments
Thanks AI - there is no MagneticStorageByteHours metric under Timestream/InfluxDB or it appears anyone else so appears you made that up or it is not enabled in my Cloudwatch
answered a year ago
To monitor disk usage for your Amazon Timestream for InfluxDB instance, you'll need to use a combination of AWS monitoring tools, as there isn't a single straightforward metric that directly shows disk utilization for Timestream.
For Timestream, storage is divided into two tiers: the memory store for recent data and the magnetic store for historical data. To get an idea of your storage usage, you should focus on monitoring the magnetic store, as it's where most of your long-term data will be stored.
Here are some steps you can take to monitor your storage usage:
-
Use Amazon CloudWatch: While you mentioned that DiskUtilization didn't change, there are other metrics you should look at. For Timestream, you should monitor the "MagneticStorageByteHours" metric. This metric represents the cumulative number of bytes stored in the magnetic tier over time.
-
Check CloudWatch Insights: In the CloudWatch console, navigate to the Insights section and look for the EC2 resource health dashboard. This may provide additional information about your instance's resource utilization.
-
Use the DescribeTable API: You can use the DescribeTable API operation to get detailed information about your Timestream table, including its storage usage. The response will include metrics about the current size of your table in both the memory store and the magnetic store.
-
Set up CloudWatch Alarms: To proactively monitor your storage usage, set up CloudWatch Alarms based on the relevant metrics. This will allow you to receive notifications when your storage usage approaches certain thresholds.
-
Create Custom Dashboards: In CloudWatch, you can create custom dashboards to visualize your Timestream storage metrics over time. This can help you track trends and predict when you might need to increase your storage allocation.
Remember that Timestream uses a tiered storage model, so the total size of your data would be the sum of data in both the memory store and the magnetic store. If you're not seeing changes in your metrics immediately after importing data, it may take some time for the metrics to update and reflect the new data.
If you're still having trouble understanding your storage usage or if the metrics don't seem to align with your expectations, it would be advisable to contact AWS support for a more detailed analysis of your specific usage patterns and billing.
Sources
How to see how big a Timestream table is? | AWS re:Post
How to add disk utilization in cloudwatch_Insights_ec2 resource health | AWS re:Post
Monitoring tools - Amazon Timestream
Timestream for LiveAnalytics magnetic storage cost | AWS re:Post
answered a year ago
Relevant content
asked 2 years ago
asked 5 months ago
asked a year ago
- AWS OFFICIALUpdated 2 years ago

Observing the same issue, disk_utilization metric always report a value of 1.
It's been 5 months and this issue still has not been fixed.