MySQL (deprecated) 🔗
Caution
The MySQL monitor is now deprecated and will reach of End of Support on October 31st, 2024. During this period only critical security and bug fixes are provided. When End of Support is reached, the monitor will be removed and no longer be supported, and you won’t be able to use it to send data to Splunk Observability Cloud.
To monitor your MySQL databases you can use the native OpenTelemetry MySQL receiver instead. See MySQL receiver to learn more.
The Splunk Distribution of the OpenTelemetry Collector uses the Smart Agent receiver with the MySQL monitor type to retrieve metrics and logs from MySQL.
This monitor connects to a MySQL instance and reports on the values
returned by a SHOW STATUS command, which include the following:
Number of commands processed
Table and row operations (handlers)
State of the query cache
Status of MySQL threads
Network traffic
This integration is only available on Kubernetes and Linux.
Benefits 🔗
After you configure the integration, you can access these features:
View metrics. You can create your own custom dashboards, and most monitors provide built-in dashboards as well. For information about dashboards, see View dashboards in Splunk Observability Cloud.
View a data-driven visualization of the physical servers, virtual machines, AWS instances, and other resources in your environment that are visible to Infrastructure Monitoring. For information about navigators, see Use navigators in Splunk Infrastructure Monitoring.
Access the Metric Finder and search for metrics sent by the monitor. For information, see Search the Metric Finder and Metadata Catalog.
Installation 🔗
Follow these steps to deploy this integration:
Deploy the Splunk Distribution of OpenTelemetry Collector to your host or container platform:
Configure the monitor, as described in the Configuration section.
Restart the Splunk Distribution of OpenTelemetry Collector.
Creating a MySQL user for this monitor 🔗
To create a MySQL user for this monitor, run the following commands:
CREATE USER '<username>'@'localhost' IDENTIFIED BY '<password>';
-- Give appropriate permissions
-- ("GRANT USAGE" is synonymous to "no privileges")
GRANT USAGE ON *.* TO '<username>'@'localhost';
-- Permissions for the stats options
GRANT REPLICATION CLIENT ON *.* TO '<username>'@'localhost';
The new user only has enough privileges to connect to the database. Additional privileges are not required.
Note
If you want to define seperate DB names to connect to, then you have to grant at least SELECT permission to the user.
GRANT SELECT ON <db_name>.* TO '<user_name>'@'localhost';
Considerations on localhost 🔗
For connections to localhost, MySQL programs attempt to connect to
the local server by using a Unix socket file. To ensure that the client
makes a TCP/IP connection to the local server specify a host name value
of 127.0.0.1, or the IP address or name of the local server.
Configuration 🔗
To use this integration of a Smart Agent monitor with the Collector:
Include the Smart Agent receiver in your configuration file.
Add the monitor type to the Collector configuration, both in the receiver and pipelines sections.
See how to Use Smart Agent monitors with the Collector.
See how to set up the Smart Agent receiver.
For a list of common configuration options, refer to Common configuration settings for monitors.
Learn more about the Collector at Get started: Understand and use the Collector.
Example 🔗
To activate this integration, add the following to your Collector configuration:
receivers:
smartagent/mysql:
type: collectd/mysql
host: 127.0.0.1
port: 3306
username: <global-username-for-all-db>
password: <global-password-for-all-db>
databases:
- name: <name-of-db>
username: <username> #Overrides global username
password: <password> #Overrides global password
The following is a sample YAML configuration that shows how to connect multiple MySQL databases:
receivers:
smartagent/mysql:
type: collectd/mysql
host: 127.0.0.1
port: 3306
databases:
- name: <name>
username: <username>
password: <password>
- name: <name>
username: <username>
password: <password>
Next, add the monitor to the service.pipelines.metrics.receivers
section of your configuration file:
service:
pipelines:
metrics:
receivers: [smartagent/mysql]
Configuration settings 🔗
The following table shows the configuration options for this monitor:
Option |
Required |
Type |
Description |
|---|---|---|---|
|
Yes |
|
|
|
Yes |
|
The port of the MySQL instance. For example, |
|
Yes |
|
|
|
No |
|
|
|
No |
|
|
|
No |
|
|
|
No |
|
|
The nested databases configuration object has the following fields:
Option |
Required |
Type |
Description |
|---|---|---|---|
|
Yes |
|
Name of the database. |
|
No |
|
Username of the database. |
|
No |
|
Password of the database. |
Metrics 🔗
The following metrics are available for this integration:
| Name | Description | Category | Type |
|---|---|---|---|
cache_result.qcache-hits | The number of hits on MySQL query cache. | Default | cumulative |
cache_result.qcache-inserts | The number of inserts into MySQL query cache. | Default | cumulative |
cache_result.cache_size | MySQL Qcache Size | Custom | gauge |
cache_result.qcache-not_cached | The number of MySQL queries that were not cacheable or not cached. | Custom | cumulative |
cache_result.qcache-prunes | The number of queries that were pruned from query cache because of low-memory condition. | Custom | cumulative |
cache_size.qcache | The number of queries in MySQL query cache. | Default | gauge |
mysql_commands.admin_commands | The number of MySQL ADMIN commands executed | Custom | cumulative |
mysql_commands.alter_db | The number of MySQL ALTER DB commands executed | Custom | cumulative |
mysql_commands.alter_db_upgrade | The number of MySQL ALTER DB UPGRADE commands executed | Custom | cumulative |
mysql_commands.alter_event | The number of MySQL ALTER EVENT commands executed | Custom | cumulative |
mysql_commands.alter_function | The number of MySQL ALTER FUNCTION commands executed | Custom | cumulative |
mysql_commands.alter_procedure | The number of MySQL ALTER PROCEDURE commands executed | Custom | cumulative |
mysql_commands.alter_server | The number of MySQL ALTER SERVER commands executed | Custom | cumulative |
mysql_commands.alter_table | The number of MySQL ALTER TABLE commands executed | Custom | cumulative |
mysql_commands.alter_tablespace | The number of MySQL ALTER TABLESPACE commands executed | Custom | cumulative |
mysql_commands.alter_user | The number of MySQL ALTER USER commands executed | Custom | cumulative |
mysql_commands.analyze | The number of MySQL ANALYZE commands executed | Custom | cumulative |
mysql_commands.assign_to_keycache | The number of MySQL ASSIGN TO KEYCACHE commands executed | Custom | cumulative |
mysql_commands.begin | The number of MySQL BEGIN commands executed | Custom | cumulative |
mysql_commands.binlog | The number of MySQL BINLOG commands executed | Custom | cumulative |
mysql_commands.call_procedure | The number of MySQL CALL PROCEDURE commands executed | Custom | cumulative |
mysql_commands.change_db | The number of MySQL CHANGE DB commands executed | Custom | cumulative |
mysql_commands.change_master | The number of MySQL CHANGE MASTER commands executed | Custom | cumulative |
mysql_commands.check | The number of MySQL CHECK commands executed | Custom | cumulative |
mysql_commands.checksum | The number of MySQL CHECKSUM commands executed | Custom | cumulative |
mysql_commands.commit | The number of MySQL COMMIT commands executed | Custom | cumulative |
mysql_commands.create_db | The number of MySQL CREATE DB commands executed | Custom | cumulative |
mysql_commands.create_event | The number of MySQL CREATE EVENT commands executed | Custom | cumulative |
mysql_commands.create_function | The number of MySQL CREATE FUNCTION commands executed | Custom | cumulative |
mysql_commands.create_index | The number of MySQL CREATE INDEX commands executed | Custom | cumulative |
mysql_commands.create_procedure | The number of MySQL CREATE PROCEDURE commands executed | Custom | cumulative |
mysql_commands.create_server | The number of MySQL CREATE SERVER commands executed | Custom | cumulative |
mysql_commands.create_table | The number of MySQL CREATE TABLE commands executed | Custom | cumulative |
mysql_commands.create_trigger | The number of MySQL CREATE TRIGGER commands executed | Custom | cumulative |
mysql_commands.create_udf | The number of MySQL CREATE UDF commands executed | Custom | cumulative |
mysql_commands.create_user | The number of MySQL CREATE USER commands executed | Custom | cumulative |
mysql_commands.create_view | The number of MySQL CREATE VIEW commands executed | Custom | cumulative |
mysql_commands.dealloc_sql | The number of MySQL DEALLOC SQL commands executed | Custom | cumulative |
mysql_commands.delete | The number of MySQL DELETE commands executed | Default | cumulative |
mysql_commands.delete_multi | The number of MySQL DELETE MULTI commands executed | Custom | cumulative |
mysql_commands.do | The number of MySQL DO commands executed | Custom | cumulative |
mysql_commands.drop_db | The number of MySQL DROP DB commands executed | Custom | cumulative |
mysql_commands.drop_event | The number of MySQL DROP EVENT commands executed | Custom | cumulative |
mysql_commands.drop_function | The number of MySQL DROP FUNCTION commands executed | Custom | cumulative |
mysql_commands.drop_index | The number of MySQL DROP INDEX commands executed | Custom | cumulative |
mysql_commands.drop_procedure | The number of MySQL DROP PROCEDURE commands executed | Custom | cumulative |
mysql_commands.drop_server | The number of MySQL DROP SERVER commands executed | Custom | cumulative |
mysql_commands.drop_table | The number of MySQL DROP TABLE commands executed | Custom | cumulative |
mysql_commands.drop_trigger | The number of MySQL DROP TRIGGER commands executed | Custom | cumulative |
mysql_commands.drop_user | The number of MySQL DROP USER commands executed | Custom | cumulative |
mysql_commands.drop_view | The number of MySQL DROP VIEW commands executed | Custom | cumulative |
mysql_commands.empty_query | The number of MySQL EMPTY QUERY commands executed | Custom | cumulative |
mysql_commands.execute_sql | The number of MySQL EXECUTE SQL commands executed | Custom | cumulative |
mysql_commands.flush | The number of MySQL FLUSH commands executed | Custom | cumulative |
mysql_commands.get_diagnostics | The number of MySQL GET DIAGNOSTICS commands executed | Custom | cumulative |
mysql_commands.grant | The number of MySQL GRANT commands executed | Custom | cumulative |
mysql_commands.ha_close | The number of MySQL HA CLOSE commands executed | Custom | cumulative |
mysql_commands.ha_open | The number of MySQL HA OPEN commands executed | Custom | cumulative |
mysql_commands.ha_read | The number of MySQL HA READ commands executed | Custom | cumulative |
mysql_commands.help | The number of MySQL HELP commands executed | Custom | cumulative |
mysql_commands.insert | The number of MySQL INSERT commands executed | Default | cumulative |
mysql_commands.insert_select | The number of MySQL INSERT SELECT commands executed | Custom | cumulative |
mysql_commands.install_plugin | The number of MySQL INSTALL PLUGIN commands executed | Custom | cumulative |
mysql_commands.kill | The number of MySQL KILL commands executed | Custom | cumulative |
mysql_commands.load | The number of MySQL LOAD commands executed | Custom | cumulative |
mysql_commands.lock_tables | The number of MySQL LOCK TABLES commands executed | Custom | cumulative |
mysql_commands.optimize | The number of MySQL OPTIMIZE commands executed | Custom | cumulative |
mysql_commands.preload_keys | The number of MySQL PRELOAD KEYS commands executed | Custom | cumulative |
mysql_commands.prepare_sql | The number of MySQL PREPARE SQL commands executed | Custom | cumulative |
mysql_commands.purge | The number of MySQL PURGE commands executed | Custom | cumulative |
mysql_commands.purge_before_date | The number of MySQL PURGE BEFORE DATE commands executed | Custom | cumulative |
mysql_commands.release_savepoint | The number of MySQL RELEASE SAVEPOINT commands executed | Custom | cumulative |
mysql_commands.rename_table | The number of MySQL RENAME TABLE commands executed | Custom | cumulative |
mysql_commands.rename_user | The number of MySQL RENAME USER commands executed | Custom | cumulative |
mysql_commands.repair | The number of MySQL REPAIR commands executed | Custom | cumulative |
mysql_commands.replace | The number of MySQL REPLACE commands executed | Custom | cumulative |
mysql_commands.replace_select | The number of MySQL REPLACE SELECT commands executed | Custom | cumulative |
mysql_commands.reset | The number of MySQL RESET commands executed | Custom | cumulative |
mysql_commands.resignal | The number of MySQL RESIGNAL commands executed | Custom | cumulative |
mysql_commands.revoke | The number of MySQL REVOKE commands executed | Custom | cumulative |
mysql_commands.revoke_all | The number of MySQL REVOKE ALL commands executed | Custom | cumulative |
mysql_commands.rollback | The number of MySQL ROLLBACK commands executed | Custom | cumulative |
mysql_commands.rollback_to_savepoint | The number of MySQL ROLLBACK TO SAVEPOINT commands executed | Custom | cumulative |
mysql_commands.savepoint | The number of MySQL SAVEPOINT commands executed | Custom | cumulative |
mysql_commands.select | The number of MySQL SELECT commands executed | Default | cumulative |
mysql_commands.set_option | The number of MySQL SET OPTION commands executed | Custom | cumulative |
mysql_commands.show_binlog_events | The number of MySQL SHOW BINLOG EVENTS commands executed | Custom | cumulative |
mysql_commands.show_binlogs | The number of MySQL SHOW BINLOGS commands executed | Custom | cumulative |
mysql_commands.show_charsets | The number of MySQL SHOW CHARSETS commands executed | Custom | cumulative |
mysql_commands.show_collations | The number of MySQL SHOW COLLATIONS commands executed | Custom | cumulative |
mysql_commands.show_create_db | The number of MySQL SHOW CREATE DB commands executed | Custom | cumulative |
mysql_commands.show_create_event | The number of MySQL SHOW CREATE EVENT commands executed | Custom | cumulative |
mysql_commands.show_create_func | The number of MySQL SHOW CREATE FUNC commands executed | Custom | cumulative |
mysql_commands.show_create_proc | The number of MySQL SHOW CREATE PROC commands executed | Custom | cumulative |
mysql_commands.show_create_table | The number of MySQL SHOW CREATE TABLE commands executed | Custom | cumulative |
mysql_commands.show_create_trigger | The number of MySQL SHOW CREATE TRIGGER commands executed | Custom | cumulative |
mysql_commands.show_databases | The number of MySQL SHOW DATABASES commands executed | Custom | cumulative |
mysql_commands.show_engine_logs | The number of MySQL SHOW ENGINE LOGS commands executed | Custom | cumulative |
mysql_commands.show_engine_mutex | The number of MySQL SHOW ENGINE MUTEX commands executed | Custom | cumulative |
mysql_commands.show_engine_status | The number of MySQL SHOW ENGINE STATUS commands executed | Custom | cumulative |
mysql_commands.show_errors | The number of MySQL SHOW ERRORS commands executed | Custom | cumulative |
mysql_commands.show_events | The number of MySQL SHOW EVENTS commands executed | Custom | cumulative |
mysql_commands.show_fields | The number of MySQL SHOW FIELDS commands executed | Custom | cumulative |
mysql_commands.show_function_code | The number of MySQL SHOW FUNCTION CODE commands executed | Custom | cumulative |
mysql_commands.show_function_status | The number of MySQL SHOW FUNCTION STATUS commands executed | Custom | cumulative |
mysql_commands.show_grants | The number of MySQL SHOW GRANTS commands executed | Custom | cumulative |
mysql_commands.show_keys | The number of MySQL SHOW KEYS commands executed | Custom | cumulative |
mysql_commands.show_master_status | The number of MySQL SHOW MASTER STATUS commands executed | Custom | cumulative |
mysql_commands.show_open_tables | The number of MySQL SHOW OPEN TABLES commands executed | Custom | cumulative |
mysql_commands.show_plugins | The number of MySQL SHOW PLUGINS commands executed | Custom | cumulative |
mysql_commands.show_privileges | The number of MySQL SHOW PRIVILEGES commands executed | Custom | cumulative |
mysql_commands.show_procedure_code | The number of MySQL SHOW PROCEDURE CODE commands executed | Custom | cumulative |
mysql_commands.show_procedure_status | The number of MySQL SHOW PROCEDURE STATUS commands executed | Custom | cumulative |
mysql_commands.show_processlist | The number of MySQL SHOW PROCESSLIST commands executed | Custom | cumulative |
mysql_commands.show_profile | The number of MySQL SHOW PROFILE commands executed | Custom | cumulative |
mysql_commands.show_profiles | The number of MySQL SHOW PROFILES commands executed | Custom | cumulative |
mysql_commands.show_relaylog_events | The number of MySQL SHOW RELAYLOG EVENTS commands executed | Custom | cumulative |
mysql_commands.show_slave_hosts | The number of MySQL SHOW SLAVE HOSTS commands executed | Custom | cumulative |
mysql_commands.show_slave_status | The number of MySQL SHOW SLAVE STATUS commands executed | Custom | cumulative |
mysql_commands.show_status | The number of MySQL SHOW STATUS commands executed | Custom | cumulative |
mysql_commands.show_storage_engines | The number of MySQL SHOW STORAGE ENGINES commands executed | Custom | cumulative |
mysql_commands.show_table_status | The number of MySQL SHOW TABLE STATUS commands executed | Custom | cumulative |
mysql_commands.show_tables | The number of MySQL SHOW TABLES commands executed | Custom | cumulative |
mysql_commands.show_triggers | The number of MySQL SHOW TRIGGERS commands executed | Custom | cumulative |
mysql_commands.show_variables | The number of MySQL SHOW VARIABLES commands executed | Custom | cumulative |
mysql_commands.show_warnings | The number of MySQL SHOW WARNINGS commands executed | Custom | cumulative |
mysql_commands.signal | The number of MySQL SIGNAL commands executed | Custom | cumulative |
mysql_commands.slave_start | The number of MySQL SLAVE START commands executed | Custom | cumulative |
mysql_commands.slave_stop | The number of MySQL SLAVE STOP commands executed | Custom | cumulative |
mysql_commands.truncate | The number of MySQL TRUNCATE commands executed | Custom | cumulative |
mysql_commands.uninstall_plugin | The number of MySQL UNINSTALL PLUGIN commands executed | Custom | cumulative |
mysql_commands.unlock_tables | The number of MySQL UNLOCK TABLES commands executed | Custom | cumulative |
mysql_commands.update | The number of MySQL UPDATE commands executed | Default | cumulative |
mysql_commands.update_multi | The number of MySQL UPDATE MULTI commands executed | Custom | cumulative |
mysql_commands.xa_commit | The number of MySQL XA COMMIT commands executed | Custom | cumulative |
mysql_commands.xa_end | The number of MySQL XA END commands executed | Custom | cumulative |
mysql_commands.xa_prepare | The number of MySQL XA PREPARE commands executed | Custom | cumulative |
mysql_commands.xa_recover | The number of MySQL XA RECOVER commands executed | Custom | cumulative |
mysql_commands.xa_rollback | The number of MySQL XA ROLLBACK commands executed | Custom | cumulative |
mysql_commands.xa_start | The number of MySQL XA START commands executed | Custom | cumulative |
mysql_handler.commit | The number of internal COMMIT statements. | Custom | cumulative |
mysql_handler.delete | The number of times rows have been deleted from tables. | Custom | cumulative |
mysql_handler.prepare | The number of times "Prepare" phase was executed in the two-phase commit operations. | Custom | cumulative |
mysql_handler.read_first | The number of times the first entry in an index was read. | Custom | cumulative |
mysql_handler.read_key | The number of times a row was read based on a key. | Custom | cumulative |
mysql_handler.read_next | The number of requests to read the next row in key order. | Custom | cumulative |
mysql_handler.read_prev | The number of requests to read the previous row in key order. | Custom | cumulative |
mysql_handler.read_rnd | The number of requests that read a random fixed position in the data file. | Custom | cumulative |
mysql_handler.read_rnd_next | The number of requests for the next row in the data file. | Custom | cumulative |
mysql_handler.rollback | The number of requests for a rollback operation on the storage engine. | Custom | cumulative |
mysql_handler.savepoint | The number of requests to place a savepoint on the storage engine. This can be used to roll back later. | Custom | cumulative |
mysql_handler.savepoint_rollback | The number of requests to roll back to a savepoint. | Custom | cumulative |
mysql_handler.update | The number of requests to update a row in a table. | Custom | cumulative |
mysql_handler.write | The number of requests to insert a row in a table. | Custom | cumulative |
mysql_handler.external_lock | The number of external_lock occurences. | Custom | cumulative |
mysql_locks.immediate | The number of MySQL table locks which were granted immediately. | Default | cumulative |
mysql_locks.waited | The number of MySQL table locks which had to wait before being granted. | Default | cumulative |
mysql_octets.rx | The number of bytes received by MySQL server from all clients. | Default | cumulative |
mysql_octets.tx | The number of bytes sent by MySQL server to all clients. | Default | cumulative |
mysql_select.full_join | The number of joins that perform full table scans. | Custom | cumulative |
mysql_select.full_range_join | The number of joins that used a range search on a reference table. | Custom | cumulative |
mysql_select.range | The number of joins that used a range on the first table. | Custom | cumulative |
mysql_select.range_check | The number of joins without keys that check for key usage after each row. | Custom | cumulative |
mysql_select.scan | The number of joins that did a full scan of the first table. | Custom | cumulative |
mysql_sort_merge_passes | The number of merge passes done by the sorting algorithm. | Custom | cumulative |
mysql_sort.range | The number of sorts that were done using ranges. | Custom | cumulative |
mysql_sort_rows | The number of rows that were sorted. | Custom | cumulative |
mysql_sort.scan | The number of sorts that were done by scanning the table. | Custom | cumulative |
mysql_slow_queries | The number of queries that have taken more than long_query_time seconds. | Custom | cumulative |
threads.cached | The number of threads cached by MySQL for re-use on a new client connection. A MySQL thread corresponds to a single MySQL connection. | Default | gauge |
threads.connected | The number of currently open MySQL connections. A MySQL thread corresponds to a single MySQL connection. | Default | gauge |
threads.running | The number of MySQL threads that are processing a query. A MySQL thread corresponds to a single MySQL connection. | Custom | gauge |
total_threads.created | The total number of threads created by MySQL for client connections. A MySQL thread corresponds to a single MySQL connection. | Custom | cumulative |
mysql_bpool_pages.data | The number of pages in the InnoDB buffer pool containing data. The number includes both dirty and clean pages. | Custom | gauge |
mysql_bpool_pages.dirty | The current number of dirty pages in the InnoDB buffer pool. | Custom | gauge |
mysql_bpool_pages.free | The number of free pages in the InnoDB buffer pool. | Custom | gauge |
mysql_bpool_pages.misc | The number of pages in the InnoDB buffer pool that are busy because they have been allocated for administrative overhead, such as row locks or the adaptive hash index. | Custom | gauge |
mysql_bpool_pages.total | The total size of the InnoDB buffer pool, in pages. | Custom | gauge |
mysql_bpool_counters.pages_flushed | The number of requests to flush pages from the InnoDB buffer pool. | Custom | cumulative |
mysql_bpool_counters.read_ahead_rnd | The number of “random” read-aheads initiated by InnoDB. This happens when a query scans a large portion of a table but in random order. | Custom | cumulative |
mysql_bpool_counters.read_ahead | The number of pages read into the InnoDB buffer pool by the read-ahead background thread. | Custom | cumulative |
mysql_bpool_counters.read_ahead_evicted | The number of pages read into the InnoDB buffer pool by the read-ahead background thread that were subsequently evicted without having been accessed by queries. | Custom | cumulative |
mysql_bpool_counters.read_requests | The number of logical read requests. | Custom | cumulative |
mysql_bpool_counters.reads | The number of logical reads that InnoDB could not satisfy from the buffer pool, and had to read directly from disk. | Custom | cumulative |
mysql_bpool_counters.wait_free | Normally, writes to the InnoDB buffer pool happen in the background. When InnoDB needs to read or create a page and no clean pages are available, InnoDB flushes some dirty pages first and waits for that operation to finish. This counter counts instances of these waits. | Custom | cumulative |
mysql_bpool_counters.write_requests | The number of writes done to the InnoDB buffer pool. | Custom | cumulative |
mysql_bpool_bytes.data | The total number of bytes in the InnoDB buffer pool containing data. The number includes both dirty and clean pages. | Custom | gauge |
mysql_bpool_bytes.dirty | The total current number of bytes held in dirty pages in the InnoDB buffer pool. | Custom | gauge |
mysql_innodb_data.fsyncs | The number of fsync() operations so far. | Custom | cumulative |
mysql_innodb_data.read | The amount of data read since the server was started (in bytes). | Custom | cumulative |
mysql_innodb_data.reads | The total number of data reads (OS file reads). | Custom | cumulative |
mysql_innodb_data.writes | The total number of data writes. | Custom | cumulative |
mysql_innodb_data.written | The amount of data written so far, in bytes. | Custom | cumulative |
mysql_innodb_dblwr.writes | The number of doublewrite operations that have been performed. | Custom | cumulative |
mysql_innodb_dblwr.written | The number of pages that have been written to the doublewrite buffer. | Custom | cumulative |
mysql_innodb_log.waits | The number of times that the log buffer was too small and a wait was required for it to be flushed before continuing. | Custom | cumulative |
mysql_innodb_log.write_requests | The number of write requests for the InnoDB redo log. | Custom | cumulative |
mysql_innodb_log.writes | The number of physical writes to the InnoDB redo log file. | Custom | cumulative |
mysql_innodb_log.fsyncs | The number of fsync() writes done to the InnoDB redo log files. | Custom | cumulative |
mysql_innodb_log.written | The number of bytes written to the InnoDB redo log files. | Custom | cumulative |
mysql_innodb_pages.created | The number of pages created by operations on InnoDB tables. | Custom | cumulative |
mysql_innodb_pages.read | The number of pages read from the InnoDB buffer pool by operations on InnoDB tables. | Custom | cumulative |
mysql_innodb_pages.written | The number of pages written by operations on InnoDB tables. | Custom | cumulative |
mysql_innodb_row_lock.time | The total time spent in acquiring row locks for InnoDB tables, in milliseconds. | Custom | cumulative |
mysql_innodb_row_lock.waits | The number of times operations on InnoDB tables had to wait for a row lock. | Custom | cumulative |
mysql_innodb_rows.deleted | The number of rows deleted from InnoDB tables. | Custom | cumulative |
mysql_innodb_rows.inserted | The number of rows inserted into InnoDB tables. | Custom | cumulative |
mysql_innodb_rows.read | The number of rows read from InnoDB tables. | Custom | cumulative |
mysql_innodb_rows.updated | The number of rows updated in InnoDB tables. | Custom | cumulative |
Notes 🔗
To learn more about the available in Splunk Observability Cloud see Metric types
In host-based subscription plans, default metrics are those metrics included in host-based subscriptions in Splunk Observability Cloud, such as host, container, or bundled metrics. Custom metrics are not provided by default and might be subject to charges. See Metric categories for more information.
In MTS-based subscription plans, all metrics are custom.
To add additional metrics, see how to configure
extraMetricsin Add additional metrics
Troubleshooting 🔗
If you are a Splunk Observability Cloud customer and are not able to see your data in Splunk Observability Cloud, you can get help in the following ways.
Available to Splunk Observability Cloud customers
Submit a case in the Splunk Support Portal .
Contact Splunk Support .
Available to prospective customers and free trial users
Ask a question and get answers through community support at Splunk Answers .
Join the Splunk #observability user group Slack channel to communicate with customers, partners, and Splunk employees worldwide. To join, see Chat groups in the Get Started with Splunk Community manual.
