This is super sweet.<p>It would be great to tie this into a release pipeline, where the release process is actively keeping an eye on failure rates of that service, so that bad deploys could be halted or rolled back automatically.<p>I was thinking this could work really well when using production integration tests. A percentage of that traffic can be dynamically routed to the newly running services, allowing the release pipeline to ensure the service is functioning correctly before routing any real users.
Oh nice, it's cool to get access to dependency info without having to implement a full distributed tracing mechanism that is invasive to the service components.<p>Breaking down service success rate by inbound dependency is great for debugging many typical fault conditions.