Hello!
We are coming back with new set of information regarding Energy Logserver – starting with currently latest version – 7.0.5. This time we would like to turn your attention to some new data management capabilities we’ve introduced as well as our response to CentOS 7&8 dispute. Hope you will find it helpful!
Data Management Capabilities
SUPPORT OF ARCHIVING SELECTED FIELDS
While log retention due to regulatory compliance is something we see in almost every organizations we work with – the scope of what part from log message to store – varies.
With newly introduced „archiving the selected fields” you are able to select the exact fields from the log message, which you would like to save in your storage.
Just create new „Archive” task and filter the names you want to include in the report:
This way you can seriously optimize you log storage & archives searching speed!
OBJECT PERMISSION – DELETING RELATING OBJECTS
Now, when deleting an object, in “object permission” you can mark related objects to be deleted at the same time. This is made to ease-up the governance time with our solution. Remember when you had to manually remove each visualization from saved dashboard?
It is not the case anymore!
No when you go to each:
Saved search -> Visualization -> Dashboard – you can delete dashboard with all related objects.
SCHEDULER FOR „DATA EXPORT”
Newly added scheduler helps you to stay compliant with re-occurring reporting requests. This feature is helpful when you are looking to:
Automate certain reporting task (e.g. monthly application performance report)
Prepare report from certain upcoming date (with scheduler, you don’t have to remember)
Dump the raw data in scheduled manner
This feature can be a great addition to both – compliance and governance related function set.
Deployment updates
DEPLOYMENT NOW POSSIBLE FOR ORACLE LINUX 7/8, CENTOS STREAM & SCIENTIFIC LINUX
Our installation support is now additionally possible for Oracle Linux7/8, Scientific Linux 7, Centos Stream (and also originally for Centos7/8 and RedHat7/8). We decided to introduce new implementation possibilities due to recent issues with Linux Centos distribution. You can see more in following article: CentOS Linux is dead—and Red Hat says Stream is “not a replacement”
As your fellow technical team – we will be happy to discuss this ground-breaking announcement and help you prepare for the future!