![]() This feature’s config.json setting is AdvancedLoggingConfig which can contain a filespec to another config file, a database DSN, or JSON. Logs are recorded asynchronously to reduce latency to the caller.Īdvanced logging supports hot-reloading of logger configuration. When using Advanced Logging for auditing, System Admins can capture the following auditing in the target configuration in addition to discrete log levels: Multiple TCP sockets: TCP socket target can be configured with an IP address or domain name, port, and optional TLS certificate.Īll access to the REST API or CLI is audited. Multiple syslogs: Supports local and remote syslog servers, with or without TLS transport. Multiple local file targets: Supports rotation and compression triggered by size and/or duration. For example, all errors could be routed to a specific destination for review.Īdditional configuration options include: Log certain entries to specific destinations. Mirror log output to files and log aggregators for redundancy. System Admins can define multiple log targets to: Please see Audit Log v2 for more comprehensive documentation. These targets have been chosen as they support the vast majority of log aggregators, and other log analysis tools, without needing additional software installed. Allow any combination of console, local file, syslog, and TCP socket targets, and send log records to multiple targets.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |