-
Notifications
You must be signed in to change notification settings - Fork 893
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider adding a resource (semantic convention) to distinguish HTTP applications (http.app attribute) #335
Comments
Currently there is already a spec on what an HTTP app is in the semantic conventions, but no way to represent it, see https://github.com/open-telemetry/opentelemetry-specification/blob/4ab7c2fb4964c14fe972b03b5bb6825573bafb24/specification/data-http.md#http-server-definitions:
We also need to hash out differences to the service Resource https://github.com/open-telemetry/opentelemetry-specification/blob/4ab7c2fb4964c14fe972b03b5bb6825573bafb24/specification/data-resource-semantic-conventions.md#service |
The use-case where a single application is mounted on multiple (virtual host, root path) pairs seems pretty obscure to me, but not unreasonable. |
Agree, I also had that thought when re-reading the spec quoted above. But I think that's a minor detail here. |
Is there anything unique to HTTP? What about RPC processes, AMQP processes, etc. |
The initial problem here is not that service.name in particular would imply process-level isolation, but that the Resource concept itself allows only one resource per process (technically per TracerProvider, but usually there is at least one static/global variable that references this, so it's effectively per process). |
This might be solvable by open-telemetry/oteps#78. |
In some application servers, you can run multiple applications. We need a way to separate spans created by them and properly export them as multiple services. See open-telemetry/opentelemetry-java#1109. This can be done currently in OpenTracing. It is important to have this capability in OpenTelemetry 1.0. |
See #263 (comment) and #263 (comment).
We should find a way to represent information about the HTTP application (proposed name semantic attribute name
http.app
) somewhere, ideally somewhere where for each incoming HTTP request a different application can be selected (even though the most common case is that of one app per process)The text was updated successfully, but these errors were encountered: