Jun 25, 2020 | 2 min read
1.7.0 brings the first release of the new Problems Database functionality, developed by our partners at Amazee Labs, along with the first couple of integrations. We’ll talk more shortly about the great potential for the Problems Database, but for now we’ve included the ability to collate Image vulnerability scans from Trivy (integrated with our Harbor install) and parse site audit and remediation activity generated by Drutiny).
We’ve also done a heap of work behind-the-scenes on a couple of other subsystems; the logging ecosystem to date has utilized a fluentd-based log collector to forward logs to our internally-hosted ElasticSearch, and then make them available to users via Kibana. With the work done to support Kubernetes, we’ve needed to overhaul this process, and we’ve also taken the opportunity to extend it a little. We now utilize a fully-featured logging operator to collect, enrich and transfer the logs, and the system is now more extensible, customizable, and scalable, giving us (and potentially end-users) more control over log destinations, formats, and retention policies.
The third area of updates has to do with our service monitoring. To date, we have used Statuscake to provide us with real-time monitoring and alerting of site status across all of our clusters. As we’ve grown, and complexity has increased, it has been getting harder and harder for us to manage this integration ourselves. Again, we’ve selected an Ingress Monitor Controller to automatically watch all of our ingresses (routes) and add/remove monitors as required. We’ve also assessed all the various monitoring options available, and we have selected Uptime Robot as being the most suitable for our needs — at this stage, it won’t mean much to end-users, but as we make more features available, we’ll be sure to let you know.
Missed the last round of updates? See what changed in Lagoon 1.6.
See the full release notes here.