MartinDotNet
MartinDotNet
Is this still the case @pellared ?
I don't think we're going to do anything with this @alanwest @CodeBlanch ? if not, we should close this as not planned rather than keeping it open.
So this is currently an Experimental spec for those stats. So it's a little more interesting of a requirement. Ultimately, those should come from runtime, but I have no idea...
I'd say this is a pretty sane addition to the API and adds some consistency. Would you be willing to do a PR for it? What are your thoughts @CodeBlanch...
I think if someone is willing to put in the work to do it properly I think that's fine and it should be accepted, but likely not something anyone can...
My suggestion was something thar was more holistic as a change, as was suggested. I think, if things are being misunderstood as your suggestion, the best option maybe to submit...
There's not a huge amount of information to go on there, but I suspect that the ParentIds are from the HTTP outbound span (HTTP Client), not the inbound AspNet core...
This is happening as part of the OpenTelemetry Collector helm chart too. A core part of the model is that you can disable/remove certain receivers which are in the default...
Why would YAML be the default and not JSON? Are there examples of other exporters doing YAML as an output? I can understand potentially having YAML as an option, but...
I was asking for examples outside of Microsoft, and specifically within the OTel ecosystem. I'm not sure any of the other SDKs' console exporters have YAML as the default, so...