Welcome to WTF Dial Discussions

[benbjohnson]

Welcome! 👋

WTF Dial is an example project for how to structure real-world Go applications. You can find companion blog posts that explain the architecture and design at Go Beyond. Instead of using a traditional comments system, I wanted to try GitHub Discussions instead.

I'd love to hear what you're interested to learn and what you're building yourself. Please comment below and introduce yourself to the community.

[komuw]

Hi,
I'm Komu. The last few months I built https://github.com/komuw/kama which prints out a types documentation.

One question I had while perusing through the wtf code, there's hardly any logging in the code; is that by design?
I noticed that the code has metrics via prometheus but no logging.

[flowchartsman]

As far as profiling and metrics, has anyone experimented with continuous profiling/tracing (e.g. profefe)? It seems like a good way to bridge the gap between metrics and manual profiling.

[benbjohnson]

I haven't used profefe myself but it sounds awesome.

[peterbourgon]

I personally don't understand the value proposition for continuous profiling, but maybe I just haven't seen the light?

[benbjohnson]

I can the value in situations where you have infrequent & difficult to reproduce performance issues. It'd be great to go back retroactively and see profiles from a point-in-time.

[A2-NieR]

Really want to make it work for my project, but I guess I bit of more than I can chew right now trying to use a different DB that is completely new to me and at the same time trying to introduce Gin with this while still learning the ins & outs of the language 😅