Skip to main content
This information is for Chronosphere Telemetry Pipeline, which is a standalone product separate from Chronosphere Observability Platform.
The hash key processing rule copies the value of a specified source key, hashes that value, then stores the hashed copy in a specified destination key.
Unless you configure this rule to overwrite the specified source key, the resulting output will still include the source key and its original, un-hashed value.

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.

Example

Using the hash keys rule lets you store values in hashed format, which can help validate the authenticity and integrity of your data. For example, given the following sample website log data:
A processing rule with the Source key value action, the Encoding algorithm value Hexadecimal, and the Hash algorithm value SHA256 returns the following result:
This rule hashed the value of action from each log entry and stored the hashed value in a new key named action_sha256.