Adobe Commerce New Relic Integration That Tells You What Broke and Why
The default New Relic connection shows that your store is slow. We extend it to show why: failed checkouts, JavaScript errors on the payment step, bots rotating through thousands of IPs, and the release that started it. Alerts reach the right person in Slack, Microsoft Teams or Google Chat, so problems are fixed before customers notice.
Monitoring built around how your store makes money
An Adobe Commerce New Relic integration connects your store's server, browser and edge traffic to New Relic, so performance, errors and availability are tracked in one place. Evrig extends the standard setup with custom alert policies, deployment tracking, checkout and JavaScript error monitoring, synthetic availability checks, JA4 fingerprint filtering for bots, and alert workflows to Slack, Microsoft Teams and Google Chat.
Most New Relic setups fail in three ways. They alert on the wrong things, so the team learns to ignore them. They miss the failures that cost money, because a failed payment does not look slow. And they cannot explain a spike, because nobody can see which release or which bot caused it. We design for all three: alerts are tied to checkout, payment and cron, every deploy is marked on the charts, and bot traffic is grouped by fingerprint, not by IP.
Custom Alert Policies
Alerts on checkout error rate, payment latency, order drops, stuck cron and invalid indexers, tuned to your traffic so they fire when it matters.
Deployment Tracking
Every release is marked in New Relic with version, commit and author, so you can see if a problem started with a deploy.
Checkout Error Monitoring
Each checkout step reports its own failures, so you see exactly where orders break and why.
- Add session replay to debug checkout issues more effectively.
- Trace errors to their full file paths for easier debugging and faster fixes.
JavaScript Error Monitoring
Browser errors are grouped by page type and release, with the Browser agent installed safely under your Content Security Policy.
Bot and AI-Agent Dashboards
See which crawlers, scrapers and AI agents visit your store, what they cost in server time, and whether they slow pages for shoppers.
Synthetic Availability Checks
Scripted monitors test your key pages from several regions and alert you before customers find a broken page.
JA4 Bot Filtering
Attackers rotating through many IPs are grouped by their TLS fingerprint and blocked at the Fastly edge.
Alert Workflows
Alerts are routed by severity to Slack, Microsoft Teams, Google Chat, email or on-call, so the right person sees them.
Stop finding out about problems from customers
Talk to our Adobe Commerce engineers about your traffic, your checkout and your current New Relic setup.
Alerts, Deployment Tracking, Error Monitoring & Dashboards
Evrig's Adobe Commerce New Relic integration builds on the standard APM and Browser setup with four layers: alert policies tied to revenue, deployment markers on every release, error tracking at each checkout step and in the browser, and dashboards for the traffic that is not a shopper. Everything is configured in your own New Relic account, so your team keeps full access.
Custom Alert Policies
- Conditions on checkout error rate, payment gateway latency, order volume below its normal range for the hour, stuck cron jobs and queue consumers, and invalid indexers.
- Baseline and fixed thresholds: baseline (anomaly) conditions where traffic swings through the day, fixed thresholds where it does not.
- Runbook links: each alert carries a link to the first checks to make, so whoever receives it can act straight away.
- Result: fewer false alarms at night, faster warnings at peak.
Deployment Tracking
- Every release is recorded in New Relic as a change event with version, commit hash and who deployed it.
- Hooked into your pipeline: Adobe Commerce Cloud deploy hooks, GitHub Actions, Bitbucket or GitLab.
- When response time or errors jump, the chart shows the deploy line next to it.
- Result: rollback decisions in minutes, not after a post-mortem.
Checkout Error Monitoring
- Custom events and error reporting at each step: address validation, shipping rates, payment authorisation and order placement.
- Errors are tagged with payment method, error code and store view. Card data and personal data never reach New Relic.
- A funnel shows where orders fail, and an alert fires when one step breaks.
- Result: a broken payment method is found in minutes, not at the end-of-day order count.
JavaScript Error Monitoring
- New Relic Browser monitoring installed so it works under a strict Content Security Policy, with the required domains added to your CSP whitelist.
- Errors grouped by page type, browser and release, including payment iframes, Alpine.js and Magewire components and third-party scripts.
- Works on Hyvä and Luma storefronts.
- Result: front-end failures that never reach the server log are visible and traceable.
Bot and AI-Agent Traffic Dashboards
- Crawler, scraper and AI-agent traffic split out by user agent, fingerprint, path and response code.
- Shows server time each agent costs and whether it slows pages for real shoppers.
- Separates the bots you want (search engines, AI assistants you want to be cited by) from the ones to throttle.
- Result: you decide which agents to keep, limit or block, based on data.
At a Glance
| Capability | Where it runs | Signal | Mode |
|---|---|---|---|
| Custom alerts | New Relic alert policies | APM, cron, queues, indexers, orders | Ongoing |
| Deployment tracking | CI/CD pipeline → New Relic | Change events per release | Every deploy |
| Checkout errors | Adobe Commerce → New Relic APM | Custom events per checkout step | Real time |
| JavaScript errors | Browser agent | Front-end errors by page and release | Real time |
| Bot and AI-agent dashboard | New Relic dashboards | User agent, fingerprint, path | Ongoing |
| Synthetic checks | New Relic Synthetics | Key page availability and content | Scheduled |
| JA4 bot filtering | Fastly edge → New Relic Logs | TLS fingerprint across IPs | Real time |
| Alert workflows | New Relic workflows | Slack, Teams, Google Chat, email | On alert |
Synthetic Monitoring & JA4 Bot Filtering
Know your store is up, and stop attackers that IP blocking cannot
Uptime checks that only look for a 200 response miss broken pages, and IP blocklists miss bots that rotate addresses. We cover both.
Synthetic availability checks
- Scripted monitors run from several regions on your key pages: home, a category, a product, cart and checkout entry.
- Each check confirms the page loads, returns the right status and shows the expected content, not just a 200 from a maintenance or error page.
- Response time limits per page, so a slow checkout alerts as well as a down one.
JA4 fingerprint filtering for bots
- Credential stuffing, card testing and scraping bots often rotate through thousands of IP addresses, so IP blocking fails.
- JA4 is a fingerprint of how a client opens its TLS connection. It usually stays the same when the IP changes.
- We capture the JA4 value at the Fastly edge, send it to New Relic Logs, and group requests by fingerprint across IPs.
- When one fingerprint hammers login, cart or checkout, an alert fires and the fingerprint is blocked or rate-limited at the edge, before it reaches Adobe Commerce.
Result: outages are caught before customers or ad platforms notice, and attacks are stopped at the edge instead of loading your servers.
Alert Workflows: Slack, Microsoft Teams & Google Chat
Send every alert to the person who can fix it
Most New Relic setups email one shared inbox, so alerts get missed or ignored. We set up New Relic workflows that route each alert by severity, service and time of day.
Slack and Microsoft Teams
Connected as native New Relic destinations, with channels per team or severity.
Google Chat
Connected through a webhook that posts a formatted card to your Google Chat space, with the same detail as the other channels.
Email and on-call
For critical alerts that need someone outside working hours.
Routing rules
For example, critical checkout alerts go to on-call, performance warnings to the dev team, bot and JA4 alerts to security.
Useful alert content
What broke, when it started, the nearest deployment marker and a runbook link, so nobody has to open New Relic first to understand the alert.
Result: alerts reach the right people in the tools they already use, and nothing waits in an inbox.
Evrig + Adobe Commerce + New Relic
As an Adobe Solution Partner (Silver) and Hyvä Gold Partner with certified Adobe Commerce developers, we know where Adobe Commerce stores actually fail: checkout, payment calls, cron, queues, indexers and third-party scripts. We instrument those parts directly, so New Relic reports on your business, not just your servers.
Built to Work Across Adobe Commerce Hosting Setups
Adobe Commerce Cloud
New Relic APM and Fastly come with the platform. We build on that setup with custom instrumentation, Browser monitoring, synthetics, JA4 logging at the Fastly edge and alert workflows.
Self-hosted Adobe Commerce, Magento Open Source and Mage-OS
We install and configure the New Relic PHP agent, Browser monitoring and infrastructure monitoring, then add the same customisations. JA4 filtering depends on your CDN or edge layer supporting it.
Result: the same monitoring approach on any setup, and it moves with you if you change hosting.
End-to-End New Relic Integration Services
Consult & Discover
Review of your New Relic account, agents, alert policies, dashboards, CSP and Fastly configuration; traffic and checkout analysis; a list of blind spots and a monitoring plan.
Build & Connect
Custom alert policies, deployment markers in your pipeline, checkout and JavaScript error instrumentation, bot and AI-agent dashboards, synthetic monitors, JA4 logging and alert workflows to Slack, Teams and Google Chat, tested on staging first.
Go Live & Tune
Production rollout, then a tuning period to cut noisy alerts and set baselines on real traffic.
Managed Support & Growth
Alert and dashboard reviews, incident triage, new monitors for new features or integrations, and upgrade checks for Adobe Commerce and the New Relic agents.
How We Deliver
Start from a tested monitoring setup instead of a blank New Relic account.
Faster Setup
Alert policies, dashboards and workflows we have already built for Adobe Commerce, adapted to your store
Ready-Made Checkout and JS Monitoring
Instrumentation for each checkout step and CSP-safe Browser monitoring
Security Built In
Synthetic checks and JA4 bot filtering configured as part of the setup
Your Channels
Alerts routed to Slack, Microsoft Teams, Google Chat or email from day one
Our Process and Timeline
01
Audit
02
Plan
03
Build on staging
04
Go-live
05
Tune
06
Support
17 Years of Magento Excellence, Watching Every Checkout
17+
Years in the Magento ecosystem
120+
Stores launched
35+
Adobe Commerce certifications
90+
Average Core Web Vitals score
18+
Countries served
- Adobe Subject Matter Expert on the team
- Adobe Commerce Official Trainers
- Magento Core Code Contributor
- Meet Magento India organizer
- Magento Meetup organizer
- Multiple Awards Winner
- Adobe Solution Partner Silver
- Hyvä Gold Partner
Ready to get more out of New Relic on Adobe Commerce?
What happens next: We reply within 1 day with a technical contact and next steps.
Quick Answers to Your New Relic Integration Queries
Connect ExpertYour Customers Notice Problems First. Should They?
A failed checkout or a bot attack costs more than the monitoring that catches it.
