up

docs/messaging/messaging-metrics.md

@@ -153,7 +153,6 @@ the broker doesn't have such notion, the destination name SHOULD uniquely identi
 <!-- END AUTOGENERATED TEXT -->
 <!-- endsemconv -->
 
-
 ## Producer metrics
 
 ### Metric: `messaging.client.published.messages`
@@ -263,7 +262,6 @@ the broker doesn't have such notion, the destination name SHOULD uniquely identi
 <!-- END AUTOGENERATED TEXT -->
 <!-- endsemconv -->
 
-
 ## Consumer metrics
 
 ### Metric: `messaging.client.consumed.messages`
@@ -374,7 +372,6 @@ the broker doesn't have such notion, the destination name SHOULD uniquely identi
 <!-- END AUTOGENERATED TEXT -->
 <!-- endsemconv -->
 
-
 ### Metric: `messaging.process.duration`
 
 When this metric is reported alongside a messaging process span, the metric value SHOULD be the same as the corresponding span duration.
@@ -488,7 +485,6 @@ the broker doesn't have such notion, the destination name SHOULD uniquely identi
 <!-- END AUTOGENERATED TEXT -->
 <!-- endsemconv -->
 
-
 [DocumentStatus]: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/document-status.md
 [MetricRequired]: /docs/general/metric-requirement-level.md#required
 [MetricRecommended]: /docs/general/metric-requirement-level.md#recommended

model/trace/messaging.yaml

@@ -73,9 +73,6 @@ groups:
     attributes:
       - ref: messaging.system
         requirement_level: required
-      - ref: messaging.batch.message_count
-        requirement_level:
-          conditionally_required: If the span describes an operation on a batch of messages.
       - ref: messaging.client.id
         requirement_level: recommended
       - ref: messaging.destination.partition.id