OpenTelemetry.Proto.Logs.V1.LogRecord
sealed class LogRecord : IMessage<LogRecord>, IMessage, IEquatable<LogRecord>, IDeepCloneable<LogRecord>, IBufferMessage
A log record according to OpenTelemetry Log Data Model:
https://github.com/open-telemetry/oteps/blob/main/text/logs/0097-log-data-model.md
Field number for the "attributes" field.
Field number for the "body" field.
Field number for the "dropped_attributes_count" field.
Field number for the "flags" field.
Field number for the "observed_time_unix_nano" field.
Field number for the "severity_number" field.
Field number for the "severity_text" field.
Field number for the "span_id" field.
Field number for the "time_unix_nano" field.
Field number for the "trace_id" field.
Additional attributes that describe the specific event occurrence. [Optional].
Attribute keys MUST be unique (it is not allowed to have more than one
attribute with the same key).
A value containing the body of the log record. Can be for example a human-readable
string message (including multi-line) describing the event in a free form or it can
be a structured data composed of arrays and maps of other values. [Optional].
Flags, a bit field. 8 least significant bits are the trace flags as
defined in W3C Trace Context specification. 24 most significant bits are reserved
and must be set to 0. Readers must not assume that 24 most significant bits
will be zero and must correctly mask the bits when reading 8-bit trace flag (use
flags & TRACE_FLAGS_MASK). [Optional].
Time when the event was observed by the collection system.
For events that originate in OpenTelemetry (e.g. using OpenTelemetry Logging SDK)
this timestamp is typically set at the generation time and is equal to Timestamp.
For events originating externally and collected by OpenTelemetry (e.g. using
Collector) this is the time when OpenTelemetry's code observed the event measured
by the clock of the OpenTelemetry code. This field MUST be set once the event is
observed by OpenTelemetry.
For converting OpenTelemetry log data to formats that support only one timestamp or
when receiving OpenTelemetry log data by recipients that support only one timestamp
internally the following logic is recommended:
- Use time_unix_nano if it is present, otherwise use observed_time_unix_nano.
Value is UNIX Epoch time in nanoseconds since 00:00:00 UTC on 1 January 1970.
Value of 0 indicates unknown or missing timestamp.
Numerical value of the severity, normalized to values described in Log Data Model.
[Optional].
The severity text (also known as log level). The original string representation as
it is known at the source. [Optional].
A unique identifier for a span within a trace, assigned when the span
is created. The ID is an 8-byte array. An ID with all zeroes is considered
invalid. Can be set for logs that are part of a particular processing span.
If span_id is present trace_id SHOULD be also present. [Optional].
time_unix_nano is the time when the event occurred.
Value is UNIX Epoch time in nanoseconds since 00:00:00 UTC on 1 January 1970.
Value of 0 indicates unknown or missing timestamp.
A unique identifier for a trace. All logs from the same trace share
the same `trace_id`. The ID is a 16-byte array. An ID with all zeroes
is considered invalid. Can be set for logs that are part of request processing
and have an assigned trace id. [Optional].
public LogRecord()