AppDynamics and BMC Remedy, always in sync
Connect application performance to your ITSM system of record. ZigiOps turns AppDynamics health rule violations into BMC Remedy incidents in real time — severity, work notes and resolution flow both ways, no scripts required.
AppDynamics 
BMC Remedy Performance degradations surface first in AppDynamics, but BMC Remedy is where the enterprise tracks and reports on incidents. Without a link between the two, someone has to manually re-key every meaningful alert into Remedy — or major incidents go untracked.
ZigiOps links each AppDynamics health rule violation to a BMC Remedy incident and keeps severity, status and work notes synchronized in real time, so Remedy stays the single source of truth without manual data entry.
How the AppDynamics ↔ BMC Remedy 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.
AppDynamics 
BMC Remedy Every field that matters, mapped both ways
Map AppDynamics entities to BMC Remedy entities down to the individual field, without writing a script.
More control over how AppDynamics ↔ BMC Remedy syncs
Updates flow the moment they happen — no polling delays, no scheduled batch jobs.
Scope every sync with filters on severity, application, CI 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 performance alert to tracked incident
AppDynamics detects the degradation; Remedy is where the enterprise records and reports on it. ZigiOps keeps the two in step end to end.
A monitored application or tier breaches its threshold, raising an alert with severity and topology data.
A matching incident appears instantly, mapped field-for-field and linked to the affected CMDB CI.
Status and work notes sync back to AppDynamics as the incident is investigated.
Resolving the incident in Remedy closes it in AppDynamics too, with a full audit trail.
AppDynamics ↔ BMC Remedy FAQ
Is the AppDynamics–BMC Remedy sync bidirectional?
Yes. Incidents stay aligned in both directions in real time, with conflict-resolution logic keeping both systems authoritative.
What fields map between the two?
Alert ↔ incident, severity ↔ priority, status, and notes ↔ work info notes — all in both directions with full fidelity.
Does the integration update the CMDB?
Yes. AppDynamics application and tier context can map to the related CMDB CI on the Remedy incident.
Can I limit the sync to specific severities?
Yes. Conditional triggers let you scope the sync by severity, application or health rule, so only the alerts that matter reach Remedy.
Can I connect multiple AppDynamics controllers to one Remedy instance?
Yes. ZigiOps supports unlimited connections, each with its own field mapping and filter rules.
Do I need to script anything in AppDynamics or Remedy?
No. The entire integration is configured no-code in ZigiOps — no AppDynamics actions or Remedy workflows to build or maintain.
See AppDynamics ↔ BMC Remedy sync live
Book a demo and we'll connect your AppDynamics and BMC Remedy instances in real time.