# AxoSyslog documentation New to AxoSyslog? AxoSyslog is a binary compatible `syslog-ng` replacement, from the original creator, developed by the same team. Same architecture, same config files, same paths. Cloud-native images, fast releases, modern observability (OTel, K8s), and powerful data processing: read more about the [differences between AxoSyslog and `syslog-ng`](). Also, it’s super easy to [install](docs/axosyslog-core/install/index.md), and you can [upgrade from `syslog-ng` in minutes](docs/axosyslog-core/install/upgrade-syslog-ng/index.md). AxoSyslog is a scalable, open source security data processor by [Axoflow](). AxoSyslog is a drop-in replacement for `syslog-ng`, created by the original creators of `syslog-ng`. (It started as a fork, branched after syslog-ng™ v4.7.1). ## AxoSyslog, the drop-in `syslog-ng` replacement AxoSyslog provides the: * same binaries (for example, `/usr/sbin/syslog-ng`), * same configuration files (`/etc/syslog-ng/syslog-ng.conf`), certificates, etc., * same configuration syntax, and the * same license and development practices. If you’re already using `syslog-ng`, you can [upgrade your existing `syslog-ng` deployments to AxoSyslog](docs/axosyslog-core/install/upgrade-syslog-ng/index.md) in a matter of minutes. ## More than just a replacement AxoSyslog also provides: * detailed metrics about what your pipeline is doing, * the [FilterX data processing engine](docs/axosyslog-core/filterx/index.md), * enhanced container and Kubernetes support, including [Helm charts](docs/axosyslog-core/install/helm/index.md), * eBPF integration for efficient kernel-level data collection with minimal overhead, * destinations for [ClickHouse](docs/axosyslog-core/chapter-destinations/clickhouse/index.md), [Microsoft Sentinel, Azure Monitor](docs/axosyslog-core/chapter-destinations/azure-monitor/index.md), [Google Pub/Sub](docs/axosyslog-core/chapter-destinations/google-pubsub-grpc/index.md), and many more modern services, * [regular releases]() with new features, and * responsive and helpful [community and professional support for AxoSyslog and `syslog-ng`](docs/axosyslog-core/support/index.md). If you want to try running `syslog-ng` in a container, or use it as a log collector in Kubernetes, try AxoSyslog! See [Install AxoSyslog](docs/axosyslog-core/install/index.md) to get started. ## Feedback Any feedback is greatly appreciated, especially on what else this document should cover. General comments, errors found in the text, and any suggestions about how to improve the documentation are also welcome as [GitHub issues](), or on the [Axoflow Discord server](). ## Support In case you need help with any of the AxoSyslog projects, or directly with `syslog-ng`, you have several ways to contact us: * Open a [GitHub issue in the AxoSyslog repository](). * Chat with us in the [syslog-ng or axosyslog channels of the Axoflow Discord server](). * Fill the [Axoflow contact form](). We also provide consulting and professional services for logging and observability related projects. [Contact us]() if you need our help! ## Documentation license This documentation is originally based on the [syslog-ng Open Source Edition documentation]() for version 3.38 and is used in compliance with the terms of [The syslog-ng Open Source Edition Documentation License](docs/axosyslog-core/documentation-license/index.md). We are continuously working on it to keep it up-to-date with the latest released version of [AxoSyslog]() (currently 4.25). In compliance with the above license, `syslog-ng` is used only to refer to the binary of the application, or in filenames, pathnames, and similar technical terms. For all other references, we use the AxoSyslog name. Syslog-ng is a trademark of One Identity. New files and modifications compared to the [syslog-ng Open Source Edition documentation]() are under the copyright of Axoflow, and licensed under Apache License 2.0, except for using the Axoflow and AxoSyslog trademarks. The Axoflow and AxoSyslog trademarks and logos are trademarks of Axoflow Inc. All other trademarks are property of their respective owners. This documentation is maintained by Axoflow, and continually updated for new releases. ## Acknowledgements We would like to express our gratitude to everyone involved with the project, including the syslog-ng developers, advocates, and documentation maintainers who worked at BalaBit or are still working at One Identity, or who helped the project as external contributors, users, or as part of the community. Last modified July 7, 2025: [Adds banner to high-traffic pages (8f28f4e1)]()