Versions Compared

Old Version 25

changes.mady.by.user Nicolas Rios

Saved on

compared with

New Version Current

changes.mady.by.user Stephanie Mariscal

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This page lists all the new features and fixed issues from previous releases for SQL Diagnostic Manager for MySQL:

8.8.0 SQL DM for MySQL (March 2019)

New Features

  • SQL DM for MySQL now monitors Google Cloud SQL server Operating System metrics.
  • This release includes Google Cloud SQL server file based log monitoring for General query, Slow query, and Error log files.
Note
This release includes new registration keys. The new keys are available for registered users from our 
Newtab2
aliasCustomer Portal
urlhttps://www.webyog.com/customer
.

Fixed Issues

  •  Regular Expression can now be used for the "Queries Starting with" filter for Processlist based Sniffer.
  •  The "Flush Status" query was renamed to "Flush Local Status" in the Monitors tab.
  •  SQL DM for MySQL is no longer displaying the warning message "User does not seem to have PROCESS privileges on this host. Only user's own processes will be displayed".
  •  The message "No data to display" in the history trend analysis graph for Monitor InnoDB cache>Free Memory is no longer prompting.
  •  SQL DM for MySQL is no longer displaying the "Undefined" message when hovering over the trend graph with a Monitor value of zero.
  •  The SQL Query for the CSO Tables_Without_Constraints  was modified to excludes the views.
  •  SQL DM for MySQL now correctly raises SNMP traps/Syslog notifications when a monitor state changes from "Warning" to "Critical".
  •  The password field value is now correctly shown as a masked value.
  • The RDS Log monitoring "Test reading the file" now correctly checks for "DownloadDBLogFilePortion" permissions.  

Miscellaneous

  • The double quotes can now be used in the email subject format.
  • The MOM variable MemAvailable was added. The Javascript function for the RAM Usage monitor is modified to display appropriate value depending on the kernel.
  • The MariaDB C/C connector was upgraded.
  • SQL DM for MySQL has included an option to show truncated query/full query in the Threads page.
  • All the SQL DM for MySQL passwords are stored encrypted in the SQLite database.


8.7.0 SQL DM for MySQL (August 2018)

New Features

No New Features for this version.

Fixed Issues

  • In some rare-cases SQL DM displayed connection timeout error in Query Analyzer page.
  • SQL DM logged error “too many SQL variables” if the Custom SQL Object query returned more than 500 rows
  • Auto-Refresh interval was not getting set in Threads page.
  • In Query Analyzer, Sniffer Settings gave console error on saving.
  • OS metrics monitoring did not work with Aurora instances when the instance was  registered with IP address.
  • On killing one thread in the Threads page, 2 extra rows got removed.
  • Default notification subject is changed to SQL DM for MySQL | [$ALERT_TYPE] | [$SERVER_NAME] | [$MSG_DETAILS].
  • Now separate SNMP traps will be sent for each alertable monitor in one collection. Earlier, a single trap contained all alertable monitors.
  • When unix_socket plugin is enabled for a user then all the users were listed under the monitor “Accounts without passwords”.
  • Added more information in the Query Details popup in Query Analyzer.
  • In pages with multi-server selector, on selecting and deselecting the servers in the selector pop-up, the servers are updated/selected in the server selector field in the background.
  • In Query Analyzer and Real-Time, the metric value in the UI and in the downloaded CSV report did not match.
  • In Query Analyzer and Real-Time, column names were different in CSV report as compared to UI.
  • Diagnostic report showed wrong value for “Read file from” parameter, if log monitoring is disabled.

8.6.0 SQL DM for MySQL (April 2018)

...

Expand
title5.x SQL DM for MySQL

5.72 SQL DM for MySQL (April 2014)

Fixed Issues:

  • In rare cases, SQL DM for MySQL could not close alerts from Monitors page.
  • When monitoring MySQL v5.6 with replication using GTIDs (global transaction IDs), SQL DM for MySQL reported false notification alert for GTID counters when notifications for change in server configuration was enabled.

Miscellaneous:

  • Upgraded libraries that theoretically could be vulnerable to the 'Heartbleed' OpenSSL bug.

5.71 SQL DM for MySQL (March 2014)

New Features:

  • With only one MySQL server selected, Dashboard page will now display charts in such a way that whitespace and the need of scrolling are reduced. With more than 1 servers selected, the Dashboard charts are drawn using a vertical layout as before.
  • Real-Time interface can now show the actual query in addition to replacing literals with the "?" wildcard.

Fixed Issues:

  • Using TAGS for registered servers in order to manage access for non-admin users did not always work as expected when multiple TAGS were used.
  • Yet another fix for a LDAP group authentication issue.
  • In Real-Time interface EXPLAIN option was not available if query length was greater than 5000.
  • In Real-Time interface database and user@host were not available for aggregating queries. They are now.

Miscellaneous:

  • MySQL availability and System availability charts in Dashboard are now disabled by default. Users who want them can enable from Dashboard Customize page. We removed them primarily as they consume space in the interface and have little information that is not obvious from other charts.

5.7 SQL DM for MySQL (March 2014)

Fixed Issues:

  • 5.69 introduced an issue causing LDAP authentication to fail in some cases.

Miscellaneous:

  • Code cleanups and internal optimizations. Users having a large number of MySQL servers registered will observe a lower system load with this version due to this.

5.69 SQL DM for MySQL (February 2014)

Fixed Issues:

  • LDAP search for user in group authentication could fail with Active Directory.
  • Real-time sessions could fail under rare circumstances when two or more sessions were started at the same time.
  • Fixed a crash introduced in version 5.68.

5.68 SQL DM for MySQL (February 2014)

New Features:

  • Sniffer now shows database name in long running query notification and also in Query Analyzer interface when Processlist based sniffer is selected. Please note that Processlist only exposes this information if a USE statement is associated with the query. If a 'fully qualified tablename' is used in the query this information will be empty.

Fixed Issues:

  • Monitor's trend charts and history report charts were not displayed. This was introduced in version 5.67 of SQL DM for MySQL.
  • Significantly improved the speed of replacing literals for queries with wildcards in Query Analyzer.
  • Connection to MySQL via SSL encryption could fail with valid parameters. This bug was introduced in version 5.61 of SQL DM for MySQL.

5.67 SQL DM for MySQL (February 2014)

