You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Logs, metrics, and traces have already gone through a similar process to become more standardized and seeing as we have identified profiling as an "increasingly important" observability signal in our whitepaper it would be great for the observability tag to help provide input / resources towards this effort.
Several interested groups from a profiling-developer slack channel, the OTEL issue linked above, and some who discussed this live at Kubecon EU this year have started to plan for making progress on this and I've compiled some general thoughts about possible next steps in a doc here.
I'd love to discuss this as a group at the next meeting and also to gather thoughts, ideas, opinions, etc here as well!
The text was updated successfully, but these errors were encountered:
I DO think we should ideate (new issues / ideas heartily welcomed!) on how we maintain connection and alignment with the newly formed SIG Profiling, but the projects in-scope for the TAG generally, open-telemetry inclusive.
As profiling has grown in popularity and more companies have started to build tooling around profiling, there has been a lot of discussion about adding profiling as an official OTEL supported event type.
Logs, metrics, and traces have already gone through a similar process to become more standardized and seeing as we have identified profiling as an "increasingly important" observability signal in our whitepaper it would be great for the observability tag to help provide input / resources towards this effort.
Several interested groups from a profiling-developer slack channel, the OTEL issue linked above, and some who discussed this live at Kubecon EU this year have started to plan for making progress on this and I've compiled some general thoughts about possible next steps in a doc here.
I'd love to discuss this as a group at the next meeting and also to gather thoughts, ideas, opinions, etc here as well!
The text was updated successfully, but these errors were encountered: