The decode JSON processing rule transforms an escaped JSON string into a structured JSON object. The resulting output includes both the original string and a new JSON object assigned to the key of your choosing.Documentation Index
Fetch the complete documentation index at: https://chronosphere-preview.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Configuration parameters
Use the parameters in this section to configure this processing rule. 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 escaped JSON string to transform. | log |
| Destination key | dst | Required. The key to store your transformed JSON object. If a key with this name already exists, the decode JSON rule will overwrite it. | decoded_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 decode JSON rule lets you extract embedded data from a string and turn it into parsable key/value pairs. You can then use these key/value pairs in other processing rules or for general storage and analysis. For example, given the following sample website log data:log and the Destination key
value output returns the following result:
log string and created a new JSON object
called output that contains a structured version of the same key/value pairs
that are embedded in log.