Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR introduces the foundational changes necessary for supporting
logs
data in themdatagen
tool.mdatagen files for logs
This update includes the generation of
generated_logs.go
andgenerated_logs_test.go
. These files are specifically for receiver and scraper components that supportlogs
data, enabling initial log handling capabilities.Introducing LogsBuilder
This PR introduced a
LogsBuilder
similar to the existingMetricsBuilder
. It provides a structured way to manage log data with the following functions:Emit(...ResourceLogsOption)
Similar to
Emit
function in MetricsBuilderEmitForResource(...ResourceLogsOption)
Similar to
EmitForResource
function in MetricsBuilderAppendLogRecord(plog.LogRecord)
This function appends a log record to an internal buffer. The buffered log records are used to construct a
ScopeLog
when theEmit()
orEmitForResource()
functions are called. Scope name and version are automatically generated.Next steps
metadata.yml
to send structured logsExample usage:
Example output:
Link to tracking issue
Part of #12571
Testing
Added
Documentation
Added