Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify parameters for emtting a log record #3354

Merged
merged 17 commits into from
Apr 8, 2023

Conversation

alanwest
Copy link
Member

@alanwest alanwest commented Mar 31, 2023

Supersedes #3350

Clarifies the parameters for emitting a log record.

Context was particularly confusing. Context is not a property of the LogRecord data model. Cleans up section of bridge API spec that seems to suggest that Context is a field of LogRecord. Also, clarifies that Context can be associated with an emitted LogRecord. We have similar language in the trace API that leaves room for languages to achieve this in an idiomatic way. See

The API MUST accept the following parameters:
- The span name. This is a required parameter.
- The parent `Context` or an indication that the new `Span` should be a root `Span`.
The API MAY also have an option for implicitly using
the current Context as parent as a default behavior.

@tigrannajaryan
Copy link
Member

@alanwest please fix the build.

alanwest and others added 3 commits April 6, 2023 11:07
Co-authored-by: Reiley Yang <reyang@microsoft.com>
…elemetry-specification into alanwest/logs-and-context
@alanwest alanwest requested a review from a team as a code owner April 6, 2023 18:35
@jack-berg
Copy link
Member

Hey @alanwest can you add a changelog entry?

@alanwest alanwest changed the title Clarify that context is available to Emit LogRecord API Clarify parameters for emtting a log record Apr 8, 2023
@jack-berg jack-berg merged commit 29f8007 into open-telemetry:main Apr 8, 2023
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.

None yet

8 participants