The MySQL error log is an essential part of database server performance monitoring. Whenever something goes wrong or performance degrades, the Error Logs are usually the first place we look to start troubleshooting.

The MySQL Error Log is one of three related log types:

• The Error Log: It contains information about errors that occur while the server is running (as well as server start and stop events).
• The General Query Log: This is a general record of what mysqld is doing (connect, disconnect, queries).
• The Slow Query Log: It consists of “slow” SQL statements as defined in the long_query_time global variable.

You can enable error log monitoring to allow Monyog to keep an eye on your MySQL Error Log, and notify you when something goes awry. Moreover, Monyog combines the General Query, Slow Query and Error logs in a single view for both network and cloud servers. For example, in the …

MariaDB came into being the day that Oracle announced the purchase of Sun in 2010.  In order to keep it free under the GNU GPL, Michael Widenius forked MySQL and took several MySQL developers with him in the process.  Since then, MariaDB has been a drop-in replacement for MySQL, albeit with more features and better performance.

In the Improve MariaDB Performance using Query Profiling blog, we learned some useful techniques for tracking and analyzing slow queries using a couple of MariaDB server’s built-in tools: the Slow Query Log and the Performance Schema.  

The Slow Query Log records queries that are deemed to be slow and potentially problematic, that is, queries that take longer than the long_query_time global system variable value to run.

The Performance Schema is a storage engine …

Query profiling is a useful technique for analyzing the overall performance of a database. Considering that a single mid-to-large sized application can execute numerous queries each and every second, query profiling is an important part of database tuning, both as a proactive measure and in diagnosing problems.  In fact, it can become difficult to determine the exact sources and causes of bottlenecks and sluggish performance without employing some sort of query profiling techniques. This blog will present a few useful query profiling techniques that exploit MariaDB server’s own built-in tools: the Slow Query Log and the Performance Schema.

MariaDB vs. MySQL

Needless to say, the techniques that we’ll be covering here today are likely to be equally applicable to MySQL, due to the close relationship between the two products.

The day that Oracle announced the purchase of Sun back in 2010, Michael “Monty” Widenius …

Although only available as a Release Candidate, MySQL 8 is already proving itself to be a huge leap forward in many regards. Error logging is no exception. The MySQL development team just announced that they have redesigned the error logging subsystem to use a new component architecture.

The redesign will allow the filtering of log events, as well as the routing of error log output to multiple destinations, via the enabling of multiple sink components.  This will make it possible to send error log events to third-party systems for additional formatting and analysis.

In today’s blog, we’ll explore how to employ MySQL 8’s component-based error logging to achieve a variety of logging configurations. Note that all this is specific for MySQL 8 and is not available in earlier versions and also not in MariaDB. However, MariaDB has an option to write the error log to the system “syslog” on systemd-based Linux variants – …

We’re excited to announce that Webyog has been acquired by Idera, Inc. Idera, Inc. is a leading provider of B2B software productivity tools that enable technical users to do more. This acquisition will allow Webyog to expand the reach of our MySQL tools to new geographies while better serving our customers.

Webyog began in 2001 with the mission to develop a quality MySQL GUI tool (SQLyog) for our users and quickly became a key contributor to the MySQL ecosystem. Our core principle of enabling users to easily manage their MySQL databases has resonated with MySQL users and enabled us to build best of breed database management tools for the community as a whole. Today, Webyog provides MySQL database management and monitoring tools to over 2.5 million users in 150+ countries.

Our joining forces with IDERA will further enhance our product offerings and provide customers with exciting …

We recently conducted a webinar on Audit Log analysis for MySQL & MariaDB Databases. This blog will further provide a deep dive into the security & compliance surrounding databases.

Database auditing is the tracking of database resources utilization and authority, specifically, the monitoring and recording of user database actions. Auditing can be based on a variety of factors, including individual actions, such as the type of SQL statement executed, or on a combination of factors such as user name, application, time, etc.  Performing regular database log analysis bolsters your internal security measures by answering questions like who changed your critical data, when it was changed, and more. Database auditing also helps you comply with increasingly demanding compliance requirements.

The purpose of this blog is to outline the importance of audit log …

Join Shree Nair, Product Manager at Webyog, as he demonstrates the new ‘Audit Log Analysis’ feature introduced in Monyog v8.5.0 and rolls out the roadmap for the upcoming releases.

Date & Time: Wednesday, March 21, 2018 at 11:00 am EDT

Register Now!

What to expect from the webinar?

– Quick walkthrough of Audit Log feature on a live Monyog instance.

– You will learn about the upcoming product roadmap for Monyog.

– You can take part in Q&A session and submit your feature requests too.

If you can’t attend this webinar live, register anyway and we’ll send you a link to the recording.

You can …

Changes as compared to Monyog MySQL Monitor v8.4.1 include:

This release fixes a few minor bugs only and implements a number of user requests.

Features:

• Monyog can now analyze MariaDB and MySQL enterprise Audit log.
• Added support for LDAP with StartTLS and SSL.
• The default path for MONyog.log can be changed using the parameter “MONyogLogPath” from the MONyog.ini file.

Bug Fixes:

• Monyog logged bogus SQLite errors on fresh installation.
• Monyog displayed console error if LDAP group name contained inverted comma.
• Changed alert condition for “Seconds behind master” monitor to consider “NULL” as an alertable condition. It considered the value “NULL” stable condition earlier.
• On upgrading, Monyog filled the mail alert field for sniffer with the bogus email id “admin@mydomain.com”.
• On selecting a …

Important notice: With this release, we have changed the registration keys. As usual, the new keys are available for registered users from our Customer Portal.

Monyog MySQL Monitor v8.4.0 adds more alert and logging options and enhances the MONyog API. Further, we redesigned the settings page and a number of bugs were fixed.

Changes as compared to Monyog MySQL Monitor v8.3.2 include: Features:

Added more notification channels (Slack and Pagerduty) for Monyog alerts. (Read more) Option to write Monyog alerts in the Syslog of the machine where Monyog is installed. This option is only available for Linux. Option to edit the subject line for Monyog alerts. Added MONyog API to disable notification for a monitor based on a server/tag. ( …

Amazon Web Services (AWS) is a cloud platform that offers a wide variety of services including computing power, database storage, content delivery and other functionality that targets businesses of all sizes. One of their database solutions includes the Amazon Relational Database Service. Amazon RDS includes a number of popular RDBMSes, including Amazon Aurora, PostgreSQL, MySQL, MariaDB, Oracle, and Microsoft SQL Server, as well as tools to manage your databases and monitor their performance.

Despite the wide range of metrics available within the Amazon RDS console, there are some very good reasons for using your own monitoring tool(s) instead or in addition to those offered by Amazon RDS. For example, familiarity with your own tool(s) or access to features that Amazon RDS does not provide would constitute two persuasive reasons for employing a local tool.

With traditional software monitoring platforms such as Monyog still enjoying …