You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to golang-nuts
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. 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!