Submit a ticketCall us

Cloud Workloads: Meet Your New Hybrid IT Reality
Have you found yourself in that evolving, hybrid IT grey area and wondering if cloud workloads are now part of your purview? And if so, will monitoring cloud workloads require a new set of dedicated cloud monitoring tools? Your answers: yes, they should be, and no, they don’t.

Find out how SolarWinds® Server & Application Monitor (SAM) can help you monitor your cloud workloads side by side with your on-premises workloads. Register Now.

Home > Success Center > Database Performance Analyzer (DPA) > Missing statistics for SQL statements when DPA is monitoring a MySQL database instance

Missing statistics for SQL statements when DPA is monitoring a MySQL database instance

Created by Melanie Boyd, last modified by MindTouch on Jun 23, 2016

Views: 176 Votes: 0 Revisions: 4

Overview

If DPA is monitoring a MySQL database instance and you don't see statistics for SQL statements, use the following information to resolve the issue.

Environment

  • DPA 10.0 and later
  • MySQL

Cause 

There are some common reasons for why SQL data can be missing:

  • The MySQL performance schema is disabled.
  • MySQL does not provide statistics for SQL run in a stored procedure.
  • MySQL does not provide statistics for SQL run from a prepared statement.
  • SQL has been executed in batches.

If none of these reasons apply, SolarWinds DPA might not be getting a sufficient quantity of statement history from your MySQL instance to collate SQL statistics. We can extend the amount of statement history available by enabling a MySQL option from within SolarWinds DPA.

Resolution

Verify that the MySQL performance schema is enabled, and that the SQL is not run in a stored procedure, a prepared statement, or batches.

If none of those reasons apply, extend the amount of statement history available, by enabling the MySQL events_statements_history_long table. You can enable this table for all monitored database instances or for just a single database instance.

Enabling events_statements_history_long for all instances

  1. Log on to the SolarWinds DPA web console as an administrator.
  2. Go to the page Options > Administration > Advanced Options > System Options.
  3. Click MYSQL_ENABLE_HISTORY_LONG.
  4. From the New Value list, select Enable.
  5. Click Update.

Enabling events_statements_history_long for a single instance

  1. Log on to the SolarWinds DPA web console as an administrator.
  2. Go to the page Options > Administration > Advanced Options > DB Instance Options.
  3. Select a database instance from the list.
  4. Click MYSQL_ENABLE_HISTORY_LONG.
  5. From the New Value list, select Enable.
  6. Click Update.

 

 

Last modified

Tags

Classifications

Public