Compared to APM Tools

Resurface is complementary to most APM tools -- we aren't a replacement for New Relic or DataDog. If you're a fan of those tools, you'll appreciate the extra visibility that Resurface provides into how your APIs are being used.

APM tools are all about tracking and reporting on performance, focusing on response times. These tools detect when response times exceed expectations and help devops teams understand what components are responsible for the slowdown. All of this is hugely valuable, but is based on anonymous performance data.

Resurface doesn't focus on performance reporting, but on logging actual requests and responses from your API. This allows every attempted user action to be recorded, and when necessary, retried in the future. APM tools can detect outages and failures, but Resurface goes further by allowing users affected by a failure to be identified, and their transactions to be recovered.

What is Monitored?
Microservices providing APIs and websites
Microservices providing APIs and websites
Available Data?
Response time breakdowns across application components, Optionally include end-user monitoring with JavaScript instrumentation
Complete API requests & responses -- including all request parameters, request & response headers, request & response payloads (in JSON, HTML and other formats), plus request URL and response code. Data can be filtered or sampled with logging rules.
Questions Answered?
Are my websites and APIs reachable by users? Are my websites and APIs performing acceptably? When performance is bad, what component is causing the slowdown? Is it the application, the database, or the network that is slow? When did the slowdown begin? Is there a recent code change that may have caused the problem? Which technical team should investigate the slowdown?
Are customers using my APIs as expected? How can I discover API calls for unexpected or harmful conditions? How do I get usage data for modeling and predicting customer behavior? How can I re-calibrate my models as customer behaviors change over time? What specific customers and API calls in the past were affected by a defect? Which customers have failed API calls that could be recovered? Which customers are dependent on legacy or deprecated API calls?
Limitations?
Built to handle anonymous performance data, Focus on looking deep inside the application and its components, Rarely includes customer-specific fields, Often relies on JavaScript instrumentation (which actually reduces performance!), Often requires third-party data transfer, Data integrations often subject to caps or usage limits
No performance metrics or response time breakdowns, No visibility into client devices, No visual reports included (but we work with most reporting & dashboarding tools)