Rearview vs New Relic Change Tracking
New Relic Change Tracking is genuinely good and it is included free with the platform, which is the strongest argument against paying for anything else. It is also anchored to entities you monitor and aimed at engineers. Here is exactly where that boundary sits, and when free is the right answer.
This is the hardest comparison on our site to write honestly, because New Relic Change Tracking is good and it is included with the platform you may already pay for. “We already have this, and it costs nothing extra” is the strongest argument against buying anything else, and it is often correct.
What New Relic Change Tracking does well
- Marks changes directly on your telemetry. A deploy or a config change appears as a marker on the chart where the metric moved, which is the fastest possible way to connect the two when the change is one it knows about.
- Correlates changes to what broke. Error rates, latency, apdex, all in the same tool with the change overlaid.
- Free with the platform. No separate line item, no new vendor, no new procurement conversation. That is a genuine advantage and we are not going to pretend otherwise.
Where the boundary sits
New Relic is an observability platform, and its change tracking is anchored to entities it monitors. A change is meaningful there because it attaches to a service, a host, a browser app. That anchoring is what makes the chart overlay work, and it is also the limit.
| New Relic Change Tracking | Rearview | |
|---|---|---|
| Deploys and code | ✅ native | ✅ native |
| Infrastructure and config | ✅ native | ⚠️ via the generic API |
| Change overlaid on your telemetry | ✅ the core strength | ❌ not attempted |
| A price edited in Stripe, a CMS republish, an app that self-updated | ❌ no entity to anchor to | ✅ the core data model |
| Who it is built for | Engineers, on a full platform seat | Whoever gets asked what changed |
| Cost | Included with the platform | Flat, standalone |
The fourth row is the whole difference. A price change in Stripe is not an entity New Relic monitors, so there is nothing for it to attach to. That is not a gap in their product, it is what their product is: change tracking exists there to explain telemetry, and a Stripe price has no telemetry.
Choose New Relic if…
- You already run New Relic, and the changes you care about are deploys and infrastructure.
- The question is usually “which deploy caused this latency spike?”
- The people asking already have seats and know the tool.
- You want zero additional cost, which is a completely legitimate reason.
Rearview is the better fit if…
- The changes that hurt you have no telemetry: a price, a coupon, a republished page, a shipping rule, an app that updated itself overnight.
- The person asking does not have an engineering seat and is not going to get one.
- The question is “what changed yesterday?” rather than “what caused this chart to move?”
Running both is normal
These answer different questions and we would not argue with a team that keeps New Relic for everything with telemetry and wants a plain-English record of everything without it. If your changes all live in code and infrastructure, New Relic already covers you and you should stop reading here.
Related reading: compared to Datadog Change Tracking, compared to Sleuth, and when somebody changed something and nobody wrote it down.
Never wonder “what changed?” again.
Rearviewputs every production change on one timeline, so anyone on the team can ask. Join the waitlist and we'll let you know when it's ready.
Get early access →