Calyptia Core Agent
Calyptia Core Agent Documentation
Differences from Open Source
Performance and Benchmarking
Getting Started with Calyptia Core Agent
Configuring Calyptia Core Agent
Buffering & Storage
Scheduling and Retries
Validating your Data and Structure
Running a Logging Pipeline Locally
Calyptia Core Agent for Developers
Golang Output Plugins
WASM Filter Plugins
WASM Input Plugins
Create flexible routing rules
Routing is a core feature that allows to
your data through Filters and finally to one or multiple destinations. The router relies on the concept of
There are two important concepts in Routing:
When the data is generated by the input plugins, it comes with a
(most of the time the Tag is configured manually), the Tag is a human-readable indicator that helps to identify the data source.
In order to define
the data should be routed, a
rule must be specified in the output configuration.
Consider the following configuration example that aims to deliver CPU metrics to an Elasticsearch database and Memory metrics to the standard output interface:
Note: the above is a simple example demonstrating how Routing is configured.
Routing works automatically reading the Input Tags and the Output Match rules. If some data has a Tag that doesn't match upon routing time, the data is deleted.
Routing with Wildcard
Routing is flexible enough to support
pattern. The below example defines a common destination for both sources of data:
The match rule is set to
which means it will match any Tag that starts with