What is a one sentence summary of your feature request?
Improving logging for FSAA to be structured, relevant, and traceable
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
To reduce the operational complexity of File System deployments and facilitate further enhancements for FSAA Always-On Scanning, we should add structured logging to ease programmatic analysis, and improve log message relevance and traceability. The new FSAA coordination service should make this a lot simpler. This will involve the following:
Log message improvements
-Adjust severity (set and document criteria for each severity)
-Reduce the volume of messages
-Connect messages to resources and consequences
Unified logging
-Combine job and applet logs (affected by the coordination service)
-Bring SDD-related logs into the main log
-Unified log retention settings (count and size, rollover, and compression)
-Links to find/browse/search logs
Structured logging
-Bring some of what currently logged messages into SQL
-Attach metadata to log messages (resource IDs, scan IDs, SDD criteria, etc.)
How do you currently solve the challenges you have by not having this feature?
N/A - Idea posted by Access Analyzer product team