Published Sep 26, 2026
Academic and technical literature identifies challenges for serverless observability such as inconsistent granularity, correlation difficulty, and statelessness, which can limit automated root-cause analysis across any vendor solution.
This review did not compile a complete product roadmap. Vendor public “what’s new” pages indicate ongoing evolution and changes related to APM and serverless convergence.
From community discussions and general market sentiment:
Because serverless monitoring is typically reviewed as part of the overall New Relic platform experience, most review sites do not isolate serverless as a separate product category. The summaries below reflect broader platform feedback that is relevant to serverless buyers.
Across review platforms and vendor materials, users commonly report the following advantages:
New Relic publishes whitepapers and vendor-authored collateral that describe platform positioning and reported outcomes. Many performance and ROI claims in vendor materials are not independently audited in those documents.
Example: vendor engineering playbooks and whitepapers can be useful for understanding internal practices, but they do not constitute independent ROI validation.
Common in software, fintech, e-commerce, and other sectors operating distributed systems. This review did not compile a serverless-specific customer list by industry.
Get a comprehensive analysis of New Relic Serverless Monitoring including market position, competitive landscape, adoption trends, and peer benchmarks.
Download full report →Pricing and billing frustration (negative):
General platform preference (positive):
Serverless instrumentation reality (mixed/neutral):
Reported improvement metrics in observability case studies often depend on baseline maturity, sampling choices, instrumentation coverage, and incident definitions and measurement windows. Buyers should request the following when evaluating vendor case studies:
New Relic Serverless Monitoring is part of New Relic’s broader observability platform and focuses on monitoring serverless workloads—primarily AWS Lambda—by collecting telemetry (metrics, traces, logs). The product provides visibility into function performance (latency, errors, cold starts), dependency behavior, and end-to-end transaction impact. New Relic describes the capability as observability that correlates serverless function behavior with upstream and downstream services and infrastructure.
A recent packaging and architecture direction is New Relic’s APM + Serverless convergence, where the serverless monitoring experience and billing are increasingly tied to the APM entity model. This change can simplify having a single observability model for teams, and it can also affect how serverless is priced and managed compared with a standalone serverless product.