Updates the global configuration of data privacy, affecting all your applications.
The request consumes an application/json
payload.
PUT | SaaS | https://{your-environment-id}.live.dynatrace.com/api/config/v1/dataPrivacy |
Environment ActiveGate | https://{your-activegate-domain}:9999/e/{your-environment-id}/api/config/v1/dataPrivacy |
To execute this request, you need an access token with DataPrivacy
scope.
To learn how to obtain and use it, see Tokens and authentication.
DataPrivacyAndSecurity
objectGlobal configuration for data privacy and security.
The audit logging is enabled (true
) or disabled (false
).
Masking of IP addresses and GPS coordinates is enabled (true
) or disabled (false
).
Masking of personal data in URIs is enabled (true
) or disabled (false
).
Masking of user action names is enabled (true
) or disabled (false
).
This masking is available only for web applications.
ConfigurationMetadata
objectMetadata useful for debugging
Dynatrace version.
A sorted list of the version numbers of the configuration.
A sorted list of version numbers of the configuration.
This is a model of the request body, showing the possible elements. It has to be adjusted for usage in an actual request.
{"logAuditEvents": true,"maskIpAddressesAndGpsCoordinates": true,"maskPersonalDataInUris": true,"maskUserActionNames": true,"metadata": {"clusterVersion": "1.192.1","configurationVersions": [4,2],"currentConfigurationVersions": ["1.0.4","1.23"]}}
Success. The configuration has been updated. Response doesn't have a body.
We recommend that you validate the payload before submitting it with an actual request. A response code of 204 indicates a valid payload.
The request consumes an application/json
payload.
POST | SaaS | https://{your-environment-id}.live.dynatrace.com/api/config/v1/dataPrivacy/validator |
Environment ActiveGate | https://{your-activegate-domain}:9999/e/{your-environment-id}/api/config/v1/dataPrivacy/validator |
To execute this request, you need an access token with DataPrivacy
scope.
To learn how to obtain and use it, see Tokens and authentication.
Success. The submitted configuration is valid. Response doesn't have a body.
In this example, the request updates the data privacy configuration from the GET request example. It activates the Mask user actions and Mask personal data in URLs features.
The API token is passed in the Authorization header.
You can download or copy the example request body to try it out on your own. First, be sure to create a backup copy of your current configuration with the GET data privacy configuration call.
curl -X PUT \https://mySampleEnv.live.dynatrace.com/api/config/v1/dataPrivacy \-H 'Authorization: Api-Token dt0c01.abc123.abcdefjhij1234567890' \-H 'Content-Type: application/json' \-d '{<truncated - see the Request body section below>}'
https://mySampleEnv.live.dynatrace.com/api/config/v1/dataPrivacy
{"maskIpAddressesAndGpsCoordinates": true,"maskUserActionNames": true,"maskPersonalDataInUris": true,"logAuditEvents": true}
204