Dynatrace Integration

This guide explains how to automatically send Dynatrace problems to ITOC360 using a webhook.

1. Create the workflow Head over to the Workflows menu on the left panel. The list will be empty if you haven't made one before. Just click the button at the top right to start a new one.

2. Set up the trigger We want this to run whenever an alert pops up, so grab the Davis problem trigger. In the configuration panel on the right, set it up like this:

• Event state: Keep it as active or closed

• Event category: Add the ones you need. Usually, it's Availability, Custom, Error, Monitoring unavailable, Resource, Slowdown, and Info.

3. Configure the HTTP Request Now drop an HTTP Request action right below your trigger. This is what actually sends the payload out.

• Method: POST

• URL: https://api.itoc360.app/functions/v1/events?token<x-itoc360-token>

• Payload: You can just copy and paste the JSON block below. It basically maps the Dynatrace variables to the format ITOC360 expects.

JSON

{
  "ProblemID": "{{ event().get('display_id', event().get('event.id', 'unknown')) }}",
  "ProblemTitle": "{{ event().get('title', event().get('event.name', 'No title')) }}",
  "State": "{{ event().get('event.status', 'ACTIVE') }}",
  "Severity": "{{ event().get('severity', 'CUSTOM') }}",
  "ImpactedEntity": "{{ event().get('affected_entity_types', '') }}",
  "ProblemURL": "{{ event().get('problemUrl', '') }}",
  "Timestamp": "{{ event().get('timestamp', '') }}"
}

Using legacy Dynatrace?

The payload above only works on the current Dynatrace platform, which uses Workflows and Jinja-style expressions. On legacy environments the {{ event().get(...) }} syntax is not evaluated and the placeholders arrive as literal text.

If your environment shows Settings → Integration → Problem notifications instead of Workflows, you are on the legacy generation. Set up a Custom Integration notification there, point the Webhook URL at the same ITOC360 endpoint, add a Content-Type: application/json header, and use this payload instead:

json

{
  "ProblemID": "{ProblemID}",
  "ProblemTitle": "{ProblemTitle}",
  "State": "{State}",
  "Severity": "{ProblemSeverity}",
  "ImpactedEntity": "{ImpactedEntity}",
  "ProblemURL": "{ProblemURL}",
  "Timestamp": ""
}

Legacy placeholders use single curly braces. Don't mix the two syntaxes — they are not interchangeable. Timestamp is intentionally left empty because legacy Dynatrace has no equivalent placeholder; ITOC360 uses its own receive time instead.

Note: Use {ProblemID}, not {PID}. ProblemID is the human-readable problem number shown in the Dynatrace UI; PID is a long internal identifier. ITOC360 builds the alert fingerprint from ProblemID, so PID produces alerts that are hard to match back to Dynatrace.

On legacy Dynatrace, State arrives as OPEN or RESOLVED — both are handled automatically.

4. Allowlist the domain (Don't skip this) By default, Dynatrace blocks external outgoing requests. If this step is skipped, the webhook request may fail. Go to Settings > General > External requests. Open the Allowlist tab and click + New host pattern. Add the following host:

api.itoc360.app

5. Deploy Once everything looks good, click Deploy at the top right. It’ll prompt you to save, so just hit Save and deploy to push it live.

6. Test the flow Let's make sure it actually fires. Hit the "Run" button on the canvas to trigger a test execution. Check the logs at the bottom of the Dynatrace screen—you should see a green Success status.

To support automatic resolution in ITOC360, create a second workflow or update the trigger configuration to also send resolved/closed problem events. ITOC360 maps resolved or closed states to RESOLVE events using the same ProblemID.

Troubleshooting

If Dynatrace events do not appear in ITOC360:

• Make sure the ITOC360 webhook URL is copied correctly.

• Verify that the HTTP method is set to POST.

• Confirm that the payload is valid JSON.

• Make sure api.itoc360.app is added to the Dynatrace external request allowlist.

• Check the workflow execution logs in Dynatrace.

• Verify that the workflow trigger matches the selected event categories.

• Confirm that the ITOC360 source token is valid.

If incidents are not resolved automatically:

• Make sure resolved or closed Dynatrace problem events are sent to ITOC360.

• Confirm that the same ProblemID is included in both active and resolved events.

• ITOC360 uses ProblemID as the correlation key to match updates with the original incident.