Fixed Issues:

  • Fixed a rare crash occurring in CSO's (Custom SQL Objects).
  • Fixed a UI issue in Realtime's lower pane. Only Safari browsers were affected.
  • SQL DM for MySQL did not retain LDAP group authentication details after restart.
  • The SQL DM for MySQL interface for specifying LDAP groups did not allow for more than 64 characters.
  • Query Analyzer did not show queries when time range was selected with slow log and general log tables (log files were not a problem) as the source for Query Analyzer.
  • CSV-reports exported from Monitors page could show wrong values for a few monitors.

Miscellaneous:

  • SQL DM for MySQL now loads list of servers interface faster.

5.66 SQL DM for MySQL (November 2013)

New Features:

  • SQL DM for MySQL can now authenticate users using LDAP user groups without the need to add them in SQL DM for MySQL.
  • Explain plan for Insert, Update and Delete queries is now available in SQL DM for MySQL Processlist page for MySQL 5.6+ servers.

Fixed Issues:

  • The fix for failing alerts for InnoDB deadlocks with MySQL 5.6 servers in 5.65 introduced a new issue where the time for the occurrence of the deadlock reported was wrong.
  • When monitoring a Galera cluster and when cluster nodes failed to connect to each others, the error sent by cluster nodes ("unknown command") could cause SQL DM for MySQL to crash.
  • When a server was deleted from SQL DM for MySQL in rare cases the corresponding data directory was not removed.

Miscellaneous:

  • Linux versions of SQL DM for MySQL now include a script that can be used for log rotation of the Monyog.log.

5.65 SQL DM for MySQL (November 2013)

Fixed Issues:

  • Parsing the output of SHOW ENGINE INNODB STATUS for InnoDB deadlocks if server was MySQL 5.6.x. For same reason alerting also failed.
  • Some counters failed to report alert conditions. This bug was introduced in version 5.62 of SQL DM for MySQL.

5.64 SQL DM for MySQL (October 2013)

Fixed issues:

  • This release includes fixes for a rare crash when deleting servers and when trying to access a SQLite database that could not be accessed for some reason.

5.63 SQL DM for MySQL (September 2013)

Fixed Issue:

  • If SQL DM for MySQL was not able to connect to a MySQL server, replication page would 'hang' and even crash in rare cases. This was introduced in version 5.62.

5.62 SQL DM MySQL (September 2013)

New Features:

  • Removed a hard coded limit (of 512) of the number of MySQL servers that could be registered with an 'unlimited server'-license. Now the restriction is solely with the implementation of the license in the license key.
  • Added and updated a few counters in order to provide more specific support for MySQL 5.6 and MariaDB 10.

Fixed Issues:

  • Cleaned up JavaScript execution running in the background that was not needed. With a large number of servers registered (from around 150 on a typical system) this could result in some slugginess in interactive parts of SQL DM for MySQL due to CPU contention.
  • Explain option was not present in processlist page for queries starting with comment.
  • On Windows 'Real_time' monitoring did not work since 5.61.
  • Rendering of replication page failed if GTID (Global Transaction ID) mode was enabled for MySQL Slaves.
  • Resolving the IP from a host name happened multiple times during display of replication page what could slow down rendering of replication page noticeably on some environments.
  • Some Dashboard charts could show incorrect data.
  • Dashboard failed to render charts when based on a counter saved without caption, series caption and series values.
  • When restarting SQL DM for MySQL it would perform a SQLite Schema upgrade even if it was not required. Version 5.61 was affected.

5.61 SQL DM for MySQL (August 2013)

Miscellaneous:

  • MySQL 3.23 and 4.0 servers are no longer supported and an attempt to register such will be denied.

5.6 SQL DM for MySQL (August 2013)

New Features:

  • SQL DM for MySQL supports LDAP authentication for login into SQL DM for MySQL interface. This is available only in Ultimate version of SQL DM for MySQL.
  • Added a feature in Query Analyzer to include or exclude queries based on the search string / regular expression.

Fixed Issues:

  • Monitor trend charts were not updating in realtime.
  • Tooltips were truncated in DiskInfo's table information.
  • In Sniffer, "Queries starting with" option was not working properly if query started with comment.
  • Queries starting with a comment did not show EXPLAIN option in the Real Time interface.
  • Fixed a crash when viewing replication page if slave details were not properly specified (any detail NULL).

5.58 SQL DM for MySQL (April 2013)

New Features:

  • Added a feature in realtime to include or exclude queries based on the search string / regular expression.

Fixed Issues:

  • Purging mechanism was not working properly (this bug was introduced in version 5.57 of SQL DM for MySQL).
  • Tag/Group names are in alphabetical order now.
  • SQL DM for MySQL can now "Kill query" on Amazon RDS instances.
  • The rendering of Dashboard page is further improved.

5.57 SQL DM for MySQL (March 2013)

Fixed Issues:

  • The rendering of Monitors and Dashboard page was slow with large number of servers both registered and selected and when multiple users were connected simultaneously displaying the page. It could take one minute or more in some cases. It is now a matter of seconds.
  • With a large number of servers registered, editing details for one was slow. Also this could take around 1 minute, and the improvement is in the same range as above.
  • Event manager's database (Events.data) is now moved from global level to server level in order to prevent locking problems with a large number of servers. SQL DM for MySQL will migrate data first time it starts after the upgrade.
  • Fixed a multi-threading issue that in rare cases could crash SQL DM for MySQL while registering more than one server at the same time.
  • Fixed a rare crash in SQL DM for MySQL while viewing replication tab.
  • Fixed a rare crash in SQL DM for MySQL while resolving CSOs ("Custom SQL Objects").
  • SQL DM for MySQL could fail to send mail alerts if a single mail contained alerts for more than one monitor.
  • SQL DM for MySQL was showing errors in Query Analyzer, Realtime and Processlist pages when a query contained characters used for specifying HTML tags.
  • If a registered server was not a slave but marked as such in Advanced Settings .. Replication, SQL DM for MySQL was leaking connections every time it was collecting data and finally connections (from SQL DM for MySQL as well as other clients) could fail due to 'max_connections' setting being exceeded.
  • For MySQL InnoDB-related monitors were showing "(n/a)". The reason was removal of the 'have_innodb' server variable in MySQL 5.6.

5.56 SQL DM for MySQL (December 2012)

