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.
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!
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.
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.
We've got asked a couple of times about how to do authentication and authorization with a database like PostgreSQL or Redis. "Easy, write a plugin!", has been our standard answer.
We've just released a new version of VerneMQ. This release contains many bug fixes and several (smallish) performance improvements.
We presented VerneMQ at the Paris Erlang User Group on June 29th 2015. We don't want to exclude those of you who couldn't make it to Paris on time and share the slides with you. At this point thanks again for having us!
Meet VerneMQ the most scalable MQTT message broker!