Skip to main content
This information is for Chronosphere Telemetry Pipeline, which is a standalone product separate from Chronosphere Observability Platform.
The lift submap processing rule uses regular expressions to search for key/value pairs inside a JSON object, then either moves or copies any applicable key/value pairs out of the JSON object and into a higher level of the record.

​
Configuration parameters

Use the parameters in this section to configure the . The Telemetry Pipeline web interface uses the items in the Name column to describe these parameters. Pipeline configuration files use the items in the Key column as YAML keys.

​
Examples

Using the lift submap rule lets you restructure your telemetry data by pulling key/value pairs out of a nested object and storing them as flat data in a higher level of the record. You can use this rule to simplify deeply nested data and store key/value pairs in more accessible locations.

​
Move key/value pairs

For example, given this sample log data:
A processing rule with the Key value $user.account, the Regex value id, the Levels value 1, and the Replacement key value account.%1 returns the following result:
This rule searched for applicable key/value pairs inside the account object, moved id up one level into a new key named account.id, and then removed account and the key/value pairs it originally contained.

​
Copy key/value pairs

You can also use the Keep original setting to copy key/value pairs out of an object instead of moving them. For example, given this sample log data:
A processing rule with the Key value $user.account, the Regex value id, the Levels value 1, the Replacement key value account.%1, and the Keep original setting enabled returns the following result:
This rule searched for applicable key/value pairs inside the account object, moved id up one level into a new key named account.id, but did not remove account and the key/value pairs it originally contained. For a processing rule with a similar effect, see flatten subrecord. For a processing rule with the opposite effect, see nest keys.