Overview

When processing incoming data, AxoRouter automatically converts everything to its internal message model, and maps the contents of the model to the specific destinations as needed. The internal message model of AxoRouter is based on the OpenTelemetry Log Data Model, so what is sent to the destination is determined by the log section of the model (the main payload is log.body).

The meta section contains all the information and metadata AxoRouter has about the message: what was its source, how it was received, where it will be forwarded, how was it classified, and so on. You can use these metadata for example:

• in the processing steps of the flows,
• on the search interfaces of Axoflow Console,
• during Flow tapping and Log tapping.

The related metrics of these data can be used:

• on the analytics pages, and
• in Flow tapping and log tapping filters.

When AxoRouter sends the message to its destination, parts of these metadata is automatically mapped into the relevant log field, but most of it (for example, labels) isn’t send to the destination by default.

For most destinations, there are specific fields that allow you to configure specific values that are sent to the destination, or to override the log.body field completely.

The message model has the following main elements:

• log: The log data structure describes the log record.
• meta: Metadata about a specific message record, for example, a log message.
• resource: The resource data structure describes the resource that generated the log record.
• scope: The scope data structure describes the Log Scope.