Fixed Issues:

  • Fixed a memory leak when reading MySQL server logs through SFTP.
  • Fixed a multi-threading issue that in rare cases could crash SQL DM for MySQL running on Linux while reading the MySQL error log.
  • "Apply settings to all the servers with same tags" was not working when data collection was disabled globally.
  • The fix in 5.55 for indented display of a slave compared to its master was not complete. Proper indentation could still fail.

5.55 SQL DM for MySQL (December 2012)

Fixed Issues:

  • In the replication page a slave was not displaying indented compared to its master as it should if slave and master were running on same host.
  • Fixed a multi-threading issue that in rare cases could crash SQL DM for MySQL if the Monitors page was viewed simultaneously in multiple browsers.
  • Stability fixes for issues found during internal stress-testing and code review. No crash, slowdown ('hang') or similar was reported due to any of those, but it could theoretically happen under specific and rare circumstances.

5.54 SQL DM for MySQL (November 2012)

Fixed Issues:

  • Sometimes SQL DM for MySQL could hang while editing server's tag.
  • Processlist did not show "view query" for prepared statements.

5.53 SQL DM for MySQL (November 2012)

New Features:

  • Added monitors for monitoring a galera-based cluster. These monitors do not display as default but there is a 'Galera' monitor group that can be unhidden from Tools .. Manage Monitor Groups.

Fixed Issues:

  • Authentication to SMTP servers could fail with very long passwords. Also authentication with Amazon SES could fail.
  • When saving a connection Monyog could apparently 'hang' for a while.
  • With a large number of sample points displayed in Dashboard, loading of the page was slow. It could take up to around 1 minute in some cases. Now it is a few seconds.
  • SSH keys could be 'forgotten' after a Monyog restart.
  • Fixed a rare crash when editing server details.
  • In the 'Real Time' interface the option to EXPLAIN queries did not display in Internet Explorer 8.
  • For non-admin users, the replication tab was displaying all slave servers instead of showing only those servers which the user has access to.
  • Internal optimizations, library upgrades etc.

5.52 SQL DM for MySQL (October 2012)

Fixed Issues:

  • When upgrading to SQL DM for MySQL 5.51 admin rights for users with such failed to be migrated. This release fixes this for both users that have already upgraded to 5.51 and those that have not.

5.51 SQL DM for MySQL (October 2012)

New Features:

  • Added a number of monitors and advisors - mostly based on metrics exposed by MySQL 5.5+.
  • In the 'Real Time' interface user may now define the threshold for when a query should be considered slow. Lowest possible setting is 1 second.
  • In the 'Real Time' interface queries are now truncated after 5000 characters. Before it was 1000.
  • 'queries' and 'slow queries' can now be exported to CSV in the 'Real Time' interface.
  • Original query formatting is now retained in 'Real-Time'.
  • User Manager has added a privilege to allow (or not) to 'view literals' in Query Analyzer page for non-admin users. This can be used for blocking access to read sensitive data for such users and still giving them access to use the Query Analyzer.
  • Multiple saved Real-Time sessions can now be viewed at a time.
  • Added a 'thread count' showing number of currently running threads on 'Processlist' page.

Fixed Issues:

  • In the 'Real Time' interface displaying large BULK INSERTS was slow.
  • Logging out from SQL DM for MySQL while 'Real Time' was populating could crash SQL DM for MySQL. Linux - and not Windows - was affected.
  • In the replication overview page SQL DM for MySQL will now show 'binlog' file name and it's position wherever it applies (where binlogging is enabled). Before it was showing only for master servers.
  • In the Monitors page the percentage of SELECTS did not display. This was unlike INSERTS, DELETES and UPDATES .
  • A 'Long running query' email alert has added a note clarifying that when the alert was sent the query may still be running. Before it could be understood like the alert was sent after query had completed.

5.5 SQL DM for MySQL (September 2012)

New Features:

  • Added a new major feature called ‘Real-Time’ to monitor MySQL. This feature details the top 200 queries, slow queries, locked queries, locking queries, tables, databases, users, hosts and query states in real time. Information is retrieved from MySQL every one second. Queries taking more than 10 seconds to execute are considered as slow queries. Note that SQL DM for MySQL depends on the ‘InnoDB Plugin’ (optional with recent MySQL 5.1 versions, standard with higher MySQL versions) to get information on locked and locking queries. Refer
    Newtab2
    aliasMySQL docs
    urlhttp://dev.mysql.com/doc/innodb-plugin/1.0/en/innodb-plugin-introduction-obtaining.html
    for more information on InnoDB plugin. Also note that constants listed here are currently 'hard-coded' but we plan to implement user settings. 'Real-Time' is an Enterprise and Ultimate feature.
  • Optimized Monitors page to retrieve and display data approximately 10 times faster than before
  • Added an option to choose verbosity of email notifications. 'lesser verbosity' is in particular relevant if you receive mails on a mobile phone or another small handheld device.
  • Added 'Monitor level' email-address alert setting. If an email address is specified for a specific monitor, notification will be sent to that particular email-address when the monitor is alertable in addition to the email address specified globally for the server.
  • In the MySQL query log settings page, the 'file path' field for general query as well as slow query log was disabled for MySQL versions lesser than 5.1.6.

5.3 SQL DM for MySQL (July 2012)

New Features:

  • Introduced support for 'native' MySQL SSL-encryption with direct MySQL connections.
  • SQL DM for MySQL now fully supports IPv6 (Internet Protocol Version 6).
  • History-trends have been optimized to retrieve data faster than it was before. With large data sets this results in a speed improvement in the range of a factor ~25.
  • Passwords for SQL DM for MySQL users are no longer stored in clear text. A hash is stored (for admin user in MONyog.ini - for other users in the embedded database). Also MySQL passwords as well as SSH/SSL keys, certificates and passphrases are now stored obfuscated. First time SQL DM for MySQL starts after upgrading from a version using clear text storage it will rewrite passwords etc. to the hashed/obfuscated representation.
  • Added a Linux counter "Load Average" as exposed by the Linux kernel in /proc/loadavg.

Fixed Issues:

  • Fixed a memory leak with SSH key based authentication.
  • If HTML tags were a part of long running query, the notification email format was getting distorted.
  • MySQL connection through SSH tunnel never re-established connection in Sniffer module when the connection failed for the first time
  • Filter settings in the sniffer defined on a (MySQL) user with a SPACE character in its name did not work as expected.
  • UI fixes.

5.21 SQL DM for MySQL (June 2012)

