Update Zipkin remoteEndpoint preferences

[MrAlias]

Do not reference semantic conventions that have been removed.

• The net.peer.ip attribute was removed: Define net.sock attributes and clarify logical net.peer|host.name attributes #2614
  • Replace this with net.sock.peer.addr and or net.sock.peer.name
• The http.host attribute was removed: Remove alternative attribute sets from HTTP semantic conventions #2469

[pellared]

Can you also update

opentelemetry-specification/specification/logs/data-model.md

Line 850 in 025f8fc

<td>Attributes["net.peer.ip"]</td>

and

opentelemetry-specification/specification/logs/data-model.md

Line 862 in 025f8fc

<td>Attributes["net.peer.name"]</td>

for consistency?

[MrAlias]

Can you also update

opentelemetry-specification/specification/logs/data-model.md

Line 850 in 025f8fc

<td>Attributes["net.peer.ip"]</td>

and

opentelemetry-specification/specification/logs/data-model.md

Line 862 in 025f8fc

<td>Attributes["net.peer.name"]</td>

for consistency?

I would rather scope this PR to updating the Zipkin remote endpoint preferences. Maybe that is a good change for another PR?

[pellared]

I would rather scope this PR to updating the Zipkin remote endpoint preferences.

I am fine with this.

Maybe that is a good change for another PR?

Let me know if you want to do it or I should create it.

[MrAlias]

Let me know if you want to do it or I should create it.

Yeah, please create one. Thanks!

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.

[pellared]

@lmolkova PTAL

[lmolkova]

Thanks!

[carlosalberto]

@pellared Is your changes request still valid?

[pellared]

@pellared Is your changes request still valid?

Comments addressed. Approved 👍

[carlosalberto]

cc @yurishkuro

[yurishkuro]

tbh, I don't understand how to read that table. It gives OTEL names and OTEL definitions - how does that help in translating to Zipkin format? I would've expected either the equivalent Zipkin tag or the dedicated field in Zipkin data model.

[MrAlias]

tbh, I don't understand how to read that table. It gives OTEL names and OTEL definitions - how does that help in translating to Zipkin format? I would've expected either the equivalent Zipkin tag or the dedicated field in Zipkin data model.

The table is an ordered ranking. This PR does not introduce or advocate for the table, it only updates semantic conventions. The table currently contains semantic conventions that were removed. This removes the stale values and replaces them with the replacement semantic conventions. It is an editorial change.

cc @carlosalberto

[carlosalberto]

This looks good to go - will merge right after 1.18.0 is released, in case there's any follow up (by Yuri or anybody that knows Zipkin better than us).