New year, new NXLog Enterprise Edition.
Our developers have been hard at work throughout the holiday season to release the latest version of our flagship log collection solution. We are proud to announce NXLog Enterprise Edition 5.7, which includes bug fixes, security updates, and, of course, many new features.
Read on to find out more about some of these new features.
Native support for Google Cloud Logging, Amazon S3, and Microsoft 365
Google Cloud Logging, Amazon S3, and Microsoft 365 integrations were already available as Add-Ons to NXLog Enterprise Edition. Previously, these Add-Ons were external scripts that could be invoked with an Exec directive.
We’ve ported these external scripts into native NXLog modules (im_googlelogging & om_googlelogging, im_amazons3 & om_amazons3, and im_ms365). Written in the Rust programming language, you can expect fast, reliable, and secure operation. These new native modules now benefit from an easy-to-understand configuration, similar to other NXLog modules, and removes the need to use and support external programming languages and libraries.
Structured events in Google Chronicle
Google Chronicle is one of the many SIEM solutions that NXLog Enterprise Edition seamlessly integrates with. In fact, Google even recommends using our software on their own website.
We announced native support for unstructured events in Google Chronicle with NXLog Enterprise Edition 5.5. Now, we’ve built on that foundation by supporting structured events in this latest version. As a logging company, we firmly believe that structured events are the most useful and efficient method of log collection.
Google Cloud Pub/Sub integration
In addition to the aforementioned Google products, we’ve also added support to Publish and Subscribe to Google Cloud Pub/Sub instances. You can learn more about Google’s asynchronous, scalable messaging service on the Google Pub/Sub website.
Kerberos support for Windows
We’ve added support for Kerberos network authentication to our im_wseventing module. Previously, this functionality was only available on Linux. Now, you can receive logs through Windows Event Forwarding by authenticating with Kerberos rather than over HTTPS.
OAuth2 support for Kafka output
When you request features, we deliver them. That’s why we’ve added OAuth2 support as a method of SASL authentication to our om_kafka output module. Securely integrate with Apache Kafka systems using our native modules.
You can check out all of the new features and fixes in our release notes, and view our changelog for a full list of what’s changed between versions. Check out our comprehensive documentation, and get in touch with us below if you need help upgrading, have a feature request, or have any other questions.