New Features:

  • The Monyog API was rewritten and enhanced with more options. Options now include calls to enable/disable data collection, sniffer, notifications etc. for servers by either specifying a server name or a server tag. The old API calls have been blocked.

Fixed Issues:

  • Notification emails were not being sent when the number of file descriptors used by SQL DM for MySQL exceeded a certain number.
  • Fixed a bug with the Custom SQL monitor where no data was being displayed in the Monitors page when all the columns retrieved by the Custom SQL were specified as Key Columns.
  • Increased readability by improving SNMP trap format.
  • UI fixes and enhancements.

Miscellaneous:

  • Testing slave connections has been moved to replication monitoring settings. Prior to this release it was in 'MySQL settings' tab making it necessary for users to switch between tabs for testing slave connections.

5.2 SQL DM for MySQL (May 2012)

IMPORTANT note:

  • This release requires a new registration code. Neither the 5.1x nor the pre-5.1x key will work with this. Registered customers will get the new code from our Customer Portal. Please have the new code available before installing. Until SQL DM for MySQL is registered with new keys, it will not be collecting data from your servers.

New Features:

  • Added filter for including or excluding specific hosts and(or) users in Slow log analysis.
  • Added and modified a few Monitors related to Replication, InnoDB and Security. Most of this utilizes metrics exposed by MySQL from version 5.5 .
  • Added a preconfigured Custom SQL Object (CSO) for Percona Servers exposing the most written and most read tables.
  • There is now session-wide persistence while sorting columns in Query Analyzer.
  • Improved error messages in Query Analyzer and Wayback machine.
  • Usability enhancements, GUI fixes and internal optimizations.

Fixed Issues:

  • SQL DM for MySQL was not working while behind Apache configured as a reverse proxy. This bug was introduced in version 5.0 of SQL DM for MySQL.

5.12 SQL DM for MySQL (April 2012)

Fixed Issues:

  • Sometimes the default landing page failed to load after a log in. A refresh was necessary. This was introduced in version 5.0 of SQL DM for MySQL.
  • Closed alerts could reappear in the Monitors page after an unsuccessful data collection and MySQL restart.

5.11 SQL DM for MySQL (April 2012)

IMPORTANT note:

  • This release requires a new registration code. Registered customers will get the new code from our Customer Portal. Please have the new code available before installing. Until SQL DM for MySQL is registered with new keys, it will not be collecting data from your servers.

New Features:

  • Introduced tag level customization in SQL DM for MySQL Monitors. SQL DM for MySQL tags for servers are now available as Monyog Object Model variable (MONyog.Connections.TagName returns an array of tag names defined for a server). Documentation has examples on how to use it in scripting. Also see the note on 'Native JavaScript properties' support in next point below.
  • Native JavaScript properties (like length, indexOf, splice etc) are now fully supported in Monitors and Dashboard. Note that 'indexOf' is required to check for individual tags from the array exposed by Monyog.Connections.TagName (see point above) in case there is more than one tag.
  • Optimized Dashboard page to retrieve information faster.
  • Auto-registered slaves will now have server names as their host names as default.
  • Auto registering slaves will now assume the SSH host name of the slaves to be same as that of MySQL host. Before this the slaves' SSH hosts were assumed to be the same as that of the master.

Fixed Issues:

  • On SQL DM for MySQL restart, server edit, SQLite vacuum and MySQL restart there were 2 consecutive data collections with a short time interval. This could skew charts and MySQL metrics. Now SQL DM for MySQL collects data 2 consecutive times only when required - i.e during the first collection and after an unsuccessful data collection.
  • Exporting charts as PNG exported as JPEG instead in Monitors page. This bug was introduced in version 5.0 of SQL DM for MySQL.
  • UI fixes.

Miscellaneous:

  • Increased SQL DM for MySQL session timeout from 30 minutes to 8 hours (the MySQL default).

5.1 SQL DM for MySQL (March 2012)

IMPORTANT note:

  • This release requires a new registration code. Registered customers will get the new code from our Customer Portal. Please have the new code available before installing. Until SQL DM for MySQL is registered with new keys, it will not be collecting data from your servers.

New Features:

  • In the 'Disk Info' page, clicking on a donnut chart in the Database level of a server will now drill down to table level.
  • Query Analyzer' now has information on Average rows sent & examined while analyzing Slow Query Log. Those options has been hidden in version 5.0 and seen only in "Query details" pop up, now in v5.01 users can view those columns in QA output along with "Query details" pop up.
  • Comparison of MySQL server configuration of multiple servers side by side is now faster in the 'Server Config' page.

Fixed Issues:

  • The 'login' page sometimes did not work in some 'minor' IE 8 builds (if not updated with latest patches from Microsoft). Same could happen with Google Chrome that were not up to date. This happened due to 'Google Gears' (that is no long part of Chrome). It now will work with all IE8 builds and Chrome from version 9.x (current is 17.x) - also with 'Gears'.
  • MySQL server configuration could show incorrect values if MariaDB Servers were compared in the 'Server Config' page.
  • A MySQL server that was a master and a slave at the same time was not showing the slave status in the 'Replication' tab even if it was marked as a slave in 'Register Server'.
  • In the 'Replication' tab of SQL DM for MySQL the display of binlog_do_db and binlog_ignore_db settings were interchanged.
  • On a fresh installation the default SQL DM for MySQL port was 8888. This was introduced in 5.0. Its now reverted back to 5555.
  • Sometimes queries could fail to display in 'Wayback Machine' interface.
  • In 'Monitors' page - History/Trend view charts did not plot if data series contained '(n/a)' value(s).

Miscellaneous:

  • Internet Explorer 6.x and 7.x are no longer supported. And actually this should have been announced in 5.0 GA release notes, but it was missed (it was announced in 5.0 beta1 release notes however).

5.0 SQL DM for MySQL (February 2012)

UI Enhancements:

  • Introduced a left panel that contains the list of servers registered in SQL DM for MySQL, 'Tools' & 'Customize'. The 'List of servers' page has been removed. Users can now select/unselect servers from this panel.
  • Previously available icons for Edit server/Duplicate server/Diagnostic reports etc now appear as a drop down menu next to each server.
  • Previously the 'Customization' page appeared under 'Tools', now it appears as 'Customize' on the left panel.
  • 'Manage changed Monitor/Advisors & Dashboard charts' are now available as 'Manage changes' under 'Customize'.
  • 'Manage Custom SQL Objects' are now available under 'Manage changes'.
  • The Global Notifications come on the top right hand corner before the help button.
  • Pagination in Query Analyzer page. This removes the limitation of 200 queries in the result set.
  • 'Monitors' is now the default landing page.

