Retagger

The Retagger is a sequencer block, that allows rewriting of the Path in the Data and Definitions events based on the metadata received earlier via Definition messages.

Retagger can be used to alter the Path of the values logged by CDPLogger. Typically this altering is needed before sending the logged data to some log consolidation service (like the cloud log server). Retagger can do different manipulations for the Path. These can be simple modifications like prefixing the Path or changing the Path separator from the CDP Path separator i.e. dot (.) to some other separator like a slash (/). But the Retagger is mostly meant to be used for complete Path rewriting (i.e. retagging), based on tagging information that was gathered and attached to the logged values from different levels of the CDP system.

The following is a block diagram of the typical usage of the Retagger block:

Events

Arguments

Properties

Example 1 - Path Rewriting Based On Tags

This example shows how to use the Retagger to rewrite the home automation system CDP application Paths to be somewhat easier to read and to be in a unified pattern, like /DATA/{optional roomname}/{devicename-counter#}/{metric} .

For that, the room and device tags should be added to the CDP nodes that correspond to rooms and devices accordingly, and the CDPLogger should be configured to find them. For example, let's assume the following tags for these CDP nodes have been configured:

After these additional tags are added, the CDPLogger.ValueLogReader will start to emit these Tags with Definition events, for example for some logged values like this:

Now, the Retagger can be configured to use these tag metadata like this:

With the configuration and definitions above, and with the Definition event routed from CDPlogger, the Retagger will rewrite the Paths to the Definition and Data output events, like this:

Example 2 - Auto-Count Logged Values

For some simple setups, it can be enough to just auto-count logged sensor values without the need to add any tag information, to a pattern like /SENSORS/{metricname-2-digit-counter#}

For that, the Retagger can be configured to benefit pre-configured label tag included with every logged value, like this:

With the configuration above, and with the Definition event routed from CDPlogger, the Retagger will rewrite the Paths to the Definition and Data output events, like this:

Example 3 - Prefix and Replace Path Separator

For some simple cases, it can be enough to just prefix the CDP original Path with a prefix and with different path separator (slash).

For that, the Retagger can be configured to benefit PathSeparator replaced Path, like this:

With the configuration above, and with the Definition event routed from CDPLogger, the Retagger will rewrite the Paths like the Definition and Data output events, like this: