How to resolve Table 'performance_schema.global_status' doesn't exist error?
This error may occur because the MySQL user given in Applications Manager for monitoring lacks SELECT privileges on performance_schema.
To fix this error, ensure performance_schema is enabled and grant SELECT on performance_schema.* to the user.
Steps to provide the permission:
1. Login to MySQL as a privileged user (e.g.,
root):mysql -u root -p
2. Grant SELECT permission on
performance_schema: GRANT SELECT ON *.* TO 'mysql_user'@'apm_host';
Replace:
-
'mysql_user'with the actual MySQL username. -
'apm_host'with the host/IP of Applications Manager.
-
3. Apply the changes:
FLUSH PRIVILEGES;
Example:
GRANT SELECT ON performance_schema.* TO 'mysqlAPMUser'@'apm-test-10';
FLUSH PRIVILEGES;
New to ADSelfService Plus?
Related Articles
How to resolve 403 Forbidden error when accessing Apache Server-status Page?
If you are receiving a 403 Forbidden error when trying to access the Apache server-status page, it's likely due to missing or incorrect configurations in your Apache server settings. The server-status page provides valuable information for monitoring ...How to view data under Session & Performance tab in MySQL monitor?
Note: If the server is a MariaDB server, check whether the SYS database is installed by executing the below query on MariaDB shell: show databases; If the output does not contain the SYS database, then install the SYS database suitable for the ...Resolving no data error for MSSQL performance metrics
Problem: If the metrics in the MS SQL monitor's 'Overview' page isn't getting populated, it might be due to any of the following reasons: - MSSQL user does not have permission to access the performance counters. - Data collected from SQL server is ...Troubleshooting Bad Request and Internal Server error
When a server responds with a Bad Request (400) or Internal Server Error (500), It typically indicates issues with how the request is being made or processed. The reasons for these errors can vary, but the most common causes are Incorrectly formatted ...How to resolve the error "ManageEngine Ruby agent configuration file does not exist in apminsight.conf" ?
After installation of the Ruby agent, please follow the steps below to ensure that the above error message does not come up: Copy the apminsight.conf file from {gem_installed_directory}/appmanager_apminsight/conf directory to application home ...