AxoSyslog scalable security data processor
  • Solutions
    • Comparisons
      • Axoflow vs Cribl
      • Axoflow vs syslog-ng PE
      • Axoflow vs SC4S
      • Axoflow vs syslog-ng
    • Case Studies
      • Global Industrial Concern
      • Large Government Organization
  • Product
      Axoflow Platform AxoRouter
  • Resources
      Blog
    • Documentation
      • Axoflow Platform
      • AxoSyslog
      • Logging operator
    • Webinars
      • Show me your labels
      • Solve the Malformed Message Madness
      • Reduced and Actionable Security Data
      • Parsing Sucks
      • Resilient Syslog Architectures
    • White Papers
      • Observability Pipeline and Metrics
      • Scalable Syslog Architectures
  • About
      News About us Contact
  • Login
  • Request Sandbox

Join us at Gartner Security & Risk Management Summit in National Harbor , MD! June 9 – 11

Search
  • AxoSyslog documentation
    v4.10.0
    Search
Fighting data
Loss?
Balázs Scheidler

Book a free 30-min consultation with syslog-ng creator Balázs Scheidler

Book a Call
On This Page
Page(/chapter-examples/_index.md)
View page source Edit this page Create child page Create documentation issue Create project issue Print entire section
banner_webinar_reduce_data
banner_webinar_reduce_data
banner_webinar_reduce_data
banner_webinar_reduce_data
banner_webinar_reduce_data
banner_webinar_reduce_data
banner_malformed_message_madness_live
  1. Documentation
  2. AxoSyslog scalable security data processor
  3. Best practices and examples

Best practices and examples

This chapter discusses some special examples and recommendations.


General recommendations

Handling large message load

Using name resolution in syslog-ng

Collecting logs from chroot

Configuring log rotation

Load balancing logs between multiple destinations

Last modified July 17, 2023: Python modules (#4) (c561a28)
Privacy Policy

Copyright 2023-2025 Axoflow Inc.
All Rights Reserved
right-logo