Hi all, I'd like some feedback on a Go observability tool (yes another one..) I'm thinking about building. It would differ from existing tools because it automatically instruments your Go service with network call tracking, DB queries, call-stack traces, logs-per-request. You wouldn't have to make any changes to your code or use `ctx, span := tracer.Start()` and such. It would use eBPF to get a full call stack, including function args and return values.The idea here is to make it easier to debug production errors when things go wrong. I've done a very quick mock-up of what the dashboard would look like here <https://trayce.dev/gotrayce.html>. One caveat is that the full call stack would only be traced for status 500 responses by default (this would be configurable though) because there is a slight performance degradation by tracing this.Let me know what you think, thanks!
-- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/golang-nuts/9df070e3-96fd-4998-96d2-725f3bda2674n%40googlegroups.com.
