LogMan.io Collector configuration¶

LogMan.io Collector configuration typically consists of two files.

Collector configuration (/conf/lmio-collector.conf, INI format) specifies the path for pipeline configuration(s) and possibly other application-level configuration options.
Pipeline configuration (/conf/lmio-collector.yaml, YAML format) specifies from which inputs the data is collected (inputs), how the data is transformed (transforms) and how the data is sent further (outputs).

Collector configuration¶

/conf/lmio-collector.conf

[config]
path=/conf/lmio-collector.yaml

Pipeline configuration¶

Pipeline configuration is in a YAML format. Multiple pipelines can be configured in the same pipeline configuration file.

Every section represents one component of the pipeline. It always starts with either input:, transform:, output: or connection: and has the form:

input|transform|output:<TYPE>:<ID>

where <TYPE> determines the component type. <ID> is used for reference and can be chosen in any way.

Input specifies a source/input of logs.
Output specifies output where to ship logs.
Connection specifies the connection that can be used by output.
Transform specifies a transformation action to be applied on logs (optional).

Typical pipeline configuration for LogMan.io Receiver:

/conf/lmio-collector.yaml

# Connection to LogMan.io (central part)
connection:CommLink:commlink:
  url: https://recv.logman.example.com/

# Input
input:Datagram:udp-10002-src:
  address: 0.0.0.0 10002
  output: udp-10002

# Output
output:CommLink:udp-10002: {}

For the detailed configuration options of each component, see Inputs, Transformations and Outputs chapters. See LogMan.io Receiver documentation for the CommLink connection details.

Dynamic configuration from Web UI¶

Collector can be configured dynamically from Web UI. This means that the Collector configuration is stored on the Collector machine and can be updated without restarting the Collector through the CommLink communication channel with LogMan.io Receiver.