- Newest
- Most votes
- Most comments
There should be many in the different books on the tool, for the team i lead , we track the following things
Monitor cluster CPU utilization: You can set up an alarm to trigger if the average CPU utilization of the cluster exceeds a certain threshold. This can indicate that the cluster is under heavy load and may require additional resources or optimization.
Monitor queue wait time: You can monitor the average queue wait time for queries by priority. If the wait time is consistently high, it may indicate that the cluster is under heavy load or that there are blocking queries.
Monitor data scanned: You can set up an alarm to trigger if the amount of data scanned by queries exceeds a certain threshold. This can indicate that queries are performing full table scans or that the cluster is under heavy load.
Monitor disk space: You can set up an alarm to trigger if the amount of disk space used by the cluster exceeds a certain threshold. This can indicate that the cluster is running out of space and may need to be resized or that data needs to be deleted or moved to cold storage.
Monitor network throughput: You can set up an alarm to trigger if the network throughput of the cluster exceeds a certain threshold. This can indicate that the cluster is experiencing heavy network traffic and may need additional resources or optimization.
@seekrsi
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 8 months ago
I tried built a cloud watch alarm againt the redshift metric Query_waittime. this helped me to act on any monitoring the cluster behaviour better.