BMC Remedy and New Relic, connected in real time
Give your service desk BMC Remedy context. ZigiOps turns BMC Remedy Incidents into New Relic Applications in real time — status, priority and notes flow both ways, no scripts required.
BMC Remedy 
New Relic BMC Remedy catches issues first, but New Relic is where the team tracks and resolves them. Without a link between the two, someone has to manually turn every meaningful Incident into an Application — or it falls through the cracks.
ZigiOps turns every BMC Remedy Incident into a New Relic Application automatically, and keeps status, priority and notes synchronized in both directions for as long as the issue is open.
How the BMC Remedy ↔ New Relic 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.
BMC Remedy 
New Relic Per field, not per record — if only the priority changed on one side, only that field is resolved, not the whole ticket.
Lock specific fields (e.g. Priority) to always defer to one system, regardless of which side changed last.
Route simultaneous conflicting edits to a review queue instead of silently picking a winner, when that's the safer default.
BMC Remedy connector New Relic connector See BMC Remedy ↔ New Relic sync live
Book a demo and we'll connect your BMC Remedy and New Relic instances in real time.