That appears to be an Aurora MySQL-specific metric. In general, for RDS the Cloudwatch metrics reflect the features of the management service and infrastructure but not the database engine. To observe the database engine-specific metrics you would use the tooling for that specific engine. See https://aws.amazon.com/premiumsupport/knowledge-center/failed-login-rds-mysql/ for an example.
For Aurora MySQL and Aurora PostgreSQL, since Amazon develops those engines in can modify them to emit metrics directly into its monitoring infrastructure.
ALB metric equivalent of Latency metric in Classic load balancerasked 3 years ago
About expecific metric in rds awsasked 4 months ago
CloudWatch: Posted custom metric data successfully, but can't find the dataasked 4 months ago
Why the LoginFailures metric showing no data for RDS MySQL instance?asked 4 years ago
Difference and relationship between CloudWatch "monitoring type" and "metric resolution"asked 5 months ago
Redshift Metric No Data Available.asked 4 months ago
Failing CIS 3.3 even when metric filter existsasked 4 years ago
Memory metric showing in insufficient state after creation of memory metricasked 3 years ago
Cloudwatch Fees from Metric Storage Issueasked 2 years ago
Reboot an instance, with a Cloud Watch Alarms based on custom metricasked 3 years ago