This information is for Chronosphere Telemetry Pipeline, which is a standalone product separate from Chronosphere Observability Platform.
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.| Name | Key | Description | Default |
|---|---|---|---|
| Source key | src | Required. The key that contains the JSON object to transform. | none |
| Destination key | dst | Required. The key to store your escaped JSON string. If a key with this name already exists, the encode JSON rule will overwrite it. | encoded_json |
| Comment | comment | A custom note or description of the rule’s function. This text is displayed next to the rule’s name in the Actions list in the processing rules interface. | none |
Example
Using the encode JSON rule lets you condense a structured object into a single, condensed value. For example, given the following sample website log data:event and the Destination key
value stored_string returns the following result:
event object and created a new key called
stored_string to store the same key/value pairs as an embedded string.

