Read Time: 4 min
Today, we are announcing a few changes around the LogDNA Agent happening today and in mid-October.
Starting today, we begin officially recommending that customers who want to log WinEvents use our NXLog integration. In mid-October, we will deprecate support of WinEvents in all versions of the LogDNA Agent.
Our NXLog integration supports both file logging and WinEvents. Installation steps can be found here in our documentation.
We will be upgrading our Node.js version used to build the LogDNA Agent from v8.3.0 to v12. As a result, the new versions of the LogDNA Agent released in mid-October and beyond will not support Debian 8 and Ubuntu 14.04, as Node.js v12 drops support for those operating systems.
We will also stop supporting Debian 8 and Ubuntu 14.04 on prior versions of the LogDNA Agent.
Important Note: We are changing our product naming/versioning (detailed below) and when released, this change only applies to customers currently using LogDNA Agent v1 to send system logs. Our new LogDNA Kubernetes Agent can still be deployed to send kubernetes logs.
We are restructuring our suite of LogDNA Agents to make updates easier to deliver to our customers. Starting in mid-October, we will split our current LogDNA Agents into separate versions based on their respective platform or operating system (OS).
The installation process and package names will not change. Separating agent versions enables us to build platform- and OS-specific features. Below are the 4 different LogDNA Agents:
LogDNA Windows Agent
Log Types: Files
LogDNA Mac Agent
Log Types: File Logging
LogDNA Linux Agent
Log Types: File Logging, Journald
LogDNA Kubernetes Agent
Log Types: File Logging
We are actively building out our support matrix and will be sending an update within the next month. In general, we will continue to support our current set of platforms and operating systems (OS) other than what is being deprecated as mentioned in this email.
What actions do I need to do now as a customer?
If you currently send or might send WinEvents to LogDNA, please use our NXLog integration. Documentation on how to get started is linked here.
Where can I keep track of changes to the various LogDNA Agents?
Please check out the changelog in our public Github repository: https://github.com/logdna/logdna-agent.
What should I do in mid-October?
Manually update your agent version if there are any changes you’d like from the changelog. In addition, if you send WinEvents to LogDNA, migrate to our NXLog Integration instead. We will no longer be supporting WinEvents with our LogDNA Windows Agent.
Note: If you are sending file logs from Debian 8 or Ubuntu 14.04, do not manually update your agent. Newer LogDNA Agent versions will be built with Node.js v12 which does not support Debian 8 or Ubuntu 14.04.
How does the name change affect my configuration?
There are no changes to installing the LogDNA Agent and updating the LogDNA Agent.
What will happen to the current LogDNA Agent v1 and LogDNA Agent v2?
We will still support them as we do any legacy version. However as noted above, we will not be supporting WinEvents, Debian 8 and Ubuntu 14.04.
Thank you for your continued support as we work to improve your logging experience. If you have any questions or feedback, please feel free to email me at firstname.lastname@example.org.
With the ever-growing volume of application logs and analysis tools available, it can be time-consuming to set up your observability tools to keep up with...
Adding the ability to store and view raw logs, allowing customers to debug with logs in their unaltered form. If you’ve ever looked at your...
The Extract and Aggregate fields feature allows users to custom parse historical logs (post-ingestion) and get an aggregated count on those newly parsed fields. Enterprise...