What developer pain points observability tools could solve

One of the difficulties in debugging is to either fetched the logs (which is a long process involving Devops) or asking the user or QA to share the steps to reproduce the bug. Or the developers themselves use the breakpoints to analyze what caused the code to break.

I am working on an observability tool for developers. Idea behind it is:

• to uncover the data/object flows
• identify the anomalies in the data as it moves from one class/method to another(this will observe data for sometime to find all the possible combinations, it will raise an alert if there would be difference in data).
• uncovering which method takes the most time etc.
• Flow visualization can also be used as a form of documentation of ever changing code base and understanding the undocumented part of the code.

Moreover, I also plan to add a functionality of "indexing" the codebase allowing developers to search the logic/flows of their choice – for eg how the app behaves for user A (lets say a stripe) as compared to user B(appstore user) and output should be complete flow end to end.

Before working more on this, i wanted to get an earliest feedback to validate the top pain points developers have around this issue and what other tools are offering.