Applications detection rules API - PUT host detection headers
Updates the list of the host detection headers.
The request consumes an application/json
payload.
PUT | SaaS | https://{your-environment-id}.live.dynatrace.com/api/config/v1/applicationDetectionRules/hostDetection |
Environment ActiveGate | https://{your-activegate-domain}:9999/e/{your-environment-id}/api/config/v1/applicationDetectionRules/hostDetection |
Authentication
To execute this request, you need an access token with WriteConfig
scope.
To learn how to obtain and use it, see Tokens and authentication.
Parameters
The JSON body of the request. Contains the configuration of host detection headers.
Request body objects
The ApplicationDetectionRulesHostDetectionSettings
object
Configuration of host detection headers.
An ordered list of host detection headers.
Headers are evaluated from top to bottom; the first matching header applies.
The ConfigurationMetadata
object
Metadata useful for debugging
Dynatrace version.
A sorted list of the version numbers of the configuration.
A sorted list of version numbers of the configuration.
Request body JSON model
This is a model of the request body, showing the possible elements. It has to be adjusted for usage in an actual request.
{"hostDetectionHeaders": ["X-Host","X-Forwarded-Host"],"metadata": {"clusterVersion": "Mock version","configurationVersions": [4,2]}}
Response
Response codes
Success. The configuration has been updated. Response doesn't have a body.
Validate payload
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/applicationDetectionRules/hostDetection/validator |
Environment ActiveGate | https://{your-activegate-domain}:9999/e/{your-environment-id}/api/config/v1/applicationDetectionRules/hostDetection/validator |
Authentication
To execute this request, you need an access token with WriteConfig
scope.
To learn how to obtain and use it, see Tokens and authentication.
Response
Response codes
Success. The submitted configuration is valid. Response doesn't have a body.