In short, we can use existing logs, traces and metrics to answer questions such as:
- Where is this function called from? Is it even used?
- Is this a problematic area of the code? Where are my bottlenecks?
- What type of errors does this code raise in runtime? What issues are escalating? Which are affecting the end user?
Digma ingests OpenTracing data and tries to show useful things about your code in context, I guess:
Seems pretty neat; found via this article "# Improving Code Design With OpenTelemetry — A Practical Guide" which walks you through setting up Jaeger, Digma and OpenTelemetry traces in a sample app.