For Dynatrace Managed / Classic Problem Notifications, there is no dedicated SOAP integration. However, Custom Integration supports sending a custom payload through HTTP POST and allows the required Additional HTTP headers to be configured.
By default, the Custom Integration expects a JSON payload. If a different Content-Type is configured, Dynatrace skips the default JSON validation, allowing a different payload format such as XML to be sent.
For example, depending on the requirements of your SOAP endpoint, you may configure the following under Additional HTTP headers:
- Name: Content-Type
- Value: text/xml; charset=UTF-8
If required by the endpoint, an additional header can also be configured:
- Name: SOAPAction
- Value: <SOAP action required by your endpoint>
For SOAP 1.2, the endpoint may instead require a content type such as:
- Name: Content-Type
- Value: application/soap+xml; charset=UTF-8
The exact Content-Type, SOAPAction, authentication headers, and SOAP/XML payload structure depend on the requirements of the receiving SOAP service.
Therefore, we recommend configuring Problem Notifications → Custom Integration with the HTTP headers and SOAP/XML payload required by your endpoint and performing an end-to-end test from your side.
Dynatrace will send the configured HTTP POST request, headers, and payload, while validation and processing of the SOAP request are handled by the receiving endpoint.
