Search Knowledge Base by Keyword
NSSX Log Troubleshooting
Dev wants the log file to be bloated with 10s of thousands of rows whenever a Scan Job finishes. They also like to run everything in parallel so things like Scan Job completion, Aggregation start, Aggregation finish, Notifications, Path labels update, Index rebuild, etc do not come in any particular order. As you most likely figured out by now, this makes troubleshooting insanely frustrating. This article is to help you use correct search terms to find what you’re looking for more easily.
| If you’re looking for | You should search for |
|---|---|
| Aggregation finished | Will process subscribers for event:SFAggregationFinished |
| Aggregation started | NSSX.BL.Scanning.ScanFunctionsAggregationAPI.Run||Run ScanFunction aggregate with configuration |
| Event Notifications Template parsing errors | NSSX.Common.Notifications.RazorTemplateRenderer.RenderFromFileWithModel |
| Event notification settings | NSSX.BL.Engines.EventNotificationEngine.ShouldNotify||Should notify settings: |
| Path Label updated | Will process subscribers for event:PathLabelUpdated |
| Scan Job aborted | Will process subscribers for event:ScanAborted |
| Scan Job failed | Will process subscribers for event:ScanFailed |
| Scan Job finished | Will process subscribers for event:ScanFinished |
| Scan Job started | Will process subscribers for event:ScanStarted |