Compared to Server Logging

Resurface is complementary to most server logging tools -- we aren't a replacement for Loggly or Splunk. We are big fans of these tools, but they have little in common with Resurface.

Server logging tools are all about system health and server-level events. These discourage inclusion of customer-specific fields, and lack built-in protections for personally identifiable information. By comparison, Resurface focuses on customer-specific fields and PII.

What is Monitored?
Servers running microservices
Microservices providing APIs
Available Data?
Message string with timestamp & severity
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?
At what time did a specific event occur on my server? What was the state of my system at that time? What other server events occurred around the same time? How often did a specific server event occur in the past?
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?
Intentional logging of user PII is often discouraged by these tools, Protections for user PII may be not present by default, Query languages are limited to text matching and time correlation, Often requires third-party data transfer
No visibility into server logs or system health