Improving MariaDB Observability with OpenSearch and Grafana

When dealing with queries in MariaDB, there are several approaches, such as the general query log, the slow query log, and the performance_schema.

The general query log is not recommended as it doesn’t contain much valuable information and can use a lot of resources when writing to the file on busy systems.

The slow query log is a much better option, as it contains many metrics and can be tuned. But if you want to collect everything, writing to the disk can also be an expensive operation.

DBeaver, a solid alternative to MySQL Workbench that works like a charm with MariaDB

You may have noticed that MySQL Workbench has not been actively developed for a long time… You can see the number of open bugs. And the number of commits illustrates this too:

In fact, Workbench has been put out of maintenance mode to add the MySQL HeatWave Migration Assistant to OCI. Not less, no more.

On some versions, it is no longer able to connect to a MariaDB Server, or to use it on new OSes (Fedora 43, recent macOS, …).

These kinds of GUI tools are very popular for developers, and I was surprised by the number of users Workbench had.

What the MariaDB Community Wants Next: A Look at Our MySQL-Compatibility Poll

We recently asked the community:

“Which MySQL-compatibility feature would you most like to see in the next MariaDB release?”

A big thank you to everyone who voted. We received 506 votes, and the results give us a helpful snapshot of which compatibility gaps feel most important to users right now.

Poll results

A two-feature race

The first thing that jumps out is how close the top two were.

MEMBER OF json operator (MDEV-38591) came in first with 145 votes, but bitwise operators for binary and bit types (MDEV-10526) were right behind it with 138 votes.