uhlhosting/All STatus variables, filtered erros

## All STatus variables, filtered erros
Aborted clientsDocumentation	        10	The number of connections that were aborted because the client died without closing the connection properly.
Aborted connectsDocumentation	        1	The number of failed attempts to connect to the MySQL server.
Created tmp disk tablesDocumentation	2.8 k	The number of temporary tables on disk created automatically by the server while executing statements. If Created_tmp_disk_tables is big, you may want to increase the tmp_table_size value to cause temporary tables to be memory-based instead of disk-based.
Handler read rndDocumentation	        186.5 k	The number of requests to read a row based on a fixed position. This is high if you are doing a lot of queries that require sorting of the result. You probably have a lot of queries that require MySQL to scan whole tables or you have joins that don't use keys properly.
Handler read rnd nextDocumentation	  10.7 M	The number of requests to read the next row in the data file. This is high if you are doing a lot of table scans. Generally this suggests that your tables are not properly indexed or that your queries are not written to take advantage of the indexes you have.
Innodb buffer pool readsDocumentation	3.7 k	The number of logical reads that InnoDB could not satisfy from buffer pool and had to do a single-page read.
Key readsDocumentation	              2.7 k	The number of physical reads of a key block from disk. If Key_reads is big, then your key_buffer_size value is probably too small. The cache miss rate can be calculated as Key_reads/Key_read_requests.
Opened tablesDocumentation	          791	The number of tables that have been opened. If opened tables is big, your table cache value is probably too small.
Qcache free blocksDocumentation	      211	The number of free memory blocks in query cache. High numbers can indicate fragmentation issues, which may be solved by issuing a FLUSH QUERY CACHE statement.
Select full joinDocumentation	        5	The number of joins that do not use indexes. If this value is not 0, you should carefully check the indexes of your tables.
Slow queriesDocumentation	            1.8 k	The number of queries that have taken more than long_query_time seconds.Documentation
Sort merge passesDocumentation	      2	The number of merge passes the sort algorithm has had to do. If this value is large, you should consider increasing the value of the sort_buffer_size system variable.
	Aborted clientsDocumentation 10 The number of connections that were aborted because the client died without closing the connection properly.
	Aborted connectsDocumentation 1 The number of failed attempts to connect to the MySQL server.
	Created tmp disk tablesDocumentation 2.8 k The number of temporary tables on disk created automatically by the server while executing statements. If Created_tmp_disk_tables is big, you may want to increase the tmp_table_size value to cause temporary tables to be memory-based instead of disk-based.
	Handler read rndDocumentation 186.5 k The number of requests to read a row based on a fixed position. This is high if you are doing a lot of queries that require sorting of the result. You probably have a lot of queries that require MySQL to scan whole tables or you have joins that don't use keys properly.
	Handler read rnd nextDocumentation 10.7 M The number of requests to read the next row in the data file. This is high if you are doing a lot of table scans. Generally this suggests that your tables are not properly indexed or that your queries are not written to take advantage of the indexes you have.
	Innodb buffer pool readsDocumentation 3.7 k The number of logical reads that InnoDB could not satisfy from buffer pool and had to do a single-page read.
	Key readsDocumentation 2.7 k The number of physical reads of a key block from disk. If Key_reads is big, then your key_buffer_size value is probably too small. The cache miss rate can be calculated as Key_reads/Key_read_requests.
	Opened tablesDocumentation 791 The number of tables that have been opened. If opened tables is big, your table cache value is probably too small.
	Qcache free blocksDocumentation 211 The number of free memory blocks in query cache. High numbers can indicate fragmentation issues, which may be solved by issuing a FLUSH QUERY CACHE statement.
	Select full joinDocumentation 5 The number of joins that do not use indexes. If this value is not 0, you should carefully check the indexes of your tables.
	Slow queriesDocumentation 1.8 k The number of queries that have taken more than long_query_time seconds.Documentation
	Sort merge passesDocumentation 2 The number of merge passes the sort algorithm has had to do. If this value is large, you should consider increasing the value of the sort_buffer_size system variable.