Update semconv to 1.21.0

[dyladan]

Opening as a draft as there are quite a few breaking changes. There are a couple ways we can go about this:

1. Bump to 2.0. Probably want to combine with some structure updates for ongoing experimental updates without bumping major version every time.
2. Manually add back the removed/renamed properties with @deprecated comments

Breaking changes by specification version

1.20.0

• BREAKING: remove messaging.destination.kind and messaging.source.kind.
  (BREAKING: remove messaging.destination.kind and messaging.source.kind values opentelemetry-specification#3214,
  AWS Lambda - remove references to messaging.destination.kind and messaging.source.kind opentelemetry-specification#3348)
• BREAKING: Change span statuses for gRPC server spans.
  (BREAKING: Change span statuses for gRPC server spans opentelemetry-specification#3333)
• BREAKING: Remove http.status_code attribute from the
  http.server.active_requests metric.

1.19.0

• BREAKING: Rename faas.execution to faas.invocation_id
  (Rename faas.execution to faas.invocation_id and change units for faas.max_memory opentelemetry-specification#3209)
• BREAKING: Change faas.max_memory units to Bytes instead of MB
  (Rename faas.execution to faas.invocation_id and change units for faas.max_memory opentelemetry-specification#3209)
• BREAKING: Expand scope of faas.id to cloud.resource_id
  (Expand scope of faas.id to cloud.resource_id opentelemetry-specification#3188)

1.17.0

• Refactor messaging attributes and per-message attributes in batching scenarios.
  (Refactor messaging attributes and specify per-message attributes opentelemetry-specification#2957).
  BREAKING: renames
  • messaging.consumer_id to messaging.consumer.id
  • messaging.destination to messaging.destination.name
  • messaging.temp_destination to messaging.destination.temporary
  • messaging.destination_kind to messaging.destination.kind
  • messaging.message_id to messaging.message.id
  • messaging.protocol to net.app.protocol.name
  • messaging.protocol_version to net.app.protocol.version
  • messaging.conversation_id to messaging.message.conversation_id
  • messaging.message_payload_size_bytes to messaging.message.payload_size_bytes
  • messaging.message_payload_compressed_size_bytes to messaging.message.payload_compressed_size_bytes
  • messaging.rabbitmq.routing_key to messaging.rabbitmq.destination.routing_key
  • messaging.kafka.message_key to messaging.kafka.message.key
  • messaging.kafka.consumer_group to messaging.kafka.consumer.group
  • messaging.kafka.partition to messaging.kafka.destination.partition
  • messaging.kafka.tombstone to messaging.kafka.message.tombstone
  • messaging.rocketmq.message_type to messaging.rocketmq.message.type
  • messaging.rocketmq.message_tag to messaging.rocketmq.message.tag
  • messaging.rocketmq.message_keys to messaging.rocketmq.message.keys
  • Removed messaging.url
  • Renamed send operation to publish
  • Split destination and source namespaces and clarify per-message attributes in batching scenarios

Full list of removed keys

• DB_CASSANDRA_KEYSPACE
• DB_HBASE_NAMESPACE
• FAAS_EXECUTION
• NET_PEER_IP
• NET_HOST_IP
• NET_HOST_CONNECTION_TYPE
• NET_HOST_CONNECTION_SUBTYPE
• NET_HOST_CARRIER_NAME
• NET_HOST_CARRIER_MCC
• NET_HOST_CARRIER_MNC
• NET_HOST_CARRIER_ICC
• HTTP_HOST
• HTTP_FLAVOR
• HTTP_USER_AGENT
• HTTP_REQUEST_CONTENT_LENGTH_UNCOMPRESSED
• HTTP_RESPONSE_CONTENT_LENGTH_UNCOMPRESSED
• HTTP_SERVER_NAME
• HTTP_CLIENT_IP
• MESSAGING_DESTINATION_KIND
• MESSAGING_TEMP_DESTINATION
• MESSAGING_PROTOCOL
• MESSAGING_PROTOCOL_VERSION
• MESSAGING_URL
• MESSAGING_CONVERSATION_ID
• MESSAGING_CONSUMER_ID
• MESSAGING_RABBITMQ_ROUTING_KEY
• MESSAGING_KAFKA_CLIENT_ID
• MESSAGING_KAFKA_PARTITION
• MESSAGING_KAFKA_TOMBSTONE
• NetTransportValues.IP_TCP
• NetTransportValues.IP_UDP
• NetTransportValues.IP
• NetTransportValues.UNIX
• NetTransportValues.INPROC
• NetTransportValues.OTHER
• NetHostConnectionTypeValues
• NetHostConnectionSubtypeValues
• HttpFlavorValues
• MessagingDestinationKindValues

[dyladan]

Tests are failing because of the breaking changes used by the instrumentations.

[github-actions]

This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.

[github-actions]

This PR was closed because it has been stale for 14 days with no activity.