[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-07-10 (世界標準時間)。"],[[["This document outlines a feature in Apigee hybrid 1.2 and newer that obfuscates sensitive analytics data by hashing it with SHA512 before it's sent from the runtime plane to the control plane."],["You can configure the salt value used for hashing via the `axHashSalt` property in the `overrides.yaml` file, and it's recommended to maintain the same salt value across clusters within the same Apigee organization."],["The obfuscation feature can be enabled for specific environments by setting `features.analytics.data.obfuscation.enabled` to `true` using a `PUT` request, ensuring all environment properties are included to avoid overwriting."],["With this feature enabled, fields like `client_id`, `client_ip`, `developer_email`, and others are hashed, and the obfuscated data will be visible in the Apigee hybrid analytics dashboard after a short delay."],["Data sent before enabling obfuscation, or after disabling it, will display as unhashed in the analytics reports, and the document also showcases an example of data before and after being obfuscated."]]],[]]
