The QA team lets you know there’s an issue with a new feature on the website, that you just finished working on. Something in the app is not working as it should.
This action involves not only your microservice, but also a staging microservice, which makes it harder to debug.
Debugging microservices is difficult – you can spend hours going through logs and try to reproduce issues. You switch between different apps and lose sight of things.
To debug a staging microservice you, or the developer in charge, will need to somehow create logs for it and deploy to staging.
Aspecto provides you with a clear visualization map and tracing that spotlights where your problem is so you can find the source faster and easier – all in one web app, without writing new logs.
Step 1: Reproduce the request locally
In your local environment send the same request that failed in QA.
Step 2: Go to Live in Aspecto to see the flow created by the action just now
In “Live”, find the flow that was created by your action. You can find it either manually or by using the entry point in the search bar.
Step 3: View the flow architecture and errors
In the flow page you can see what was the failed action. It is shown both on the architecture graph and in the Flow Overview.
Step 4: Select the failed component to see more details and identify the issue
In the failed component you can see all the details of the action: request, response and the full code.
After localizing the issue with Aspecto – the road to the solution is shorter than ever.
Conclusion & Solution
In a situation of multiple microservices, where you’re only responsible for one – Aspecto helps you to debug any issue quickly and efficienlty by localizing it without leaving the platform. No need to read logs and write new ones!