Ted Young

@jvshahid A couple answers 1. I imagine that events would be for the standard ifrit lifecycle: `invoked`, `ready`, `signaled`. and `exited`. The reason for this feature is that logging/metrics code...

Sorry @jvshahid, just realized you were talking about exit codes, not signals. Doing a quick survey of diego `main` files, I noticed they occasionally have little squiggles in there which...

Since I doubt there is appetite for improvement at this point, I'm inclined to let sleeping bears lie. But I'm welcome to a v2 if CF peeps want to work...

How is this expected to work regarding feature development? Is the Tokio community willing to join the OTel spec going forwards?

So, I would like to talk to the Rust maintainers, as I do not speak for them. But as a GC member and co-founder of OpenTelemetry, I have opinions. :)...

I have two problems that I would like to see resolved. ## Problem one: remove confusion about what a Collector is The first problem is basic confusion about "what a...

@yurishkuro number one is definitely a problem. We are actively addressing an example of it right now. It is related to number two, but it causes other fundamental confusions. I...

Thanks @jpkrohling that's a great layout. My only suggestion is that I think Collector Build and Collector Distro can be combined. Anything that can be reproduced by the builder can...

@yurishkuro I have three concrete issues that can be resolved with definitions. The first is support. I would like us to only handle technical support requests for the code that...

Had a discussion about the `summary` attribute today in the Event SIG. It's a very useful field, Alex's example above (https://github.com/open-telemetry/semantic-conventions/pull/1074#issuecomment-2155453445) really shows that. One question is whether the content...