Overview
nxtLog collects logs from all registered nodes via file-based collection and syslog forwarding. Centralized log data flows into the log index for full-text search and alert-based detection. This page covers configuring log sources and troubleshooting ingestion issues.Prerequisites
- Administrator credentials with the
adminrole - nxtLog agents deployed on target nodes (see Agent Configuration)
Configuring Log Sources
- Dashboard
- Configuration File
View configured log sources
Navigate to Monitor Center > Logging (Log Sources, admin view). Each log source
defines a file path pattern, the node scope it applies to, and the expected
format.
Syslog Forwarding
Services that write to syslog rather than log files can forward directly to nxtLog’s syslog receiver.Configure rsyslog forwarding
Add a forwarding rule to
/etc/rsyslog.d/99-nxtradar.conf on the source node:/etc/rsyslog.d/99-nxtradar.conf
Use TCP forwarding (
@@) for reliable delivery. UDP forwarding (@) may drop
messages under high log volume and is not recommended for production.Log Format Parsers
Configure parsers for structured log formats to enable field-level filtering in Log Analytics:
For multiline logs (Java stack traces, Python tracebacks):
Multiline log source configuration
Next Steps
Agent Configuration
Deploy agents that run the log collection defined here
Retention Policies
Configure how long collected log data is retained
Log Analytics (User Guide)
How tenants query and create alerts from the logs you’ve configured
Troubleshooting
Diagnose log ingestion backlogs and missing log data