what I like about google trace is how easy it is to track the time spent in a request. The timeline view makes it very clear which service or step is slow, since i have used google trace in the past projects the best is integration is smooth i dont have to configure much thing manually. I was debugging a slow API once, and instead of checking logs everywhere, I could clearly see that most of the delay was coming from a DB call
I didnt use all features but for normal debugging and latency it works well and useful too Análise coletada por e hospedada no G2.com.
One thing i found which can be improved is the UI, it works but not with complex traces, I tried filtering down into specific spans but it is hard to trace. Also compared to some other tools, level of details it gives is less, unlike DataDog i have used personally it is better in those aspects
because when i used google trace for deeper logs i have to rely on other tool.
pricing is also a concern if we have high traffic cost increases much alternate option to this in case of pricing is jaegar (it also has concerns as infra cost is much in this although it is free).
support-wise, I didn’t interact much directly, but finding clear answers for specific issues in documentation wasn’t always easy.
and AI limitations are already there..as it just show raw trace data not give proper recommendations...i have to manually analyze the problem
so it can be more intelligent Análise coletada por e hospedada no G2.com.
