overrides.yaml 파일의 axHashSalt 속성을 사용해서 해시의 솔트 값을 설정할 수 있습니다. axHashSalt 속성은 민감한 분석 데이터를 난독화하기 위해 SHA512 해시를 계산할 때 솔트로 사용되는 값을 지정합니다. Apigee에서는 동일한 Apigee 조직을 호스팅하는 여러 다른 클러스터에서 동일한 값을 사용하는 것이 좋습니다.
다음 명령어를 사용하여 apigee-org 차트에서 값을 적용합니다.
[[["이해하기 쉬움","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-15(UTC)"],[[["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."]]],[]]
