AxoSyslog
Menu
Solutions
Comparisons
Axoflow vs Cribl
Axoflow vs NXLog
Axoflow vs SC4S
Axoflow vs syslog-ng PE
Use Cases
Cost Reduction
SIEM Migration
Data Governance
Pipeline Unification
AI SOC Data Layer
Storage Solutions
Log Management
Cut Your Anthropic Bill
For Managed Service Providers
Case Studies
Case studies
Case study - Storage Modernization
Case Study - Migrating to Google SecOps
Case Study – Cost and MTTR Reduction
Case Study – Data Reduction
Case Study – Data Quality Improvement
Products
Axoflow Platform
AxoLake
AxoRouter
Axoflow + AI
Integrations
Axoflow + Google Cloud
Axoflow + Splunk
Axoflow + Microsoft Sentinel
Axoflow + Dynatrace
Other integrations
Capabilities
Collection
Processing
Routing
Storage
Management
Resources
Blog
Documentation
Overview
Axoflow Platform
Webinars
Show me your labels
Solve the Malformed Message Madness
Reduced and Actionable Security Data
Parsing Sucks
Resilient Syslog Architectures
Overview
White Papers
Optimize Splunk Performance
Observability Pipeline and Metrics
Scalable Syslog Architectures
Overview
Podcast
Support & Professional Services
Open Source
AxoSyslog
AxoSyslog Documentation
Logging Operator Documentation
Syslogopedia
About
About us
News
Contact
Our Partners
Login
Request Sandbox
Light
Dark
Auto
Documentation
AxoSyslog
The concepts of AxoSyslog
The concepts of AxoSyslog
This chapter discusses the technical concepts of AxoSyslog.
The philosophy of AxoSyslog
Logging with AxoSyslog
Modes of operation
Global objects
Timezones and daylight saving
Product licensing
High availability support
The structure of a log message
Message representation in AxoSylog
Structuring macros, metadata, and other value-pairs
Things to consider when forwarding messages between AxoSyslog hosts
Last modified October 22, 2023:
Use product.abbrev variable instead of product.ose (5c18e404)