How to make us love you for your issues

Most of the time, the issues reported on GitHub or in the mail we receive are perfectly fine, don't worry. We love to hear from you in any case, so don't take the following too seriously ;) We'd still like to give some ideas on what information you can include when you report errors for VerneMQ.

Tracing VerneMQ with the erlyberly tool

We have been asked to include more debug logs in VerneMQ. We'll do that in a next release (it's all nicely included already, but we just don't call `lager:debug` that much). The reason for that is simple: In an Erlang system you mostly use tracing not debug logging.

VerneMQ plugins of tomorrow

With the initial release of VerneMQ we had great feedback from many of you interested in IoT technologies. But we also heard some concerns about integrating an Erlang based product into a rather traditional infrastructure. Why would that be a problem? Do you need to know Erlang to run VerneMQ? No! VerneMQ-as-a-product should provide blackbox MQTT functionality. You don't configure and administer it with Erlang commands or something. But...plugins!

Monitoring VerneMQ Application Metrics with Grafana

While VerneMQ had many metrics built in right from the start, we never had the chance to show you how simple it actually is to display those metrics. So we'd like to show you today how easy it is to integrate VerneMQ ReleaseĀ 0.12.0 with Grafana, a powerful dashboard composer that allows you to elegantly explore all the VerneMQ metrics.

VerneMQ 0.11.0 is here!

We've just released a new version of VerneMQ. This release contains a major refactoring of the queueing mechanism as well as several smaller improvements and bug fixes. Prior to this version the offline messages were stored in a global in-memory table backed by the LevelDB message store.