Declare logs Stable

[tigrannajaryan]

The log data model is now declared Stable: open-telemetry/opentelemetry-specification#2387

The OTLP proto in this repository now matches the log data model
in the specification.

This PR declares OTLP proto for logs Stable as well.

--

Please review the messages related to logs in this repository and make sure they match the log data model in the spec.
If you have any other concerns with regards to declaring the logs Stable please voice them.

[codeboten]

Will moving forward the stability of JSON support be possible with logs being declared stable? #230

[tigrannajaryan]

Will moving forward the stability of JSON support be possible with logs being declared stable? #230

JSON for all signal types (not just logs) is explicitly declared Alpha for now. Declaring OTLP Logs stable will not change that. We will work on stabilizing JSON separately.

[tigrannajaryan]

Here is the audit that shows all log data model fields are present in OTLP:

Data Model	OTLP
Timestamp	LogRecord.time_unix_nano
ObservedTimestamp	LogRecord. observed_time_unix_nano
TraceId	LogRecord.trace_id
SpanId	LogRecord.span_id
TraceFlags	LogRecord.flags & TRACE_FLAGS_MASK
SeverityText	LogRecord.severity_text
SeverityNumber	LogRecord.severity_number
Body	LogRecord.body
Resource	ResourceLogs.resource
InstrumentationScope	ScopeLogs.scope
Attributes	LogRecord.attributes

[tigrannajaryan]

I would like to wait for open-telemetry/opentelemetry-log-collection#466 to be merged and then consumed as a dependency in the Collector before we declare logs stable (that log-collection library PR makes changes to Timestamp/ObservedTimestamp column as defined by logs data model). We do not expect any pushback or log data model stability as a result of log-collection library changes, but I still would like to move slowly to give enough time for any unknown issues to be discovered.

[tigrannajaryan]

@djaglowski I see that open-telemetry/opentelemetry-log-collection#466 is now merged. I want to wait until the changes it introduces are also used in the Collector and we confirm that everything works nicely. Can you ping me after that is done so that we can move forward this stability declaration here?

[djaglowski]

@tigrannajaryan, yes, I know a a couple minor changes that need to happen. I'll also do a final audit to make sure we haven't missed anything. Will let you know.

[djaglowski]

The final issue that I am aware of has been addressed as of this morning.

[tigrannajaryan]

I want to also finish the removal of LogRecord Name field from the Collector codebase. It is currently blocked on open-telemetry/opentelemetry-collector-contrib#9258

[tigrannajaryan]

open-telemetry/opentelemetry-collector-contrib#9258 is now resolved. All recent changes to the logs proto are now propagated to the Collector and have been used without any problems.

There are no known issues that block log proto stability declaration that I am aware of. I believe this is now ready to move forward.

[codeboten]

There are known issues that block log proto stability declaration that I am aware of. I believe this is now ready to move forward.

@tigrannajaryan did you mean there are no known issues?

[tigrannajaryan]

There are known issues that block log proto stability declaration that I am aware of. I believe this is now ready to move forward.

@tigrannajaryan did you mean there are no known issues?

Yes, updated, it was a typo.

[bogdandrutu]

we should get couple more +1 from log SIG members

[tigrannajaryan]

Let's merge this after 0.17.0 is released.

[tigrannajaryan]

This looks good to go. Merging.