New Features:

  • Added an option to add users to admin group.
  • Columns in the replication tab can now be sorted.
  • Register/Edit server page now has tabbed interface which eases navigation.

Enhancement:

  • Improved browser level caching.

Miscellaneous:

  • The Monyog API responses are now in the following JSON format: {"STATUS": "SUCCESS/FAILURE", "RESPONSE" : ""}
  • Query Analyzer will now display query text up to 5000 characters. (before it was 2000)

...

Expand
title2.x SQL DM for MySQL

2.9 SQL DM for MySQL (December 2008)

New Features:

  • This release adds a 'base time' setting in SQL DM for MySQL. This setting (if defined by user) will be used for calculation of uptime-based counters. The reason for this implementation is that if FLUSH STATUS is executed with a MySQL server, specific server status variables will be reset to the same value as would be after a server restart. However the 'uptime' status variable itself is not affected by FLUSH STATUS. And as uptime-based counters will relate the value of cumulative status variables with some initial time, using the 'uptime' variable as the initial time will result in calculation of misleading values if FLUSH STATUS was executed. So to get true uptime-based counters in SQL DM for MySQL with servers that do not support the 'uptime_since_flush_status' variable (and currently only 5.0 COMMUNITY servers from 5.0.37 do - not ENTERPRISE servers and not any other major branch than 5.0 and also not 5.0 before 5.0.37) you will need to define a 'base time' in SQL DM for MySQL greater than or equal to the time where FLUSH STATUS was executed last time. Also you can now discard data older than a specific time by using this setting. Refer to documentation for full details.
  • Improved the purging logic with the Monyog embedded database. Now also system CPU load is considered and purging operations will be skipped if CPU is high. This is a further improvement to the change in purging logic introduced in version 2.5.
  • SQL DM for MySQL can now be running behind an Apache server configured as 'reverse proxy'. Before this release SQL DM for MySQL JavaScript was not accessed due to absolute paths, as a result SQL DM for MySQL pages were not displaying properly.

Fixed Issues:

  • Fixed high CPU usage in the 'query sniffer' if sniffer "Minimum time taken" value was set to "0" (or left blank).

2.83 SQL DM for MySQL (November 2008)

Fixed Issues:

  • SFTP log downloads used excessive memory on Linux.
  • Version 2.82 introduced an unresolved dependency with a libcrypt library on some Linux distros (including some CentOS and OpenSuSE distros).
  • Installation on Windows 2000 could fail due to a dependency on a .dll not standard on this Windows version. Also this was introduced in 2.82.
  • The status indicator for log downloads could display wrong for large files (> 2 GB).

2.82 SQL DM for MySQL (October 2008)

Fixed Issues:

  • SFTP log downloads failed with the Bitvise 'WinSSHD' SSH implementation for Windows.

2.81 SQL DM for MySQL (October 2008)

Fixed Issues:

  • Fixed an issue where data collection would continue to fail with 'database locked' error message in the log. We now roll back the query generating the lock and collection can continue (this was reported happening by a single user (only) after SQL DM for MySQL upgrade).

2.8 SQL DM for MySQL (September 2008)

New Features:

  • Added new monitoring module displaying disk usage information for databases and tables.
  • Display of slow log data in Log Analyzer had added more information (about when query occurred, information about number of rows examined and sent).

Fixed Issues:

  • When a multibyte character was used in a connection name the display would garble and also the connection could not be deleted from GUI.
  • When connection was not available the caption for counters should display "n/a". Since 2.71 it would instead display a string exposing an internal value (example: "NumCounterWithSeconds").

2.72 SQL DM for MySQL (September 2008)

Fixed Issues:

  • On 64 bit Linux systems running SQL DM for MySQL 64 bit builds queries could be considered identical by Log Analyzer even if they were not.
  • Authentication failed if the "#" character was used in password.

2.71 SQL DM for MySQL (September 2008)

Fixed Issues:

  • Fixed some issues with JSON strings that could prevent objects in the SQL DM for MySQL browser interface to populate with data. Most important 'Monitors/Advisors' page would fail to display if a username contained a doublequote character.

2.7 SQL DM for MySQL (September 2008)

New Features:

  • CPU optimizations in both SQL DM for MySQL (server) process (in particular when 'Monitors/Advisors' page was being viewed) and browser processes (viewing Dashboard could cause high CPU usage in Firefox browser in particular).

Fixed:

  • Fixed a dependency with the SSH library that could cause failure to install in Win2K. This was an issue with the updated SSH library introduced with version 2.5.

Miscellaneous:

  • The RPM installer scripts for Linux was updated in various ways. This solves issues on specific distributions including: 1) Uninstall with the SuSE/YaST 'software management' GUI was not possible. 2) It was not always possible to install on top of a running SQL DM for MySQL service - sometimes it was necessary to stop service manually before upgrading. Also note: when updating from trial to single/multi server or from single server to multi server it is still necessary to uninstall the old version first. And when installing this version any older version will have to be removed with the "rpm -e ..." command in advance (distribution-specific GUI tools may not work with versions before this one, so please use the RPM console command). We apologize for this but there is no other way.

2.6 SQL DM for MySQL (August 2008)

New Features:

  • Log Analyzer code has been completely refactored resulting in better performance and stability and more maintainable code.
  • The progress indicator for downloads in Log Analyzer page is now a true quantitative progress bar.
  • Error messages in Log Analyzer were rewritten. Every single possible error is now differentiated by a specific message providing help for the situation.

Fixed Issues:

  • With SFTP connection to the log file selecting "ALL" for log size to be downloaded in Log Analyzer page could have the result that the log file download would last forever.
  • Analyzing log chunks containing BULK INSERT statements could in special situations cause a program crash.
  • "Group by" option in history/trends page could deliver incorrect results if MySQL and SQL DM for MySQL were using different time-zones.
  • Fixed a bug with resolvement of time in log analyzer that could result that no queries or less queries than what should be were returned. The most recent queries would sometimes not be shown. Issue was only if log was retrieved with SFTP.
  • When retrieving logs stored in tables the substitution of literals would fail for binary data .
  • Installing a RPM multi/single server builds on top of a trial build (and vice versa) resulted in that they were installed in parallel. Also on SUSE SQL DM for MySQL was not registered with the correct run level. The RPM has been updated to fix this.
  • When downloading a log SQL DM for MySQL would continue to download in the background until end of file even after STOP button was clicked.
  • In the display of queries from the Processlist page special characters could garble.
  • Also in Log Analyzer page special characters would not always be identified correctly. This bug also affected records with binary data. Both display and grouping was affected (depending on where those occurred - in plain strings or in identifiers).
  • Repeatedly switching between sorting and show details for a slow query log in Log Analyzer could in certain situations crash SQL DM for MySQL.

