Updates the configuration of mapping between IP addresses and geographic regions.
The request consumes an application/json
payload.
PUT | SaaS | https://{your-environment-id}.live.dynatrace.com/api/config/v1/geographicRegions/ipAddressMappings |
Environment ActiveGate | https://{your-activegate-domain}:9999/e/{your-environment-id}/api/config/v1/geographicRegions/ipAddressMappings |
To execute this request, you need an access token with WriteConfig
scope.
To learn how to obtain and use it, see Tokens and authentication.
The JSON body of the request. Contains the configuration of the IP address mapping.
IpAddressMappings
objectConfiguration of the IP address mappings to geographic locations.
A list of IP address mapping rules.
Rules are evaluated from top to bottom; the first matching rule applies.
IpAddressMappingRule
objectConfiguration of the IP address mapping to the geographic location.
The IP address or the IP address range to be mapped to the location.
IpAddressMappingLocation
objectThe location for an IP address mapping.
The city name of the location.
The country code of the location.
To fetch the list of available country codes, use the GET all countries request.
The latitude of the location in DDD.dddd
format.
The longitude of the location in DDD.dddd
format.
The region code of the location.
To fetch the list of available region codes, use the GET regions of the country request.
IpAddressRange
objectThe IP address or the IP address range to be mapped to the location.
The IP address to be mapped.
For an IP address range, this is the from address.
The to address of the IP address range.
The subnet mask of the IP address range.
This is a model of the request body, showing the possible elements. It has to be adjusted for usage in an actual request.
{"ipAddressMappingRules": [{"ipAddressMappingLocation": {"city": "string","countryCode": "string","latitude": 1,"longitude": 1,"regionCode": "string"},"ipAddressRange": {"address": "string","addressTo": "string","subnetMask": 1}}]}
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/geographicRegions/ipAddressMappings/validator |
Environment ActiveGate | https://{your-activegate-domain}:9999/e/{your-environment-id}/api/config/v1/geographicRegions/ipAddressMappings/validator |
To execute this request, you need an access token with WriteConfig
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.