We use cookies to try and give you a better experience in Freshdesk.
You can learn more about what kind of cookies we use, why, and how from our Privacy policy. If you hate cookies, or are just on a diet, you can disable them altogether too. Just note that the Freshdesk service is pretty big on some cookies (we love the choco-chip ones), and some portions of Freshdesk may not work properly if you disable cookies.
We’ll also assume you agree to the way we use cookies and are ok with it as described in our Privacy policy, unless you choose to disable them altogether through your browser.
We are running version 4.2.3.124 and was waiting to upgrade EventSentry again until version 4.3 was released. With the recent log4j vulnerability even though EventSentry isn't affected based on KB-ID 461, version 4.2.3.136 was released the other day and states the web reports were migrated to log4j 2.17.0.
If we upgrade the web reports only (web reports only file has been downloaded manually) to this new version, will the full EventSentry version need to be upgraded to this same version before going to version 4.3 when it is released? Or even though there are separate install files, do both the management console and web reports need to be at the same version for compatibility reasons? EventSentry and the web reports are running on the same Windows Server behind firewalls.
0 Votes
2 Comments
NC posted over 4 years ago
Great. Thank you for the quick response.
0 Votes
Ingmar Koecher posted over 4 years ago Admin
You can upgrade the web reports separately as long as the first 3 parts of the version number match.
However, we always recommend running the latest version of EventSentry, for example there have been some stability fixes for the agent since build 124. If you're running PostgreSQL then I would definitely recommend upgrading to the latest build.
0 Votes
Login or Sign up to post a comment