builtin:networkzones)
In combination with ActiveGates, network zones save bandwidth and infrastructure costs by
builtin:networkzones
group:preferences
environment
environment-default
GET | Managed | https://{your-domain}/e/{your-environment-id}/api/v2/settings/schemas/builtin:networkzones |
SaaS | https://{your-environment-id}.live.dynatrace.com/api/v2/settings/schemas/builtin:networkzones | |
Environment ActiveGate | https://{your-activegate-domain}/e/{your-environment-id}/api/v2/settings/schemas/builtin:networkzones |
To execute this request, you need an access token with Read settings (settings.read
) scope. To learn how to obtain and use it, see Tokens and authentication.
enabled
For details, see Network zones.
⚠ Warning: You may experience network imbalance if you suddenly disable network zones in an environment that has a high number of OneAgents with network zone configuration. To avoid this and to ensure smooth adoption of network zones, follow best practices for planning and proper naming, as explained in Network zones.