> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # New Relic on Vortex IQ > Monitor New Relic health, cost and reliability signals, and catch incidents and runaway spend early. Monitor New Relic health, cost and reliability signals, and catch incidents and runaway spend early. No changes are made without the configured approval policy. Read-only operations do not modify the connected system; schedules, access scopes, API usage and data handling remain governed by Vortex IQ controls. [Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) ยท [How connecting works](/integrations/connector-catalogue) | **16** | **14** | **Build your own** | **Ready to build yours** | **1** | | ------------------- | ---------------- | ------------------ | ------------------------ | -------------- | | performance signals | automated checks | automated fixes | workflows | API operations | ## Monitor performance 16 performance signals. Signals with an alert band can raise Nerve Centre alerts; every signal supports a merchant-configured watcher. | Signal | Outcome | Alert behaviour | What it tracks | | ------------------------ | ----------------------- | --------------- | ----------------------------------------------------------------- | | **Error Rate** | Control risk and change | Watch only | Percentage of transactions resulting in an error. | | **Apdex Score** | Customer experience | Watch only | Application performance index score (0-1). Closer to 1 is better. | | **Apdex Trend** | Customer experience | Watch only | Apdex score trend over the selected period. | | **Avg AJAX Response** | Customer experience | Watch only | Average AJAX request response time in milliseconds. | | **Avg DOM Processing** | Customer experience | Watch only | Average DOM processing duration in milliseconds. | | **Avg Page Load Time** | Customer experience | Watch only | Average browser page load time in milliseconds. | | **Avg Response Time** | Control risk and change | Watch only | Average transaction response time in milliseconds. | | **Error Rate Trend** | Customer experience | Watch only | Error rate trend over the selected period. | | **HTTP Status Codes** | Control risk and change | Watch only | Distribution of HTTP response status codes. | | **JS Error Count** | Customer experience | Watch only | Total number of JavaScript errors captured by the browser agent. | | **Response Time Trend** | Customer experience | Watch only | Response time trend over the selected period. | | **Slowest Transactions** | Control risk and change | Watch only | Slowest transactions ranked by average duration. | | **Throughput** | Run operations | Watch only | Average requests per minute processed by the application. | | **Throughput Trend** | Customer experience | Watch only | Throughput trend over the selected period. | | **Top Error Classes** | Control risk and change | Watch only | Most frequent error classes in the selected period. | | **Total Errors** | Control risk and change | Watch only | Total number of transaction errors. | ## Audit risks and opportunities A fix status appears only where the action, inputs, approval, verification and recovery controls are mapped. Candidate remediations are never executable. | Check | Severity | Outcome | Why it matters | Fix status | | ------------------------------------------- | -------- | ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | | **Error rate above 2%** | critical | Customer experience | More than 1 in 50 requests is failing right now. Depending on which endpoints are affected, this can mean pages failing to load, checkout steps failing silently, or background jobs dropping | Report only | | **Apdex score below 0.85** | high | Customer experience | Apdex below 0.85 means a meaningful share of visits are experiencing the site as slow or frustrating rather than satisfying, using the same industry-standard scoring that tells you when perf | Report only | | **Avg response time above 1500ms** | medium | Protect revenue | Average response time over 1.5 seconds is well past the point where shoppers notice the delay, and slow response times are a documented driver of higher bounce and lower conversion; this is | Report only | | **Slow AJAX Requests** | medium | Customer experience | Slow AJAX calls make an otherwise-loaded page feel broken, spinners where content should be; the offending endpoints are listed. | Report only | | **Throughput dropped > 30% week-over-week** | medium | Run operations | Requests handled dropped more than 30% versus the prior week. This can mean genuinely lower traffic (worth knowing on its own) or it can mean the application is silently failing to serve req | Report only | | **Top Error Classes** | medium | Control risk and change | The top error classes account for most failures; fixing the first few usually collapses the whole error rate. | Report only | | **HTTP 5xx Errors** | low | Control risk and change | HTTP 5xx responses are the server refusing service; even a low rate means some customers hit a dead end at full price. | Report only | | **High Error Rate** | low | Control risk and change | An elevated error rate means requests are failing for real users right now; the error classes behind it name the code paths to fix. | Report only | | **High JavaScript Error Count** | low | Customer experience | JavaScript errors break interactions silently: buttons that do nothing, forms that never submit. Each error class comes with the page and stack to fix it. | Report only | | **Low Apdex Score** | low | Customer experience | A falling Apdex means real users find the application slower than the tolerable threshold; it is the single-number summary of experienced performance. | Report only | | **Slow Page Load** | low | Grow revenue | Slow page loads cost conversions directly; browser-side timing shows what users actually experienced rather than what the server sent. | Report only | | **Slow Response Time** | low | Control risk and change | Slow server responses cap how fast any page can feel, no matter how optimised the frontend is; the slowest transactions name the culprits. | Report only | | **Slow Transactions** | low | Control risk and change | Slow server responses cap how fast any page can feel, no matter how optimised the frontend is; the slowest transactions name the culprits. | Report only | | **Throughput** | info | Control risk and change | Informational: the technologies detected on the storefront, used to tailor the other checks to the actual stack. | Report only | ### Build your own automated fixes 14 checks report findings on New Relic today. Turn any finding into an automated fix with a Vortex IQ workflow: **13,885 read and write operations across 229 connectors** are available as building blocks, with approval, verification and rollback on every change. ## Automate approved work Vortex IQ is integrated with **0 read** and **1 write** operations across graphqls on New Relic. Combine them with anything from the **13,885 operations across 229 connectors** to automate the work in your own words. Changes follow the merchant's configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution. Read-only operations do not modify the connected system. [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=newrelic) | Resource | Read operations | Write operations | | -------- | --------------- | ---------------- | | graphqls | 0 | 1 | Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected. ### Ready to build your first New Relic workflow Pick a trigger, add the operations above as steps, and every step that changes data pauses for your approval. Monitoring and audits are live now and can start any workflow you build. *** *Generated from the connector capability graph. Counts reflect the servable registry after alias normalisation and de-duplication, and refresh automatically when the registry changes.*