Add starfish v1 attributes to span data/breadcrumbs

[cleptric]

Closes #765

See https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/trace/semantic_conventions

[stayallive]

For a response recieved we do not duplicate them but removed the old names. Should we here too? Also they can be null should we then not include them at all?

[cleptric]

Was an oversight, removed!

Hmm, good question, @AbhiPrasad ? 😬

[mfb]

Are there also standards for how http.server transactions are tagged? I noticed that laravel and symfony do it a bit differently.

[AbhiPrasad]

Are there also standards for how http.server transactions are tagged

We have some, but they are sparse. If you create a GH issue with the inconsistencies we can take a look and audit.

[mfb]

We have some, but they are sparse. If you create a GH issue with the inconsistencies we can take a look and audit.

Not sure where to open an issue, but in

sentry-laravel/src/Sentry/Laravel/Tracing/Middleware.php

Line 177 in f8685aa

$context->setData([

url and method are set as data, while in https://github.com/getsentry/sentry-symfony/blob/3e9e23da8985818872cf91e5d5d59895a1421154/src/EventListener/TracingRequestListener.php#L89 http.url and http.method are set as tags.

[cleptric]

Moving forward, we'll remove tags set by the SDK and rely on request/response context and span data instead.

[AbhiPrasad]