![]() ![]() Added fetching EXPLAIN plans for UPDATE and DELETE queries on MySQL 5.To get started contact your Account Manager or Customer Support. This is an alternate method of installation for cases where the performance_schema or pg_stat_statements are unavailable and cannot be enabled, such as with Amazon Aurora running MySQL version 5.7. We’ve added support for gathering query data from the MySQL or PostgreSQL slow query log. ![]() Select “MySQL Processlist Queries” or “PostgreSQL Stat Activity” as your category, and then select to view data by “Locked.” (To view queries stopping other queries from running, select “Locks.”) We’ve now added the reverse of that: queries which were blocked, waiting for a lock. VividCortex has historically detected and reported queries which are blocking other queries from running. You can configure alerts on these events as with any event. This is automatically enabled and it can be seen by visiting the Events page. This Event includes a link to the query that was killed as well as the query which proceeded. ![]() VividCortex now detects MySQL database deadlocks and generates an Event when one occurs. If you’d like to enable it across an entire environment, please contact Customer Support. You can change “1s” (one second) to any number you like. To enable this on a host, create or edit the configuration file for the metrics agent and add “long-running-event-threshold”: “1s”. This feature is available for MySQL and PostgreSQL. This Event includes information about the user running the query, the host executing the query, historic metrics, and a link to the query details page. Now when VividCortex detects a long running query, we can generate an Event which can trigger an alert. INSERT INTO serverseeduse (id, clientSeed, nonce, serverSeedId) VALUES (DEFAULT, 'clientSeed', DEFAULT, 1) If executed only once or after the previous query has finished, works just fine but once executed concurrently 2 or more times the deadlock happens. We’ve also added new metrics showing queries that were waiting for a lock, as well as query capture via the database slow query log. We’ve added the ability to get alerted on long running queries and database deadlocks. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |