Architecture

The Telemetry Router ingests telemetry and audit data from your STACKIT cloud products. It routes the data stream to your custom defined destinations. You can add custom filters, so that you can reduce the data stream to the content you need.

Filter

You can freely configure the filter for each Telemetry Router instance. Each configuration element is called an attribute and is identified by its key. Each filter attribute operates at one of three levels:

• resource
• scope
• logRecord

You then provide expressions, that match the objects that are represented by these levels. Each expression is built by a matcher and a value that is matched. The following options for matcher are available:

Matcher

Type of matchers

• =: Matches an expression.

  The = matcher includes a list of the matching expressions.

• !=: Negates an expression match.

  The != matcher does not include a list of the matching expressions.

The value parameter

With the value parameter you configure what actually should be evaluated by the matcher. It is an array of strings.

A value is an array of strings and not a regular expression.

Destinations

For every Telemetry Router instance you define destinations to which your data stream is forwarded to. You can send the stream to an Open Telemetry compatible endpoint or to a S3 compatible Object Storage. You can either use Basic- or Token-Auth to let your Telemetry Router instance authenticate against your destination. You define the actual destination endpoint with an URI.