Jump to content

SunnyJ

Members
  • Posts

    2
  • Joined

  • Last visited

Everything posted by SunnyJ

  1. Description: Advanced/Granular Database Cleanup Options. Detail: Currently in ESET Protect On-Prem, there are only 4 timeframe options for database log cleanup. It would be nice if there were more advanced options, such as individual time frames for different detections (ie, being able to trim firewall logs to a couple days vs blocked files/sites to a month vs antivirus detections to months or years). Or trimming of performance logs (which we had over 5m of these) differently than other logs. For companies that have to keep long periods of some logs but not others, this would help us keep these while cleaning out others and keeping the database at a manageable size.
  2. Description: Custom identifiers Detail: In an environment where management of devices is mixed, it would be nice if there was a way to gather a custom value or provide a script that can return a custom value for display in the details of a system. In our case the built in identifiers are unreliable; hostnames are managed independently by different management parties, the IP reported is the IP assigned to the adapter (so when the server is behind NAT, it's not useful), mobo SNs don't get set by the manufacturer so just return N/A or a default 0123456789. So, for at least us, on setup, we add a custom registry or configuration value to our Windows or Linux systems for monitoring and tracking (it's also affixed to the physical box). Being able to have it retrieve a registry value or run a batch/bash script that'll return a value would be highly useful for tracking purposes. I thought about having each client run a custom command with the "run command" client task; however, as far as I can tell, it does not seem to record or return any information back to the server other than a success/failure. We've considered using this approach, but then posting that data to a logging site, but that then requires more port allowances, would be difficult to match up exactly, and is inefficient, so something built in would be preferred. TBH, I'm surprised there isn't just a way to return some custom information in general, as that seems like it would be in general really handy, not just in terms of computer identification, but giving admins the ability to check for different statuses of OS or other values as needed.
×
×
  • Create New...