Troubleshooting & FAQ: Log File Parser Monitoring Agent
Find quick solutions and answers for the Nodinite Log File Parser Monitoring Agent. Jump to your specific issue using the navigation guide below.
Find Your Solution
Click any section below or use the quick links:
| Issue Type | Quick Solutions |
|---|---|
| π File Access & Permissions | Can't access files, SMB share issues, permission problems |
| π― Pattern Matching & RegEx | Patterns not working, RegEx syntax, timestamp issues |
| β‘ Performance & Optimization | High CPU, memory usage, large file handling |
| π ACK/NAK Correlation | Transaction tracking not working, timeout issues |
| π Alert Management | Too many alerts, false positives, notification issues |
What access rights are required?
The account used to run the Nodinite Log File Parser Monitoring Agent as a Windows Service must have read access to the folder(s) with log files. This is detailed in the Prerequisites for Log File Parser Monitoring Agent user guide.
Note
Please review the Logon as Service Right user guide.
File Access & Permissions
Where can log files be located?
Supported locations:
- Windows folders:
C:\Logs\*.log(local paths) - SMB shares:
\\server\share\logs\*.log(network paths)
Not supported: NFS, FTP, cloud storage (submit feature request to Support)
Common permission issues
| Problem | Solution |
|---|---|
| "Access denied" | Service account needs Read permissions on log files and folders |
| "Path not found" | Verify UNC path format: \\server\share\folder |
| SMB timeout | Check network connectivity, firewall rules |
Pattern Matching & RegEx
Common RegEx patterns
| Use Case | Pattern | Example Match |
|---|---|---|
| Errors | ERROR\|EXCEPTION\|FATAL |
ERROR: Database timeout |
| HTTP Errors | 5\d\d |
500, 503, 504 |
| Capture Groups | OrderId:(\d+) |
OrderId:12345 (captures 12345) |
| Negative Lookahead | ERROR(?!.*retry) |
ERROR but not "ERROR retry" |
Why patterns don't match
- Case sensitivity: Use
(?i)errorfor case-insensitive - Special characters: Escape
.*+?with backslash - Timestamp format mismatch: Verify log datetime format
- File encoding: Ensure UTF-8 or ASCII encoding
Performance & Optimization
Performance guidelines
| Metric | Recommended | Tuning |
|---|---|---|
| Files per agent | <200 files | Split across multiple agents |
| File size | <500 MB | Use log rotation |
| Scan interval | 30-60 seconds | Increase for non-critical logs |
| Memory usage | <100 MB | Avoid large regex patterns |
ACK/NAK Correlation
Quick setup
Example configuration:
- Start pattern:
OrderReceived.*OrderId:(\d+) - End pattern:
OrderCompleted.*OrderId:$1 - Timeout: 30 minutes
Complete guide: How to monitor correlated events
Alert Management
Common fixes
| Problem | Solution | Example |
|---|---|---|
| Known errors | Add negative pattern | ERROR(?!.*retry successful) |
| Too many warnings | Monitor only critical | Filter: ERROR, FATAL only |
| Maintenance noise | Schedule suppression | Disable alerts during deployments |
Result: 70-90% reduction in false positives.
Implementation Examples
| Use Case | Guide | Description |
|---|---|---|
| π Transaction tracking | How to monitor correlated events | ACK/NAK monitoring for business workflows |
| π Error detection | How to monitor file content | Pattern matching for errors and security events |
| π IIS monitoring | How to monitor IIS W3SVC log files | Web server performance and error monitoring |
| π System diagnostics | How to monitor Nodinite Diagnostic files | Platform health and troubleshooting |
Need More Help?
Quick resources:
- π§ Email: support@nodinite.com
- π« Support Portal: Support
- βοΈ Configuration Guide: Configuration
- π Prerequisites: Prerequisites for Log File Parser Monitoring Agent
Next Step
Configuration
Prerequisites for Log File Parser Monitoring Agent
Log File Parser Monitoring Agent