Open for Voting

Automatically select all logs

As it stands you have to tick all the logs and in the config file all logs are implicitly listed.

This means

  • if a new log is added it isn't picked up
  • you can't transfer a config file to another server easily as it may have differing logs

If the config could just say ALL LOGS and that would work around the above it would be really useful and make mass deployment a lot easier.  This is a feature my company would use immediately as we readily have to store all events as part of our protective monitoring requirements.

  • I haven't tested with the latest Log Forwarder version(we don't run the needed .Net framework version) but in 1.1 if a configured event log no longer existed the service would not start nor could you edit the config via the GUI.  In those cases we either would delete the existing config file and start over or manually remove the references in the config.  In a large, dynamic environment that ends up being a good bit of time.

    If the event log no longer exists the app should still start but record an error in a log/event log.

    If this is no longer an issue in the latest release I thank the team for the fix. If it is still an issue can the next update improve on this?