Blog

Optimize SIEM data ingestion with automated classification. Improve accuracy, reduce costs, and eliminate log chaos. Learn how Axoflow can help!

Many things can go wrong in data ingestion; chances are high that data is ingested incorrectly, causing security operations and forensics investigations to miss these events. Most organizations don’t have monitoring and controls to notice if something changes or goes wrong. Axoflow helps you avoid these problems by automatically detecting and handling multiple protocols and message formats and by alerting you on problems that it cannot handle automatically.

Discover how high-quality security data can dramatically cut SIEM costs, improve detection accuracy, and enhance SOC efficiency. Learn real-world strategies and a customer success story that saved 50% on SIEM spend.

How to upgrade your syslog-ng installation to AxoSyslog in minutes, without any configuration changes

Discover what's new in AxoSyslog 4.10.0! This release introduces Google Pub/Sub gRPC, Sentinel, and Azure Monitor destinations for enhanced cloud integration. Read on for key features and configuration examples."

Axoflow will use its $7 million seed funding to make security data easy-to-handle everywhere: during collection, routing, and in the SIEM.

Top 4 tricks to get started with reducing security data volume

Learn how security data pipeline management tools like Axoflow improve data quality, cut SIEM costs, and boost security team efficiency.

Activity report of the first six months of AxoSyslog, the binary-compatible syslog-ng fork.

AxoSyslog 4.9 highlights: ClickHouse destination, gRPC improvements, new FilterX features, and bug fixes for the AxoSyslog and the syslog-ng projects.

Our automated data engine solves syslog issues: fixes, optimizes, and structures security logs before they reach your SIEM, improving performance and accuracy

FilterX makes filtering and modifying log messages easier and faster. It supports even the most complex log formats, including deeply nested JSON objects and OpenTelemetry logs. FilterX is a replacement for syslog-ng filter statements, parsers, and rewrite rules.

Discover how AxoSyslog enhances log management by automatically detecting and tagging formatting errors in syslog messages. Improve data quality, reduce false positives, and streamline your security operations with Axoflow!

AxoSyslog is now a real fork of syslog-ng™. This blog post shows our plans going forward. TL;DR: AxoSyslog remains open source, uses the same license as syslog-ng™, and we continue to maintain it and add new features in the AxoSyslog repository.

Metrics, management, and alternatives for syslog-ng Premium Edition. Modernize your syslog-ng based logging infrastructure without disrupting your deployments!

Metrics and management for telemetry pipelines based on Syslog Connect for Splunk (SC4S) and Splunk: observe your telemetry pipeline in real time!

Meet us at KubeCon Europe 2024 in Paris at Booth L36!

Metrics and management for syslog-ng based enterprise logging and telemetry pipelines

Packet drops and buffering in syslog and observability pipelines

syslog-ng 4.6 allows you to send data directly to Google BigQuery, better collect logs on macOS, parse Windows XML logs, and improves OpenTelemetry performance

Learn how to create usable log messages by configuring log severity levels, with special focus on Python, OpenTelemetry, and syslog log levels.

Learn how to create usable log messages by configuring log severity levels, with special focus on Python, OpenTelemetry, and syslog log levels.

Documentation updates for AxoSyslog, the cloud-native syslog-ng distribution: OpenTelemetry support, Splunk HEC destination, eBPF support, and new parsers

How to parallelize syslog message processing to scale syslog over UDP reception on a single node: dos, dont's, and trade-offs, and the power of eBPF.

Republishing syslog-ng documentation in a new format, under the AxoSyslog Core name to comply with the syslog-ng Open Source Edition documentation license

syslog-ng disk buffering benefits, and how to configure it to prevent data loss from local and upstream failure modes like crashes, network outages, overloads.

Using syslog over UDP can lead to significant message loss. Here's how you can tune the kernel and syslog-ng parameters to minimize the risk of losing messages

Users report that syslog over UDP loses 30-40% of their messages. Learn why messages are dropped and how you can solve or at least mitigate the problems.

Users report that syslog over UDP loses 30-40% of their messages. Learn why messages are dropped and how you can solve or at least mitigate the problems.

Logs have been my passion for over two decades now. As a 3rd-year university student, I started an Open Source project to fix the “syslogd” problem. syslogd was the standard solution at that time to collect, deliver and aggregate system and device logs. The new project was named “syslog, the next generation” or syslog-ng for short. Well, 25 years on and we are now launching Axoflow – where we are bringing to market a long-overdue capability for the burgeoning Observability space that we anticipate will have similar impact!

Log data as collected from operating systems, appliances, and applications is extremely unstructured. You can't imagine how much so. Unless you are an analyst working with logs or you have a past where you were "grepping" data in log files, you are probably not aware of the infinite variety of formats and lack of standardization. If this is the case, you likely have a less-than-complete understanding of the story logs can tell – be it security incidents, IT operations irregularities, and a myriad of other business insights.