Miscellaneous:

  • Display of servers is now sorted in the order of the server/connection name. Earlier the internal ID was used for sorting. Also note that now no SQL DM for MySQL restart is required for changing sort order. A connection rename alone will do.

2.51 SQL DM for MySQL (July 2008)

Fixed Issues:

  • Depending on the chosen installation environment and the Linux distro, the RPM build might not install 'on top' of a previous installation. Before installing a new version it was necessary to uninstall the previous version. This is a limitation with all RPM builds released till now. From this build and onwards it will always be possible to 'upgrade on top' of a previous version. Note: this was an issue with the RPM installer - not the program binary. There is no change in the binary as such and also no change in the Windows installer and the .gz build for Linux.

2.5 SQL DM for MySQL (July 2008)

New Features:

  • MySQL Server Log Analysis: SQL DM for MySQL is now able to retrieve (completely or partially) the General Query Log and the Slow Query Log (whether stored as files or tables on the server) from the MySQL servers it connects to and analyze them.
  • Query Sniffer: A 'query sniffer' is implemented that will record a 'pseudo log' on the client (SQL DM for MySQL) side. The sniffer is useful when 'real logs' are not available, but also the sniffer has various filtering options what will sometimes make it more useful than the 'real server logs' also when they are available.

The log analysis component will (whether operating on a 'real log' or a 'sniffer pseudo log') only display identical queries once but print a 'count' for every query. Important information (like execution time, number of instances for this query etc.) will be displayed in a sortable table view.

In the log analyzer 'Filter settings' (not to be confused the filter settings of the 'query sniffer') there further is an option to 'replace literals'. The purpose of this option is to eliminate small differences between 'almost identical' queries. Currently 'quoted strings' and numbers are replaced with the dummy string 'XXX' only. We may extend this feature to support more (like special keywords and functions (like NULL, now()), operators etc.) in the next releases. It will depend on the demand for this as compared to the demand for other features. Also note that the current implementation has the 'imperfection' that also numbers that are not values (like the '1' in identifiers like column1) will be replaced.

  • More Linux system counters added: Counters related to Linux memory (including swap) usage added.
  • RPM build now supports SUSE and Mandrake/Mandriva Linux distributions.

Fixed Issues:

  • Under specific circumstances the SQL DM for MySQL service would stop very slow.
  • If network connection was temporarily unavailable the first CPU value after network came back told 100% CPU load.
  • The temporary files for storing public/private keys are now being created with very restrictive file permission in Linux. So only the owner will be able to read/write these temporary files. Although these files would exist only for a fraction of second, in earlier versions of SQL DM for MySQL other users in the same Linux system could get access to them within that small timeslice.
  • Fixed an issue with trending where graphs would not always display properly for uptime-based counters.
  • MONyog.ini file and SQL DM for MySQL database files on Linux are now only readable for user who starts/installs (.gz and RPM build respectively) SQL DM for MySQL (and of course for any user too that was given access by a root user). Before the files were world-readable. This applies to fresh installations only - there is no change with existing installations.
  • Solved an issue where slow startup could occur if lots of servers were registered (Technical: If SQL DM for MySQL had not been running for a while, large amounts of data could require deletion from the Monyog database. The queries used to identify those data would generate significant I/O at startup. The retention process is now 'smoothed over time' and indexes have been added for more efficient deletions).

2.06 SQL DM for MySQL (June 2008)

Fixed Issues:

  • Fixed: The new version 3 release of Mozilla Firefox (now in RC) has a flickering issue with SQL DM for MySQL and the login page did not load correctly in that browser version.

2.05 SQL DM for MySQL (May 2008)

Fixed Issues:

  • Fixed: OS monitoring issue in Fedora Core 6 Zod.

2.04 SQL DM for MySQL (May 2008)

Performance improvement:

  • Earlier SQL DM for MySQL was semaphore intensive. That could result in reaching the 'limit of semaphores that can be created by the kernel' in some systems. SQL DM for MySQL 2.04 will use less semaphores. Another symptom was that a large number of small and zero-size files could be left behind (in system TEMP folder on Windows and in MONyog/bin folder on Linux). This is also solved with this.

2.03 SQL DM for MySQL (May 2008)

Fixed Issues:

  • In some situations where SSH connections failed (including if SQL DM for MySQL was not able to connect to MySQL through tunnel, wrong SSH authentication details for tunneling etc.), sockets were not being closed and it could result in that many sockets were kept in CLOSE_WAIT state. (Note: Connections to MySQL not using SSH were not affected!)

2.02 SQL DM for MySQL (April 2008)

Fixed Issues:

  • In the 'delta' timeframe CPU load displayed was incorrect.

2.01 SQL DM for MySQL (April 2008)

Fixed Issues:

  • Whenever Dashboard was drawn for the first time or redrawn with new configuration settings all nodes displaying CPU load were erroneously drawn with the latest available value. New values appearing after that were drawn correctly. Only CPU load counter was affected.

2.0 SQL DM for MySQL (March 2008)

New Features:

  • SSH tunneling to MySQL servers.
  • Analysis of historical data (trends).
  • Dashboard graph size is now configurable.
  • You can choose to display x-axis values or not in Dashboard (in 'large' display mode). Also remember that no matter if axis-values are displaying you can retrieve values by pointing the mouse to a node in the charts.
  • The no. of samples displayed in dashboard is configurable.
  • Above dashboard settings can be changed from the dashboard page itself.
  • 64 bit binaries for Linux included.
  • Option to display counters as 'value/sec'.
  • Reorganized the connection page for better clarity.
  • Performance improvements.
  • JavaScript code was 'broken down' to smaller units for easier customization. Every counter group now has its own 'custom' script.
  • The menu was reorganized and other GUI improvements for easier navigation between the different functionalities.
  • The 'looks and feel' (of graphics in particular) has been vastly improved.
  • Documentation/help was updated and reorganized with better structure, more hyperlinks - and also now much more better looking.

