This repository has been archived by the owner on Dec 6, 2024. It is now read-only.
Propose OpenTelemetry Profiling Vision #212
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
inge4pres
reviewed
Aug 30, 2022
tigrannajaryan
approved these changes
Sep 1, 2022
Co-authored-by: Tigran Najaryan <[email protected]>
lizthegrey
approved these changes
Sep 3, 2022
reyang
reviewed
Sep 6, 2022
reyang
reviewed
Sep 6, 2022
reyang
reviewed
Sep 6, 2022
Co-authored-by: Reiley Yang <[email protected]>
Co-authored-by: Reiley Yang <[email protected]>
Co-authored-by: Reiley Yang <[email protected]>
reyang
approved these changes
Sep 6, 2022
|
+1 NB |
jsuereth
approved these changes
Sep 7, 2022
SeanHeelan
approved these changes
Sep 8, 2022
carlosalberto
approved these changes
Sep 8, 2022
|
Overall LGTM - I'm a little curious about the initial implementation and its target languages (it seems that it has been informally established the effort will start with Go and Java profiling?) |
aalexand
approved these changes
Sep 8, 2022
petethepig
approved these changes
Sep 8, 2022
aalexand
reviewed
Sep 8, 2022
djaglowski
approved these changes
Sep 8, 2022
crobert-1
approved these changes
Sep 8, 2022
|
This captures the vision and spirit of the discussions over the past few months, and is a good position from which to start this collaborative effort. I support! +1 |
Kielek
approved these changes
Sep 9, 2022
florianl
approved these changes
Sep 9, 2022
kittylyst
reviewed
Sep 9, 2022
scbjans
approved these changes
Sep 12, 2022
yurishkuro
reviewed
Sep 12, 2022
Co-authored-by: Sean Heelan <[email protected]>
Co-authored-by: Sean Heelan <[email protected]>
|
If I had to make it more concrete - I might adopt the Rust targets for OS/libc/CPU as a first approximation - especially for embedded CPUs. On a geospatial level - lat/long would be useful data for network flow modeling. Also network triangulation like pings to three servers - bandwidth might be harder to measure. |
|
I believe all comments have been addressed let me know if anything else needs to be before merging! |
yurishkuro
approved these changes
Sep 18, 2022
dashpole
approved these changes
Sep 20, 2022
|
This vision now has a large number of approvals from existing OpenTelemetry members, from OpenTelemetry Technical Committee and Governance Committee and from the new Profiling Workgroup members. I believe this shows a clear alignment on the vision from all participants. Members of @open-telemetry/technical-committee if you haven't had a chance to review this vision, please do. I will merge the PR and will consider this current vision accepted by OpenTelemetry Profiling if I don't see any further comments. |
kittylyst
approved these changes
Sep 21, 2022
|
No new comments. Lots of approvals. Merging. |
4 tasks
carlosalberto
pushed a commit
to carlosalberto/oteps
that referenced
this pull request
Oct 23, 2024
This change proposes high-level items that define our long-term vision for Profiling support in OpenTelemetry project. A group of open source maintainers, vendors, end-users, and developers excited about profiling / otel have been meeting for ~8 weeks now and this document was created collectively in order to share with the broader community for feedback. We've had ~15 people contribute directly to the document and over 60 people who have attended our meetings over the past couple of months. This idea of "Adding profiling as a support event type" has also been discussed at length in [this issue](open-telemetry#139) created in October 2020. If this proposal is accepted/approved then we will proceed with filling out this [project tracking issue](open-telemetry/opentelemetry-specification#2731) and following the other procedures outlined in the [project management instructions](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/project-management.md). Comments, ideas, feedback, etc. are all very welcome and highly appreciated!
carlosalberto
pushed a commit
to carlosalberto/oteps
that referenced
this pull request
Oct 23, 2024
This change proposes high-level items that define our long-term vision for Profiling support in OpenTelemetry project. A group of open source maintainers, vendors, end-users, and developers excited about profiling / otel have been meeting for ~8 weeks now and this document was created collectively in order to share with the broader community for feedback. We've had ~15 people contribute directly to the document and over 60 people who have attended our meetings over the past couple of months. This idea of "Adding profiling as a support event type" has also been discussed at length in [this issue](open-telemetry#139) created in October 2020. If this proposal is accepted/approved then we will proceed with filling out this [project tracking issue](open-telemetry/opentelemetry-specification#2731) and following the other procedures outlined in the [project management instructions](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/project-management.md). Comments, ideas, feedback, etc. are all very welcome and highly appreciated!
carlosalberto
pushed a commit
to carlosalberto/oteps
that referenced
this pull request
Oct 30, 2024
This change proposes high-level items that define our long-term vision for Profiling support in OpenTelemetry project. A group of open source maintainers, vendors, end-users, and developers excited about profiling / otel have been meeting for ~8 weeks now and this document was created collectively in order to share with the broader community for feedback. We've had ~15 people contribute directly to the document and over 60 people who have attended our meetings over the past couple of months. This idea of "Adding profiling as a support event type" has also been discussed at length in [this issue](open-telemetry#139) created in October 2020. If this proposal is accepted/approved then we will proceed with filling out this [project tracking issue](open-telemetry/opentelemetry-specification#2731) and following the other procedures outlined in the [project management instructions](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/project-management.md). Comments, ideas, feedback, etc. are all very welcome and highly appreciated!
carlosalberto
pushed a commit
to open-telemetry/opentelemetry-specification
that referenced
this pull request
Nov 8, 2024
This change proposes high-level items that define our long-term vision for Profiling support in OpenTelemetry project. A group of open source maintainers, vendors, end-users, and developers excited about profiling / otel have been meeting for ~8 weeks now and this document was created collectively in order to share with the broader community for feedback. We've had ~15 people contribute directly to the document and over 60 people who have attended our meetings over the past couple of months. This idea of "Adding profiling as a support event type" has also been discussed at length in [this issue](open-telemetry/oteps#139) created in October 2020. If this proposal is accepted/approved then we will proceed with filling out this [project tracking issue](#2731) and following the other procedures outlined in the [project management instructions](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/project-management.md). Comments, ideas, feedback, etc. are all very welcome and highly appreciated!
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change proposes high-level items that define our long-term vision for
Profiling support in OpenTelemetry project.
A group of open source maintainers, vendors, end-users, and developers excited about profiling / otel have been meeting for ~8 weeks now and this document was created collectively in order to share with the broader community for feedback. We've had ~15 people contribute directly to the document and over 60 people who have attended our meetings over the past couple of months.
This idea of "Adding profiling as a support event type" has also been discussed at length in this issue created in October 2020.
If this proposal is accepted/approved then we will proceed with filling out this project tracking issue and following the other procedures outlined in the project management instructions.
Comments, ideas, feedback, etc. are all very welcome and highly appreciated!