Compared to API Monitoring Tools

These solutions are based on predefined scripts that run periodically to verify if your API responds as expected. This is useful, but visibility is limited only to predefined behaviors.

Vendors like RunScope and Uptrends run scripts from all around the globe and alert customers if APIs suddenly become unreachable. This is most helpful for detecting major outages or connectivity problems from specific geographic locations. But this provides little insight for understanding and supporting real customers.

With Resurface, complete requests and responses to your APIs are recorded, just by instrumenting your microservices. This gives visibility into how real customers use your APIs, without requiring any scripts to define and maintain.

What is Monitored?
Microservices providing APIs
Microservices providing APIs
Available Data?
Count of successful script executions, Count of failed script executions
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 key predefined transactions working properly? From around the globe? Around the clock?
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?
Visibility limited to predefined scripts, No real customer-specific activities, Scripts are manually defined and maintained
No external monitoring