I need to hash sensitive-looking strings so I can reference them in logs without exposing the original content.

This feature hashes sensitive-looking strings before they are written to logs, so you can safely reference values without exposing the original content. It helps reduce the risk of leaking secrets while still enabling troubleshooting and correlation across events.

This feature detects strings that appear sensitive and replaces them with a deterministic hash when logging. The hashed value can be used as a stable identifier, allowing you to correlate repeated occurrences of the same underlying input across log lines and systems. Because the original string is not stored in logs, the risk of accidentally exposing credentials, tokens, or personal data is reduced. The hashing behavior is intended specifically for logging and observability scenarios where the content is not needed, only a consistent reference. It supports workflows such as tracking which requests used the same token, identifying repeated problematic inputs, or grouping incidents by recurring secret-like values. This approach also helps teams comply with internal security policies by minimizing sensitive material in telemetry. In operational use, engineers can search for the hashed identifier to follow an issue end-to-end without needing access to the original secret. The feature is especially useful in shared logging environments where many users or services can access logs. By hashing rather than logging raw values, you can preserve debugging utility while keeping sensitive content out of log storage and downstream analytics.