[RFC]Track semantics convention updates

[YANG-DB]

Is your feature request related to a problem?

Track the SS4O semantic convention updates [ Traces / Metrics / Logs ]

Standard

• http:
  • [FEATURE]Align HTTP Traces mapping to OpenTelemetry semantics Convention #24 | add http Semantic-Convention for metrics & spans #36
• cloud (provider + event):
  • [FEATURE]Update Cloud mapping with the OTEL conventions #45 | #
• database:
  • [FEATURE]Update database mapping with the OTEL conventions #47 | #
• exceptions:
  • [FEATURE]Update exceptions mapping with the OTEL conventions #48 | #
• faas:
  • [FEATURE]Update FAAS mapping with the OTEL conventions #49 | #
• feature-flag:
  • [FEATURE]Update Feature-Flag mapping with the OTEL conventions #50 | #
• messaging:
  • [FEATURE]Update Messaging mapping with the OTEL conventions #51 | #
• object-store:
  • see S3 AWS's vendor specific
• rpc:
  • [FEATURE]Update RPC mapping with the OTEL conventions #52 | #
• system:
  • [FEATURE]Update System mapping with the OTEL conventions #53 | #

---

Vendor Specific

AWS

• ELB:
  • [FEATURE] Update aws_elb and communication schemas #44 | #
• RDS:
  • [FEATURE]Update AWS.RDS mapping vendor specific #54 | #
• VPC:
  • [FEATURE]Update AWS.VPC flow logs mapping vendor specific #55 | #
• S3:
  • [FEATURE]Update AWS.S3 mapping vendor specific #56 | #
• WAF:
  • [FEATURE]Update AWS.WAF mapping vendor specific  #57 | #
• ElastiCache:
  • [FEATURE]Update AWS.ElastiCache mapping vendor specific #58 | #
• CloudTrail:
  • [FEATURE]Update AWS.CloudTrail mapping vendor specific #59 | #

Do you have any additional context?

• https://github.com/open-telemetry/semantic-conventions/tree/main/docs
• https://github.com/opensearch-project/opensearch-catalog/tree/main/schema/observability/