After a slightly slower month last week things seem to be back to full steam this month.

You can see our change log here.

Last week we sent out a call for feedback via a survey, if you haven’t already completed it then please consider doing so: https://t.libren.ms/trc8a

Here’s a summary of what’s been released in v1.27:

Ability to now validate your database schema. This seems to have caused some confusion as people have thought that somethings gone wrong. The schema updates have been added by various contributors along the way, some haven’t been 100%, some don’t meet the MySQL STRICT_TRANS_TABLES option + others and so have either failed to apply or caused some odd issues along the way. Whilst we are working out what to do with regards to the future support of PHP < 5.5 (which basically means we can’t use a proper DBAL or existing database migration code) we decided to hack something together which would track the current MySQL schema in relation to the commit a user is running. We’ll post a little more about this separately as it’s possibly useful for other projects.

We’ve refactored our documentation on how to add support for a New OS (useful when adding new health metrics to existing devices as well): http://docs.librenms.org/Developing/Support-New-OS/

Switched to using a new CLA that manages our contributors agreement. The historic AUTHORS.md file is still in place but all new commits will require the author to use the new system which is actually much easier. This does also mean that if you’ve already signed the old CLA then you will have to sign the new one as well.

We’re down to the last 12 OS’ that haven’t been converted to YAML.

Around 20+ new devices are now supported with additional improvements to many existing OS’ - Basically more graphs for you to look at

Here’s our last months pulse data from GitHub:

And our GitHub stats:

Issues are now around 40 which is great news. Some people might have found us a bit harsh in responding to issues but without some structure around what GitHub issues is there for we just have chaos and that chaos has taken us around 6 months to pull back from so that the developers are able to do so effectively. If we’ve annoyed you, we apologise - please do however work with us - it makes everyones lives easier

Once again, a huge thank you to the 20+ contributors we’ve had this month. No matter the size or complexity of the contribution, it’s always great to see people giving back.

Until next month, happy monitoring.