a
Amazon RDS - AllCode

AWS Well Architected Framework for RDS Metrics – AllCode

These are the metrics that you want to monitor in order to assure that you RDS is in running according to the standards for the Well Architected Framework.

Metrics Monitoring on AWS and Ensuring Optimization

While Amazon’s services can afford to withstand higher activity and can adjust to meet increased throughput, it’s still advisable to watch activity carefully.  Optimization of any applications built on this platform will lead to a lower monthly bill in the long term.  Using AWS’ Relational Database Service (RDS) does come with its own set of metrics monitoring options to show users what resources they are proactively using.

This includes:

    • CPU Utilization
    • Queries
    • Deadlocks
    • Database Connections
    • DML Throughput
    • DDL Latency
    • Available RAM
    • Row Lock Time
    • Network Throughput
    • Active Transactions

CPU Utilization

As it’s plainly stated, this is the percentage of how much the CPU’s capacity is occupied by certain resources.  Metrics are found here.

    • Environment: Dev
    • Cluster Identifier: oneriver-investor-portal-db-dev
    • Alarm: High CPU Utilization threshold reached
    • Criteria: Cpu utilization is >=25% in the last 5 mins

Queries

This metric counts the number of queries made per second.  Metrics are found here.

    • Environment: Dev
    • Cluster Identifier: oneriver-investor-portal-db-dev
    • Alarm: High number of Queries threshold reached
    • Criteria: Number of queries >=10 in the last 5 mins

Deadlocks

Deadlock occurs when there are multiple database connections running queries on the same set of data. The first thread locks row X, then the second thread locks row Y, then the first thread tries to lock row Y and waits, then the second thread tries to lock row X and waits.  Monitoring for such incidents is found here.

    • Environment: Dev
    • Cluster Identifier: oneriver-investor-portal-db-dev
    • Alarm: Deadlocks threshold reached
    • Criteria: Deadlocks >=2 in the last 5 mins

Database Connections

The number of connections to a Database instance.  All connections are logged here.

    • Environment: Dev
    • Cluster Identifier: oneriver-investor-portal-db-dev
    • Alarm: Max connections alarm threshold reached
    • Criteria: Max number of db connections is >=2 in the last 5 mins

DML Throughput

This type of throughput covers the average number of times data is inserted, updated, and deleted per second.  The average data interaction is logged here.

    • Environment: Dev
    • Cluster Identifier: oneriver-investor-portal-db-dev
    • Alarm: Low DML Throughput Threshold reached
    • Criteria: Avg number of DML <=0.5 in the last 5 mins

DDL Latency

Similar to DML Throughput, DDL Latency covers the average duration a data insert, update, or deletion constitutes.  The average data interaction duration is logged here.

    • Environment: Dev
    • Cluster Identifier: oneriver-investor-portal-db-dev
    • Alarm: High DDL Latency threshold reached
    • Criteria: Avg DDL Latency >=25 in the last 5 mins

Freeable Memory

The amount of available random access memory. For MariaDB, MySQL, Oracle, and PostgreSQL DB instances, this metric reports the value of the MemAvailable field of /proc/meminfo.  Available RAM is tracked here.

    • Environment: Dev
    • Cluster Identifier: oneriver-investor-portal-db-dev
    • Alarm: Low Freeable Memory threshold reached
    • Criteria: Freeable Memory <=500MB in the last 5 mins

Row Lock Time

{unable to find content on this category} Metrics are logged here.

    • Environment: Dev
    • Cluster Identifier: oneriver-investor-portal-db-dev
    • Alarm: Row Locks threshold reached
    • Criteria: Row Locks >=5 in the last 5 mins

Network Throughput

The amount of outgoing and inbound traffic to a specific database instance.  This includes both customer database traffic and traffic associated with monitoring and replication.  Traffic is monitored from here.

    • Environment: Dev
    • Cluster Identifier: oneriver-investor-portal-db-dev
    • Alarm: Low Network Throuput threshold reached
    • Criteria: Network Throughput is <=5 in the last 5 mins

Active Transactions

Counts the total active transactions.  Everything is logged here.

    • Environment: Dev
    • Cluster Identifier: oneriver-investor-portal-db-dev
    • Alarm: Active Transactions threshold reached
    • Criteria: Active Transactions >=10 in the last 5 mins

Select Throughput

The average number of queries made per second.  This metric is monitored from here.

    • Environment: Dev
    • Cluster Identifier: oneriver-investor-portal-db-dev
    • Alarm: Select Throughput threshold reached
    • Criteria: Select Throughput <=10 in the last 5 mins

Dolan Cleary

Dolan Cleary

I am a recent graduate from the University of Wisconsin - Stout and am now working with AllCode as a web technician. Currently working within the marketing department.

Related Articles

Top CI/CD Tools to Use in App Development

Top CI/CD Tools to Use in App Development

Modern software development requires continuous maintenance over the course of its operational lifespan in the form of continuous integration (CI) and continuous deployment (CD). It is tedious work, but helps developers worry less about critical breakdowns. Automating this cycle provides an easier means by which rollbacks can occur in the case of a bad update while providing additional benefits such as security and compliance functionality.

Top Software as a Service Companies in 2024

Top Software as a Service Companies in 2024

Spending for public cloud usage continues to climb with every year. In 2023, nearly $600 billion was spent world-wide with a third of that being taken up by SaaS. By comparison, Infrastructure as a Service only takes up $150 billion and Platform as a Service makes up $139 billion. On average, companies use roughly 315 individual SaaS applications for their operations and are gradually increasing on a yearly basis. SaaS offers a level of cost efficiency that makes it an appealing option for consuming software.

AWS Graviton and Arm-architecture Processors

AWS Graviton and Arm-architecture Processors

AWS launched its new batch of Arm-based processors in 2018 with AWS Graviton. It is a series of server processors designed for Amazon EC2 virtual machines. The EC2 AI instances support web servers, caching fleets, distributed data centers, and containerized microservices. Arm architecture is gradually being rolled out to handle enterprise-grade utilities at scale. Graviton instances are popular for handling intense workloads in the cloud.