Bug #43584 | More complete Connection graph including Thread Cache information | ||
---|---|---|---|
Submitted: | 12 Mar 2009 11:24 | Modified: | 7 Aug 2009 8:57 |
Reporter: | Roger David Nay | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Enterprise Monitor | Severity: | S4 (Feature request) |
Version: | Any | OS: | Any |
Assigned to: | Andy Bang | CPU Architecture: | Any |
[12 Mar 2009 11:24]
Roger David Nay
[3 Aug 2009 20:29]
Enterprise Tools JIRA Robot
Andy Bang writes: Pushed up to revision 292. Resolved by addressing two issues: 1) Making it easier to correlate data between graphs, which we solve by renaming the graphs so they sort next to each other. 2) Making the data more consistent (i.e. Aborted_connects on the Connections graph is a counter, whereas the other items are not), which we solve by creating a new graph and moving a few items around. So we end up with the following connection-related graphs: Connections Total Threads_connected not a counter Running Threads_running not a counter Cached Threads_cached not a counter Connections - Aborted Clients Aborted_clients is a counter Connections Aborted_connects is a counter Connections - Cache Threads Created Threads_created is a counter Connections Connections is a counter Connections - Max Allowed max_connections not a counter Used Max_used_connections not a counter
[4 Aug 2009 22:47]
Enterprise Tools JIRA Robot
Keith Russell writes: Patch installed in versions => 2.1.0.1085.
[6 Aug 2009 22:15]
Enterprise Tools JIRA Robot
Marcos Palacios writes: Verified fixed in advisor bundle 2.1.0.1085.
[7 Aug 2009 8:57]
Tony Bedford
An entry was added to the 2.1.0 changelog: The connections graph did not include information from the Thread Cache graph. Connections and Thread Cache were available as separate graphs but it was difficult to compare them.