Fitur ini memungkinkan Anda menyamarkan data sebelum mengirimnya sebagai bagian dari payload analisis.
Dengan fitur ini, Apigee menggunakan SHA512 untuk melakukan hashing pada nilai asli sebelum mengirim data dari platform runtime ke platform kontrol.
Anda dapat menetapkan nilai salt untuk hash dengan properti axHashSalt dalam file overrides.yaml. Properti axHashSalt menentukan nilai yang digunakan sebagai salt saat menghitung hash SHA512 untuk mengaburkan data analisis sensitif. Apigee
merekomendasikan penggunaan nilai yang sama di berbagai cluster yang menghosting organisasi Apigee yang sama.
Terapkan nilai dengan diagram apigee-org dengan perintah berikut:
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-18 UTC."],[[["\u003cp\u003eThis feature allows Apigee hybrid 1.2 and newer to obfuscate sensitive analytics data by hashing specific fields with SHA512 before sending it to the analytics backend.\u003c/p\u003e\n"],["\u003cp\u003eYou can set a salt value for the SHA512 hash using the \u003ccode\u003eaxHashSalt\u003c/code\u003e property in the \u003ccode\u003eoverrides.yaml\u003c/code\u003e file, and it is recommended to use the same salt across different clusters within the same Apigee organization.\u003c/p\u003e\n"],["\u003cp\u003eTo enable this data obfuscation feature, you must set \u003ccode\u003efeatures.analytics.data.obfuscation.enabled\u003c/code\u003e to \u003cstrong\u003etrue\u003c/strong\u003e for each environment via a PUT request, ensuring you include all other properties for that environment.\u003c/p\u003e\n"],["\u003cp\u003eOnce enabled, Apigee will hash a set list of fields (such as client_id, client_ip, and request_uri) and dimension values in custom reports to protect sensitive information, which will be reflected in the Apigee analytics dashboard.\u003c/p\u003e\n"],["\u003cp\u003eThe obfuscated data is displayed in the Apigee hybrid analytics dashboard, though it may take a few minutes for the hashed results to appear in the user interface, and previously unhashed data before enabling the feature will still be displayed.\u003c/p\u003e\n"]]],[],null,["# Obfuscate user data for analytics\n\n| You are currently viewing version 1.12 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\nThis feature allows you to obscure data before sending it as part of the analytics payload.\nWith this feature, Apigee uses SHA512 to hash the original value before sending data from the runtime\nplane to the control plane.\n\nFor additional information on using data obfuscation, including information on enabling the\nfeature in environments, see [Obfuscate user data for Apigee API Analytics](/apigee/docs/api-platform/analytics/obfuscate-user-data-for-analytics).\n\nSet the salt value in Apigee hybrid\n-----------------------------------\n\nYou can set the salt value for the hash with the\n[`axHashSalt`](/apigee/docs/hybrid/v1.12/config-prop-ref#axhashsalt)\nproperty in the `overrides.yaml` file. The `axHashSalt` property specifies a\nvalue used as a salt when computing SHA512 hashes to obfuscate sensitive analytics data. Apigee\nrecommends using the same value across different clusters that host the same Apigee organization.\nApply the value with the `apigee-org` chart with the following command: \n\n```\n helm upgrade ORG_NAME apigee-org/ \\\n --namespace apigee \\\n --atomic \\\n -f overrides.yaml\n \n```"]]
