샘플
Span limits drop the newest attributes but drop the oldest events when their respective maximum counts are reached
sha256:f85f3f62b2c67441601414e7380c232460df64cef6735d90f07f6cf75e401958
PUBLISHED
L3_CONTRACT_PASS
MIT-0
실행 증거
선언된 환경과 서명된 검증 실행을 분리해 이 샘플이 실제로 증명하는 범위를 보여줍니다.
증거 기준서명된 컨트랙트 통과
검증 영수증1
검증 수준L3_CONTRACT_PASS
선언된 환경
- 실행 컨텍스트
- go
- 운영체제
- linux
- 아키텍처
- x64
- 런타임
- go
- 언어
- go
- 패키지 매니저
- go
검증 실행 환경
- 실행 컨텍스트
- go 1.26
- 운영체제
- linux alpine · musl
- 아키텍처
- x64
- 런타임
- go 1.26
- 언어
- go
- 패키지 매니저
- go
- 실행 방식
- container · docker
CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-17
케이스
- 목표
- Span limits drop the newest attributes but drop the oldest events when their respective maximum counts are reached HOW
- 패키지
-
go.opentelemetry.io/otel/sdk v1.45.0
- 환경
- go
- 생성일
- 2026-08-17T06:47:26Z
흔히 이렇게 알고 있다
Capacity limits on a span apply a uniform dropping strategy, meaning both attributes and events would drop the newest entries or both would drop the oldest entries.
이 샘플의 작성자가 여기서 개발자나 모델이 기대할 법한 내용으로 적어둔 것이다. 아래 계약이 실제로 실행된 것이다.
컨트랙트
- When AttributeCountLimit is 3 and five attributes are added in order a0…a4, span.Attributes() contains exactly the first three (a0, a1, a2), not the last three — new arrivals are silently dropped, not old ones.
- DroppedAttributes() reports exactly 2 (the two attributes that were rejected when the store was already at capacity).
- When EventCountLimit is 3 and five events are added in order e0…e4, span.Events() contains exactly the last three (e2, e3, e4) — the oldest events are evicted from the front of the queue, opposite to attributes.
- DroppedEvents() reports exactly 2 (the two events evicted from the front of the queue).
파일
- NOTES.md
- csx.json
- go.mod
- go.sum
- limits_asymmetry_test.go
소스 아티팩트 내려받기 (tar.gz)
오리진 시더
csx-seed
검증 영수증
- go 1.26 · linux alpine/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-17 · ed25519:d91480838ac982c9