Migration to Schema v2

[joaopgrassi]

This is a tracking issue for the work involving migrating semconv to Weaver schema v2.

In general we need to:

• Migrate to new definition syntax
• Migrate scripts, templates, policies
  • Consider also moving them to weaver packages

Plan

• Start by migrating output and makefile targets
  1. Policies Switch policies to v2 #3849 - @lmolkova
  2. Update yaml and make it v2-migration friendly, keep v1 output
     • migrate groups like server, client, exception to v2 making them public group. Blocked on v2: Support requirement levels on public v2 groups weaver#1584
     • Refactor messaging into v2 spans and span refinements instead of attribute groups #3904
     • faas v2: move common attrs into spans #3905
     • Convert hw metrics to v2, add refinements for cpu, status, etc #3903
     • migrate zos entities to v2 with entity refinements - blocked on Add entity refinements to resolved schema, allow (with limits) refine identity weaver#1589
     • Browser events migration from body fields to attributes #3851
  3. Registry templates update
     • blocked on public groups v2
  4. Update-markdown snippets templates
  5. generate-gh-issue-templates - @joaopgrassi - should be trivial, no blockers
     • Convert "areas drop-down generation" make target to schema V2 #3867
  6. check-dead-yaml - @joaopgrassi
     • should be trivial, no blockers
     • Migrate "dead yaml" check to schema v2 #3878
  7. generate-schema-next
     • This could be the time we start publishing v2 schema - dev and stable flavors
     • If it's blocked, we can switch it to v2 and still produce old schema files - this part should be trivial
• After the output is on v2 (specifically p2 above - templates), we can continue updating definitions.
  • tip: use AI skill https://gist.github.com/lmolkova/6b54c77646488fa457c54894052e3df1 to migrate

[Dipanshusinghh]

Hey @joaopgrassi, can I take this one?

I went through the v2 docs and the existing HTTP convention
files - looks like we need to rewrite them to use the new
definition/2 format with proper spans, metrics, attribute
groups and entity_associations.

Already have a rough draft ready

[thompson-tomo]

First lot of issue's encountered after switching to v2:

• the attributes will no longer appear in the correct namespace and instead just appears in a home namespace which breaks links, usability etc. Solution proposed in [chore] switch weaver to builtin attribute filter #3836
• removal of attribute group brief/notes. Large number provide no value but what should we do for others
• renamed_to deprecation are needing boilerplate notes added Renamed_to deprecations now require note with v2 weaver#1556

Open question

• do we add an attribute group registry section? So that we can see what is defined, their status, brief & id