Fixed Issues:

  • SQL DM for MySQL would not install on some older Linux distro's (including RHEL3).
  • In Linux it was possible to start more identically named Monyog instances. This is now prevented.
  • When stopping SQL DM for MySQL service it could happen that the service was reported to be stopped before the task was complete. Starting service in this situation would return an error. Now it will report 'running' as long as it is not fully stopped.
  • Fixed an issue with the shell script for non-RPM Linux where it could be reported that service had started when it had not.
  • Fixed some calculation bugs (affected 'hit rate' and 'percentage of used blocks' counters).

Miscellaneous:

  • Help/documentation page will open in a separate browser window or tab (depending on browser setting).
  • 'Show All' page was renamed to 'Monitors/Advisors'.
  • System counters have been renamed to 'Linux counters'.

More details on implementation of SSH-tunneling and History/Trends analysis:

  • SSH-tunneling: The implementation does (unlike current SQLyog implementation) not start any external process and does not occupy a local port. The performance for this 'home grown' SSH-tunnel wrapper is very high (you may find it faster than direct connection to MySQL on a remote host)!
  • History/Trends analysis: This is implemented in the 'Monitors/Advisors' page. You can select whatever time interval you want for the analysis. Counters that are UPTIME based (or if you like: CUMULATIVE counters as opposed to SNAPSHOT counters) can be aggregated using SUM function and common time intervals (HOUR, DAY, MONTH etc.). This is semantically similar to the query "SELECT SUM () ... GROUP BY
Expand
title1.x SQL DM for MySQL

1.52 SQL DM for MySQL (February 2008)

Fixed Issues:

  • Installing recent versions on top of 1.1 or earlier could disable connection to the OS (not to MySQL) of servers already registered (this bug was introduced when we started supporting key authentication with 1.5).
  • Alert icons (red and yellow circles) were disappearing from the group in 'Show All' interface if the user clicked the next group.

1.51 SQL DM for MySQL (January 2008)

Fixed Issues:

  • Adding a server with notification enabled was storing wrong information in the 'connection.data' configuration file. After a restart of the SQL DM for MySQL service the wrong information that was read from that file would cause notifications to stop working. Note that if a connection was configured in 'two steps' where notification settings were added to an existing connection there was no error.
  • Fixed a memory leak occurring with public/private key authentication when connection was unsuccessful (server not available, invalid key pair etc.).
  • The shortcuts installed by SQL DM for MySQL installers now point directly to '127.0.0.1' (and not 'localhost'). This solves an issue with Firefox on Windows Vista where resolution of the URL 'localhost' was very slow.

1.51 SQL DM for MySQL (January 2008)

Fixed Issues:

  • Adding a server with notification enabled was storing wrong information in the 'connection.data' configuration file. After a restart of the SQL DM for MySQL service the wrong information that was read from that file would cause notifications to stop working. Note that if a connection was configured in 'two steps' where notification settings were added to an existing connection there was no error.
  • Fixed a memory leak occurring with public/private key authentication when connection was unsuccessful (server not available, invalid key pair etc.).
  • The shortcuts installed by SQL DM for MySQL installers now point directly to '127.0.0.1' (and not 'localhost'). This solves an issue with Firefox on Windows Vista where resolution of the URL 'localhost' was very slow.

1.5 SQL DM for MySQL (December 2007)

New Features:

  • Major speed improvements (in both data collection and as regards browser responsiveness).
  • Private/Public key authentication is now supported with SSH connection to remote hosts. Key format must be OpenSSH standard key format - special formats (like the one used by the 'Putty' program) are not supported.
  • Added security-related counters and advisors.
  • Added counters and advisors for schema and table operations.
  • PROCESSLIST display will not by default 'filter out'. A button has been added in the 'Change Filter' dialog to switch between a non-filtered result and the (old) filtered result for the PROCESSLIST page.
  • PROCESSLIST can be paused/resumed.
  • Default SSH timeout (3 minutes) was replaced with 30 seconds.

Fixed Issues:

  • Fixed some small memory leaks.
  • Deleting a connection did not remove all the files belonging to that connection.
  • Fixed a rare issue where browser could report that the page cannot be displayed while saving/editing server details or connection (IE issue only).
  • Fixed an issue with system counters where 100% CPU usage erroneously could be reported when SQL DM for MySQL started.

1.11 SQL DM for MySQL (October 2007)

Fixed Issues:

  • HTML formatting of queries in the PROCESSLIST tab was not correct. As a result display of queries could be truncated.

1.1 SQL DM for MySQL (October 2007)

New Features:

  • Support for SHOW FULL PROCESSLIST - SQL DM for MySQL monitor processes on the servers in real time. Various filtering options for PROCESSLIST are available. Further displays, copy and EXPLAIN (EXTENDED) a running query from inside SQL DM for MySQL.
  • Documentation was updated - including information about the PROCESSLIST feature, up-to-date screenshots etc.
  • Counters and Advisors - Small adjustments!
  • Debug DUMP facility - SQL DM for MySQL (Windows version) has an ability to store crash-dumps fit for debugging similar to SQLyog as explained here:
    Newtab2
    aliasDebug facility
    urlhttp://faq.webyog.com/content/32/145/en/explanation-of-the-sqlyog-debug-facility.html
    : Debug Facility.
  • Menu rearrangement etc. - or clarity we have decreased the number of menus displaying. Those that 'went away' are available as links or submenus.

1.04 SQL DM for MySQL (August 2007)

New Features:

  • Improved counters and advisors.
  • Customize page now will show the .js-components that user changed with a red * (star). Note that existing .js-components will be overwritten when you upgrade. The red star will help you to see what you need to back up before upgrading.
  • Default port is now 5555. With certain names used for the connections there was a conflict with a standard 'rule' of Norton Internet Security when port 9999 was used.
  • The option to display graphs from the 'monitors/advisors... custom timeframe' interface was temporarily removed.

Fixed Issues:

  • Fixed a crashing bug in mailing section if a .js-component was corrupted.
  • Adding the option to send mail after registering a server required SQL DM for MySQL service to be restarted.

1.03 SQL DM for MySQL (August 2007)

New Features:

  • A BELL icon displays in the 'Monitors/Advisors' page for alertable counters.
  • Various small GUI improvements.
  • Documentation updated with details about system Objects + various small corrections.

