You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 25, 2022. It is now read-only.
This library should provide an simple mechanism for isolating a LoggerName value, which will be used later in the data pipeline (specifically here), to populate the InstrumentationScope.
The following is suggested:
Add LoggerName to entry.Entry. (This does not imply that LoggerName is a top level field in the data model. It is simply a means to convey this information until the log entry is batched by Instrumentation Scope.)
Add a logger_name block, which follows the same pattern as timestamp and severity. Specifically, this means that every parser may optionally assign a string value to LoggerName.
The text was updated successfully, but these errors were encountered:
This change follows from (specification) #2276
This library should provide an simple mechanism for isolating a LoggerName value, which will be used later in the data pipeline (specifically here), to populate the InstrumentationScope.
The following is suggested:
LoggerName
toentry.Entry
. (This does not imply thatLoggerName
is a top level field in the data model. It is simply a means to convey this information until the log entry is batched by Instrumentation Scope.)logger_name
block, which follows the same pattern astimestamp
andseverity
. Specifically, this means that every parser may optionally assign a string value to LoggerName.The text was updated successfully, but these errors were encountered: