Use this metric to understand if failures are due to timeouts. Using these rates, compare with range_requests_failures.Īstra_db_range_requests_unavailables:rate1m and astra_db_range_requests_unavailables:rate5m - A calculated rate of change (over 1 minute and 5 minutes, respectively) for unavailable errors, which are a subset of total failures.
High alert on larger amounts determine potentially as a percentage of read throughput.Īstra_db_range_requests_timeouts:rate1m and astra_db_range_requests_timeouts:rate5m - A calculated rate of change (over 1 minute and 5 minutes, respectively) for timeouts, which are a subset of total failures. Using these rates, alert if the value is > 0.
Export cloudwatch metrics to prometheus drivers#
Cassandra drivers retry failed operations, but significant failures can be problematic. Using these rates, compare with write_requests_failures.Īstra_db_range_requests_failures:rate1m and astra_db_range_requests_failures:rate5m - A calculated rate of change (over 1 minute and 5 minutes, respectively) for the number of range reads that failed. Using these rates, compare with write_requests_failures.Īstra_db_write_requests_unavailables:rate1m and astra_db_write_requests_unavailables:rate5m - A calculated rate of change (over 1 minute and 5 minutes, respectively) for unavailable errors, which occur when the service is not available to service a particular request. High alert on larger amounts determine potentially as a percentage of read throughput.Īstra_db_write_requests_timeouts:rate1m and astra_db_write_requests_timeouts:rate5m - A calculated rate of change (over 1 minute and 5 minutes, respectively) for timeouts, which occur when operations take longer than the server side timeout. Using these rates, alert if the value is > 0.Īstra_db_write_requests_failures:rate1m and astra_db_write_requests_failures:rate5m - A calculated rate of change (over 1 minute and 5 minutes, respectively) for the number of failed writes. Using these rates, alert if the value is > 0.Īstra_db_read_requests_unavailables:rate1m and astra_db_read_requests_unavailables:rate5m - A calculated rate of change (over 1 minute and 5 minutes, respectively) for reads where service is not available to complete a specific request. Timeouts happen when operations against the database take longer than the server side timeout. High alert on larger amounts determine potentially as a percentage of read throughput.Īstra_db_read_requests_timeouts:rate1m and astra_db_read_requests_timeouts:rate5m - A calculated rate of change (over 1 minute and 5 minutes, respectively) for read timeouts. Using these rates, alert if the value is > 0.Īstra_db_read_requests_failures:rate1m and astra_db_read_requests_failures:rate5m - A calculated rate of change (over 1 minute and 5 minutes, respectively) for the number of failed reads. You can request that rate limits are increased for your Astra DB databases.
Phase 5: Connect client applications directly to TargetĪstra_db_rate_limited_requests:rate1m and astra_db_rate_limited_requests:rate5m - A calculated rate of change (over 1 minute and 5 minutes, respectively) for the number of failed operations due to an Astra DB rate limit.Phase 3: Enable asynchronous dual reads.Connect client applications to ZDM Proxy.Set up the ZDM Proxy Automation with ZDM Utility.Phase 1: Deploy ZDM Proxy and connect client applications.
0 kommentar(er)
