I love what the Go team is shipping on this front, but I'd love to hear from folks who actively use these features in production.
Between OTEL, Datadog, Google Cloud, and umpteen other distributed tracing offerings, I don't quite understand how this fits in. I'd love there to be a drop-in approach to using this in my existing Google Cloud Run application, but as far as I understand I'd need to figure out some way to collect the traces, save them somewhere (ostensibly GCS?) and then download them when I need to diagnose an issue.
Seems like a lot of work, and just another thing to maintain.
thomascountz•4mo ago
I feel the same. I can't quite tell where this fits in, in a production context.
I suppose the value proposition might be that it's all built-in, meaning there's no events to publish over the network nor any OTEL collectors to deploy. This is just a file on the host that you can read and use go's built-in trace tool to examine. In that way, I guess it's simply like any log file, but enriched with trace data and configured to only contain only the traces you're interested in.
theli0nheart•4mo ago
Between OTEL, Datadog, Google Cloud, and umpteen other distributed tracing offerings, I don't quite understand how this fits in. I'd love there to be a drop-in approach to using this in my existing Google Cloud Run application, but as far as I understand I'd need to figure out some way to collect the traces, save them somewhere (ostensibly GCS?) and then download them when I need to diagnose an issue.
Seems like a lot of work, and just another thing to maintain.
thomascountz•4mo ago
I suppose the value proposition might be that it's all built-in, meaning there's no events to publish over the network nor any OTEL collectors to deploy. This is just a file on the host that you can read and use go's built-in trace tool to examine. In that way, I guess it's simply like any log file, but enriched with trace data and configured to only contain only the traces you're interested in.