Josh Suereth
Josh Suereth
Tested this with optimised docker image build and it drops to 1.5s for the check
I updated to have @lquerel's collision detection as well, on debug build this is: ``` > Total execution time: 4.745763013s ``` Optimised, ~1s, so major improvements.
I think this may be related to https://github.com/open-telemetry/semantic-conventions/pull/903/ cc @trisch-me
If no further comments/updates happen before monday, I'd like to talk about this in the general semconv meeting. From what I can tell - you may need something *stronger* then...
> If the answer is "not really": we can use semconv, but we may want to full up specify the attributes and force semconv to have them defined [like these...
I'd like to add consideration for the *inverse* relationship for embed. E.g. Instead of embed living on the consumer, we do something like: ```yaml groups: id: registry.types.geo type: embeddable_group brief:...
> Too broad definition of attribute groups This is why I was suggesting a new group type for embeddable things. I think this gives us a good set of properties:...
Adding to some comments here, due to a conflux of PRs and discussions disparate. > why do you think it makes codegen complicated? Because when you "reference" individuals, it's hard...
resources now have name, which denote a "TYPE" identity, awkwardly.
We should document this and maintain it in weaver and then link to that note from semconv codegen docs.