Dy ServiceNow and Dynatrace, always in sync
Turn detected anomalies into actionable work. ZigiOps syncs Dynatrace problems with ServiceNow incidents in real time — severity, impact and root cause flow both ways, no scripts required.
ServiceNow Dynatrace detects the anomaly first; the service desk works from ServiceNow. Without a link between them, root-cause context stays in Dynatrace while the incident record lacks the detail teams need to act fast.
ZigiOps links each Dynatrace problem to its ServiceNow incident and keeps severity, impact and root-cause detail synchronized in real time — no scripts, no manual updates.
How the ServiceNow ↔ Dynatrace mapping works inside ZigiOps
A look at the visual field-mapping canvas ZigiOps engineers use to configure this pair — point, click, connect. No scripts, no pipelines.
ServiceNow Every field that matters, mapped both ways
Map ServiceNow entities to Dynatrace entities down to the individual field, without writing a script.
More control over how ServiceNow ↔ Dynatrace syncs
Updates flow the moment they happen — no polling delays, no scheduled batch jobs.
Scope every sync with filters on severity, impact level or any custom field.
Built-in logic decides which update wins and logs every decision for full traceability.
Sync resumes on its own after downtime or network interruptions — nothing to restart by hand.
Validate field mappings and rules against real data before the integration goes live.
See sync status and catch failures early, without digging through logs.
When a sync fails, ZigiOps surfaces the likely cause and a suggested fix — no log-diving required.
From detected anomaly to resolved incident
Dynatrace spots the anomaly and its root cause; the service desk works it to resolution. ZigiOps keeps the two in lockstep.
Dynatrace's AI engine identifies a problem and its likely root cause.
A matching ServiceNow incident appears instantly, with severity, impact and root-cause detail attached.
Status and work notes sync back to Dynatrace as the team investigates and resolves.
When the problem resolves in Dynatrace, the incident closes automatically with a full audit trail.
ServiceNow ↔ Dynatrace FAQ
Is the ServiceNow–Dynatrace sync bidirectional?
Yes. Problems and incidents stay aligned in both directions in real time, with conflict-resolution logic keeping both systems authoritative.
What fields map between the two?
Problem ↔ incident, severity ↔ priority, impact, and root cause ↔ work notes — all in both directions with full fidelity.
Does the incident auto-close when the problem resolves?
Yes, if configured that way. When Dynatrace marks a problem resolved, ZigiOps can automatically update or close the linked incident.
Can I map specific Dynatrace entities to specific CIs?
Yes. Entity context from Dynatrace can be mapped to configuration items in your ServiceNow CMDB for precise incident routing.
Can I limit the sync to specific severities?
Yes. Conditional triggers let you scope the sync by severity level, impact or any other field, so only the problems that matter reach ServiceNow.
Do I need to script anything in ServiceNow or Dynatrace?
No. The entire integration is configured no-code in ZigiOps — no business rules or custom Dynatrace webhooks to build or maintain.
See ServiceNow ↔ Dynatrace sync live
Book a demo and we'll connect your ServiceNow and Dynatrace instances in real time.