Skip to content

Update ScopeProfiles to Profile relationships diagram to 1-n#684

Merged
tigrannajaryan merged 3 commits intoopen-telemetry:mainfrom
dd-ryanrosario:main
Aug 8, 2025
Merged

Update ScopeProfiles to Profile relationships diagram to 1-n#684
tigrannajaryan merged 3 commits intoopen-telemetry:mainfrom
dd-ryanrosario:main

Conversation

@dd-ryanrosario
Copy link
Copy Markdown
Contributor

Updated the relationship between ScopeProfiles and Profile from 1-1 to 1-n in the relationships diagram. This is a documentation-only change that fixes the diagram to accurately reflect the actual data model.

The protobuf message definition shows:

message ScopeProfiles {
  // The instrumentation scope information for the profiles in this message.
  // Semantically when InstrumentationScope isn't set, it is equivalent with
  // an empty instrumentation scope name (unknown).
  opentelemetry.proto.common.v1.InstrumentationScope scope = 1;

  // A list of Profiles that originate from an instrumentation scope.
  repeated Profile profiles = 2;
  ...
}

The repeated Profile profiles field indicates a one-to-many relationship, where a single ScopeProfiles can contain multiple Profile instances. The inconsistency in the diagram seems to have originated here when removing ProfileContainer.

@dd-ryanrosario dd-ryanrosario requested review from a team July 21, 2025 18:00
@tigrannajaryan tigrannajaryan merged commit 7e2e91a into open-telemetry:main Aug 8, 2025
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants