Blog

Detection rules fail silently when parsers miss schema changes. Learn how autonomous classification keeps your fields where your detections expect them.

From SIEM cost control to AI-ready data, security telemetry pipelines are emerging as a critical layer for managing security data at scale.

A government organization cut infrastructure by 85% and log volume by 40% with Axoflow's security data pipeline during its Google SecOps migration.

Gain strategic control with Axoflow's autonomous data layer: Axolake, AxoStore, and Locker for automated curation, cost cuts, and compliance.

Axoflow's storage strategy for the Security Data Layer: edge storage, cost-efficient data lakes, stream processing, and air-gapped deployments.

Learn why many security data pipeline vendors fail to provide real value despite claiming to support dozens of destinations, and how real integrations bring faster investigations, lower bills, and better data for your SOC teams.

Key findings from Splunk's 2025 State of Security report: poor data quality and alert overload drive SOC burnout. How automated pipelines help.

Optimize firewall logs before they hit Splunk with AxoRouter: better data quality, lower ingestion costs, no more noisy unstructured messages.

Real telemetry automation means no manual parser fixes and no AI babysitting. How Axoflow delivers detection-ready data, fully automated.

How Axoflow natively integrates with Google SecOps, GKE, Pub/Sub, BigQuery, and Private Service Connect to secure your security data pipelines.

Axoflow does automatic parsing and labeling, so you can route your data using static and dynamic labels, instead of static, low-level rules.

Discover the flexible deployment modes of Axoflow, and learn how you can streamline SIEM data management, reduce costs by 50%, and improve data quality.

Without reliable host attribution, security teams lose vital context. Axoflow's inventory enriches data so you can pinpoint every event's source.

AxoRouter auto-identifies log sources and fixes missing hostnames, invalid timestamps, and formatting errors. No rule maintenance required.

Telemetry Controller turns logs, metrics, and traces into Kubernetes resources with a multi-tenant API built on top of OpenTelemetry.

Log tapping samples your pipeline's log flow on demand. Filter by labels and investigate problematic syslog events with just a few clicks.

Logging operator is now a CNCF sandbox project - how does it affect you, and what are the future plans for Logging operator? What is a Telemetry Pipeline for Kubernetes?

I'll be giving talks at ContainerCon (part of OSSummit EU) and Observability Day (KubeCon NA) about log collection best practices in multi-tenant Kubernetes environments and the Telemetry Controller