Fixed Issues:

  • %age of queries doing full table scan metric was incorrect.
  • With very small mail interval setting it could occur that selected servers became deselected.
  • Fixed a bug in the calculation of full table scans.

1.02 SQL DM for MySQL (August 2007)

Fixed Issues:

  • Fixes an issue in previous 1.x releases that may result in too early expiry of the TRIAL.

1.01 SQL DM for MySQL (August 2007)

Fixed Issues:

  • Replication counters did not display in LINUX builds (both .rpm and .tar.gz).

Additional note on file storage positions and upgrading:

Version 1.0 RC changed the storage position for various files used by SQL DM for MySQL. This release is in this respect identical to 1.0 RC and 1.0.

By default the embedded database is now stored:

  • Windows 2K/XP/2003: {System_drive}:\Documents and Settings\All Users\ApplicationData\Webyog\MONyog\Data
  • Windows Vista:{System_drive}:\ProgramData\Webyog\MONyog\Data

... but user can specify another location if for instance she does not want to store on the system disk/partition at all.

Also the monyog.ini file and the log file is now no longer stored in 'program files' file tree (or whatever localized name it has). The storage position is:

  • Windows 2K/XP/2003: {System_drive}:\Documents and Settings\All Users\ApplicationData\Webyog\MONyog
  • Windows Vista:{System_drive}:\ProgramData\Webyog\MONyog

Users upgrading from 0.9 who want to use existing data must after installing this version:

  1. Stop SQL DM for MySQL service.
  2. Copy the folders containing databases named with a number like "0001" or "0002".
  3. Start SQL DM for MySQL service.

No such intervention is required when upgrading from version 1.0 RC or 1.0 (unless storage position is changed again, of course!).

Upgrading from versions before 0.9 is not possible. These versions must be uninstalled and installation folder deleted or this version must be installed to another folder.

1.0 SQL DM for MySQL (August 2007)

New Features:

  • Installs and runs on Windows 2000.
  • Every counter is available in every timeframe.
  • User can specify where the embedded database is stored.

Fixed Issues:

  • Retrieval of memory information from Linux servers was broken in 1.0 RC.
  • Windows version: Solved an issue with a dependency on a .dll file that was reported missing on some systems.

Additional note on file storage positions:

Version 1.0 RC changed the storage position for various files used by SQL DM for MySQL. This release is in this respect identical to 1.0 RC.

By default the embedded database is now stored:

  • Windows 2K/XP/2003: {System_drive}:\Documents and Settings\All Users\ApplicationData\Webyog\MONyog\Data
  • Windows Vista:{System_drive}:\ProgramData\Webyog\MONyog\Data

... but user can specify another location if for instance she does not want to store on the system disk/partition at all.

Also the monyog.ini file and the log file is now no longer stored in 'program files' file tree (or whatever localized name it has). The storage position is:

  • Windows 2K/XP/2003: {System_drive}:\Documents and Settings\All Users\ApplicationData\Webyog\MONyog
  • Windows Vista:{System_drive}:\ProgramData\Webyog\MONyog

Users upgrading from 0.9 who want to use existing data must after installing this version.

1. Stop SQL DM for MySQL service.
2. Copy the folders containing databases named with a number like "0001" or "0002".
3. Start SQL DM for MySQL service.

No such intervention is required when upgrading from version 1.0 RC (unless storage position is changed again, of course!).

Upgrading from versions before 0.9 is not possible. These versions must be uninstalled and installation folder deleted or this version must be installed to another folder.

Expand
title0.x SQL DM for MySQL

0.9 SQL DM for MySQL Beta1 (July 2007)

Note that this release is a TRIAL build. It has the restrictions that,

  1. Maximum 2 servers can be registered.
  2. It will expire on August 15th 2007.

Before expiry of this beta we plan to release version 1.0 FINAL and publish purchasing and licensing terms.

Also notice that the schema of the embedded database has changed compared to previous versions. With this beta we will not provide a database upgrade script. If you have a previous version installed you must either,

  • install to another folder.
  • or uninstall the old version.

New Features:

  • Authentication is in place. SQL DM for MySQL pages can be watched from another machine where SQL DM for MySQL service is running. SQL DM for MySQL pages can be watched from another machine where SQL DM for MySQL service is running.
  • Two-level alerts (WARNING/CRITICAL).
  • Mail alerts.
  • Various timeframes available for display of data in 'Monitors/Advisors'.
  • Replication counters.
  • Documentation (1st version) included.
  • And lots of minor improvements.

Known issues:

  • Installation on Windows 2000 is (still) not possible (due to a dependency in the SSH library that we use). We hope to fix this soon.
  • We are aware of some (rare) problems that can occur on Windows Vista including:
    1. Graphs will not populate with old (stored) data.
    2. Pages will not update properly.

0.20 SQL DM for MySQL (May 2007)

Fixed Issues:

  • Fixed a crashing issue while installing the SQL DM for MySQL over existing SQL DM for MySQL installation.
  • Introduced locks to make thread safe.
  • Fixed a leak of GDI's (Graphics Device Interfaces). Number of open GDI's would increase and when SQL DM for MySQL was running for very long time, SQL DM for MySQL service could ultimately crash.
  • Fixed few JavaScript issues.

0.16 SQL DM for MySQL (March 2007)

Fixed Issues:

  • AJAX is now fully implemented in the Monyog main screen.
  • Improved advisors - in particular regarding the Query Cache.
  • Fixed all reported (and some non-reported) GUI issues.
  • Lots of code changes for better structure, performance and maintainability.


Scroll pdf ignore
Newtabfooter
aliasIDERA
urlhttp://www.idera.com
| 
Newtabfooter
aliasProducts
urlhttps://www.idera.com/productssolutions/sqlserver
| 
Newtabfooter
aliasPurchase
urlhttps://www.idera.com/buynow/onlinestore
|
Newtabfooter
aliasSupport
urlhttps://idera.secure.force.com/
|
Newtabfooter
aliasCommunity
urlhttp://community.idera.com
|
Newtabfooter
aliasResources
urlhttp://www.idera.com/resourcecentral
|
Newtabfooter
aliasAbout Us
urlhttp://www.idera.com/about/aboutus
|
Newtabfooter
aliasLegal
urlhttps://www.idera.com/legal/termsofuse
IDERA Website | Products | Buy | Support | Community | About Us | Resources | Legal