# Percona MySQL InnoDB Storage Summary

**URL:** <https://forums.percona.com/t/percona-mysql-innodb-storage-summary/34845>\
**Category:** PMM 2.x\
**Tags:** pmm, mysql, percona\
**Created:** [November 7, 2024, 12:38pm UTC](https://forums.percona.com/t/percona-mysql-innodb-storage-summary/34845 "2024-11-07T12:38:12Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![adamrodrigues98](https://avatars.discourse-cdn.com/v4/letter/a/a6a055/32.png) [@adamrodrigues98](https://forums.percona.com/u/adamrodrigues98)\
**Post date:** [November 7, 2024, 12:38pm UTC](https://forums.percona.com/t/percona-mysql-innodb-storage-summary/34845/1 "2024-11-07T12:38:12Z")

</div>

## Description:

I’m having trouble displaying InnoDB Storage Summary.

## Steps to Reproduce:

MySQL \> InnoDB Details \> InnoDB Storage Summary

## Additional Information:

The necessary settings are already enabled, only the InnoDB Storage Summary menu does not display the information, I use MySQL RDS AWS.

Is there any other setting that I forgot to enable?

performance\_schema ON  
SET GLOBAL innodb\_monitor\_enable = all;  
GRANT SELECT, RELOAD, PROCESS, SHOW DATABASES, REPLICATION CLIENT ON _._ TO `pmm`@`%`

 ![size](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/3X/5/4/542d130e5acd742f37af57d8db70980c405f267d.png)

##Version:  
ProjectName: pmm-managed  
Version: 2.42.0  
PMMVersion: 2.42.0

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [November 7, 2024, 1:53pm UTC](https://forums.percona.com/t/percona-mysql-innodb-storage-summary/34845/2 "2024-11-07T13:53:36Z")

</div>

Hello @adamrodrigues98,  
When the innodb monitors are enabled, this table `information_schema.innodb_metrics` is populated with data and scrapped by PMM. Check this table has data in your RDS instance.

---

<div class="post-metadata">

**Author:** ![adamrodrigues98](https://avatars.discourse-cdn.com/v4/letter/a/a6a055/32.png) [@adamrodrigues98](https://forums.percona.com/u/adamrodrigues98)\
**Post date:** [November 7, 2024, 2:13pm UTC](https://forums.percona.com/t/percona-mysql-innodb-storage-summary/34845/3 "2024-11-07T14:13:39Z")

</div>

Hello

Yes, there is data in this table.

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [November 7, 2024, 3:41pm UTC](https://forums.percona.com/t/percona-mysql-innodb-storage-summary/34845/4 "2024-11-07T15:41:36Z")

</div>

Hmm. That’s the table which the exporter scans for data

> <https://github.com/percona/mysqld_exporter/blob/70740e148536e452af59602f5e9507358d229fce/collector/info_schema_innodb_metrics.go#L44>

Can you check the PMM agent error logs? The logs would be on the PMM server since the agent is running there for RDS.

---

<div class="post-metadata">

**Author:** ![adamrodrigues98](https://avatars.discourse-cdn.com/v4/letter/a/a6a055/32.png) [@adamrodrigues98](https://forums.percona.com/u/adamrodrigues98)\
**Post date:** [November 7, 2024, 5:12pm UTC](https://forums.percona.com/t/percona-mysql-innodb-storage-summary/34845/5 "2024-11-07T17:12:38Z")

</div>

I found some logs similar to this one.

I’ll check if it’s permission, if it is I’ll let you know the resolution here.

time=“2024-11-07T12:33:29.755+00:00” level=error msg=“ts=2024-11-07T12:33:29.755Z caller=scraper.go:145 level=error component=enhanced msg="Failed to filter log events." error="AccessDeniedException: User: arn:aws:iam::971441073540:user/monitoramento-mysql is not authorized to perform: logs:FilterLogEvents on resource: arn:aws:logs:us-east-1:971441073540:log-group:RDSOSMetrics:log-stream: because no identity-based policy allows the logs:FilterLogEvents action\n\tstatus code: 400, request id: 69a813ab-c859-4a22-b13b-880ee0c8dc7f"” agentID=pmm-server/rds component=agent-process type=rds\_exporter
