These metrics doesn’t exist in our prometheus engine, how can we enable these to our prometheus.
mysql_global_status_innodb_max_trx_id
mysql_global_status_innodb_oldest_view_low_limit_trx_id
mysql_global_status_innodb_purge_trx_id
mysql_global_status_innodb_purge_undo_no
mysql_global_status_innodb_deadlocks
Hi @Ramyashree
Provided metrics are fetched by global_status collector.
Have you got any mysql_global_status_innodb_ metrics?
Please check errors in pmm-agent logs if collector is enabled and other metrics are fetched.
Also deadlocks value is provided by mysql_info_schema_innodb_metrics_lock_lock_deadlocks_total metric from another collector.
Thank you @Vadim_Yalovets
yes we have mysql_global_status_innodb_ metrics
But above mentioned transaction metrics doesn’t exist.
Please check if such metrics are collected by exporter.
e.g.
curl -s -u pmm:/agent_id/0b1cf56a-52b0-4d56-bd47-86b6df2b1f3d localhost:42002/metrics | egrep '_trx_id|_purge_undo_no|_innodb_deadlocks'
Hi @Vadim_Yalovets
Sorry for delayed reply few servers am able to see the response after curl, few servers am unable to see, Mysql version are 5.6 and above. please let’s us know.
Hi Ramyashree,
Please check pmm-agent logs. It could have some information regarding failed scraping.