added mysql charts info on a few charts
Costa Tsaousis committed
May 31, 2016 at 03:19 UTC
a02f7e35b5f3d4860f180a5dd459a156bafa13c4
1 file changed
+40
web/index.html
+40
@@ -1341,6 +1341,46 @@ var submenuData = {
1341
};
1342
1343
var chartData = {
1344
+ 'mysql.net': {
1345
+ info: 'The amount of data sent to mysql clients (<strong>out</strong>) and received from mysql clients (<strong>in</strong>).'
1346
+ },
1347
+
1348
+ 'mysql.queries': {
1349
+ info: 'The number of statements executed by the server.<ul>' +
1350
+ '<li><strong>queries</strong> counts the statements executed within stored SQL programs.</li>' +
1351
+ '<li><strong>questions</strong> counts the statements sent to the mysql server by mysql clients.</li>' +
1352
+ '<li><strong>slow queries</strong> counts the number of statements that took more than <a href="http://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_long_query_time" target="_blank">long_query_time</a> seconds to be executed.' +
1353
+ ' For more information about slow queries check the mysql <a href="http://dev.mysql.com/doc/refman/5.7/en/slow-query-log.html" target="_blank">slow query log</a>.</li>' +
1354
+ '</ul>'
1355
+ },
1356
+
1357
+ 'mysql.handlers': {
1358
+ info: 'Usage of the internal handlers of mysql. This chart provides very good insights of what the mysql server is actually doing.' +
1359
+ ' (if the chart is not showing all these dimensions it is because they are zero - set <strong>Which dimensions to show?</strong> to <strong>All</strong> from the dashboard settings, to render even the zero values)<ul>' +
1360
+ '<li><strong>commit</strong>, the number of internal <a href="http://dev.mysql.com/doc/refman/5.7/en/commit.html" target="_blank">COMMIT</a> statements.</li>' +
1361
+ '<li><strong>delete</strong>, the number of times that rows have been deleted from tables.</li>' +
1362
+ '<li><strong>prepare</strong>, a counter for the prepare phase of two-phase commit operations.</li>' +
1363
+ '<li><strong>read first</strong>, the number of times the first entry in an index was read. A high value suggests that the server is doing a lot of full index scans; e.g. <strong>SELECT col1 FROM foo</strong>, with col1 indexed.</li>' +
1364
+ '<li><strong>read key</strong>, the number of requests to read a row based on a key. If this value is high, it is a good indication that your tables are properly indexed for your queries.</li>' +
1365
+ '<li><strong>read next</strong>, the number of requests to read the next row in key order. This value is incremented if you are querying an index column with a range constraint or if you are doing an index scan.</li>' +
1366
+ '<li><strong>read prev</strong>, the number of requests to read the previous row in key order. This read method is mainly used to optimize <strong>ORDER BY ... DESC</strong>.</li>' +
1367
+ '<li><strong>read rnd</strong>, the number of requests to read a row based on a fixed position. A high value indicates 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 entire tables or you have joins that do not use keys properly.</li>' +
1368
+ '<li><strong>read rnd next</strong>, the number of requests to read the next row in the data file. This value 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.</li>' +
1369
+ '<li><strong>rollback</strong>, the number of requests for a storage engine to perform a rollback operation.</li>' +
1370
+ '<li><strong>savepoint</strong>, the number of requests for a storage engine to place a savepoint.</li>' +
1371
+ '<li><strong>savepoint rollback</strong>, the number of requests for a storage engine to roll back to a savepoint.</li>' +
1372
+ '<li><strong>update</strong>, the number of requests to update a row in a table.</li>' +
1373
+ '<li><strong>write</strong>, the number of requests to insert a row in a table.</li>' +
1374
+ '</ul>'
1375
+ },
1376
+
1377
+ 'mysql.table_locks': {
1378
+ info: 'MySQL table locks counters: <ul>' +
1379
+ '<li><strong>immediate</strong>, the number of times that a request for a table lock could be granted immediately.</li>' +
1380
+ '<li><strong>waited</strong>, the number of times that a request for a table lock could not be granted immediately and a wait was needed. If this is high and you have performance problems, you should first optimize your queries, and then either split your table or tables or use replication.</li>' +
1381
+ '</ul>'
1382
+ },
1383
+
1384
'system.cpu': {
1385
info: 'Total CPU utilization (all cores). 100% here means there is no CPU idle time at all. You can get per core usage at the <a href="#cpu">CPUs</a> section and per application usage at the <a href="#apps">Applications Monitoring</a> section.<br/>Keep an eye on <b>iowait</b> ' + sparkline('system.cpu', 'iowait', '%') + '. If it is constantly high, your disks are a bottleneck and they slow your system down.<br/>Another important metric worth monitoring, is <b>softirq</b> ' + sparkline('system.cpu', 'softirq', '%') + '. A constantly high percentage of softirq may indicate network drivers issues.'
1386
},