HA - Get proxy configurations for all data centers

This API call retrieves proxy configurations for all data centers in premium high availability deployments.

Authentication

To execute this request, you need the Service Provider API (ServiceProviderAPI) permission assigned to your API token. Generate your API token via Cluster Management Console (CMC). To learn how to obtain and use it, see Cluster API - Authentication.

Endpoint

/api/v1.0/onpremise/proxy/configurations

Parameter

Parameter
Type
Description
In
Required
dc
string

Data Center

path
required

Response

Response codes

Code
Type
Description
200

Success

404
-

Proxy is not configured for given Data Center

Response body objects

The InternetProxy object

Configuration of proxy server for Internet connection

Element
Type
Description
nonProxyHosts
string[]

Definition of hosts for which proxy won't be used.

port
integer

Port of proxy server

scheme
string

Protocol which proxy server uses

server
string

Address (either IP or Hostname) of proxy server

userOrPasswordDefined
boolean

Indicates if user/password for proxy is configured

Response body JSON model

{
"nonProxyHosts": [
"string"
],
"port": 1,
"scheme": "string",
"server": "string",
"userOrPasswordDefined": true
}

Example

In this example, you request to receive proxy configurations for all data centers. In return you receive JSON response listing of proxy configurations for eu-west-1 and us-east-1.

Curl

curl -X GET "https://myManaged.cluster.com/api/v1.0/onpremise/proxy/configurations" -H "accept: application/json"

Request URL

https://myManaged.cluster.com/api/v1.0/onpremise/proxy/configurations

Response body

{
"configurations": {
"eu-west-1": {
"scheme": "http",
"server": "outbound-proxy-dc1.dynatrace.com",
"port": 8080,
"nonProxyHosts": [
"https://mycompany.com/proxy/*",
"*.internal.lab.company.com"
],
"userOrPasswordDefined": true
},
"us-east-1": {
"scheme": "http",
"server": "outbound-proxy-dc2.dynatrace.com",
"port": 8080,
"nonProxyHosts": [
""
],
"userOrPasswordDefined": true
}
}
}

Response code

200