[[["容易理解","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 feature allows for the obfuscation of sensitive analytics data in Apigee hybrid versions 1.2 and newer by hashing specific fields using SHA512 before sending it from the runtime plane to the control plane."],["The `axHashSalt` property in the `overrides.yaml` file is used to specify the salt value for the SHA512 hash, and it's recommended to use the same value across different clusters within the same Apigee organization."],["Obfuscation can be enabled for each environment by setting `features.analytics.data.obfuscation.enabled` to `true` using a `PUT` request, however, ensure to include all properties when using the PUT request, as it overwrites the entire property set."],["With obfuscation enabled, Apigee hashes fields such as `client_ip`, `developer_email`, `request_uri`, `proxy_pathsuffix`, and others, ensuring sensitive data is protected and is reflected in analytics dashboards."],["Note that analytics reports will display unhashed data if it was communicated from the runtime plane before enabling obfuscation or after disabling the feature."]]],[]]
