-
Notifications
You must be signed in to change notification settings - Fork 237
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
Propose a new K8s SemConv SIG project #2352
Conversation
Pinging relevant people here. Please explicitly ask for being included in the domain experts list if you are not already. /cc @open-telemetry/semconv-k8s-approvers @open-telemetry/semconv-container-approvers @TylerHelmuth @dmitryax @dashpole @jinja2 @frzifus @mx-psi @povilasv @jamesmoessis @AlexanderWert @rogercoll @braydonk @jsuereth Feel free to advertise this and/or proposing people for joining this project. |
dedc5fb
to
c4c53f2
Compare
Thanks for pushing this SIG @ChrsMark ! I think it is really needed to standardize all the I would gladly join the SIG and share my domain expertise, specially in the containers area. |
I support the new SIG! I don't have enough expertise in the general k8s area to join, but will spread the word with some more knowledgeable folks to see who would be interested. |
As a maintainer of the operator and helm charts, id love to be added to this effort. It would be great if we could improve and standardize more in the k8s world. |
Thanks @ChrsMark , happy to see this proposal, can we extend this SIG a little bit to cover k8s cost as well by https://github.com/opencost? |
Thank's for the suggestion @gyliu513! @gyliu513 do you have specific semantic conventions in mind that you would like to introduce? If so, you can always propose them with an issue and it could be added in the SIG's backlog. |
Thanks for starting the SIG! I'm happy to help with this effort |
Any suggestions/proposals regarding meeting times? I suggest we start with bi-weekly meetings. Looking into https://calendar.google.com/calendar/u/0/embed?src=c_2bf73e3b6b530da4babd444e72b76a6ad893a5c3f43cf40467abc7a9a897f977@group.calendar.google.com, I see |
8 am is also the Promethues WG, with I lead, but it is every-other-week. I could join if we also did this project every other week offset from the prometheus wg. |
7b1cfa2
to
bbd1ac0
Compare
We are still in need of a second sponsor for this SIG. Based on #2361 someone from @open-telemetry/specs-semconv-maintainers can be the 2nd sponsor here. |
I'm happy to sponsor this effort! |
It seems that we have a 2nd sponsor from SemConv maintainers. We will need to add:
But these can be added after we have merged this first PR for the project. Could we get some eyes from the GC please? |
45bf8bf
to
9a65223
Compare
e4a62e3
to
6c489ce
Compare
@AlexanderWert can you review/approve? thanks! |
Signed-off-by: ChrsMark <[email protected]>
Signed-off-by: ChrsMark <[email protected]>
45c6801
to
ff0c792
Compare
@open-telemetry/governance-committee please review, I think we decided we want approvals from majority of GC for new projects I've added this to Thursday's Governance Committee meeting agenda in case we don't have enough GC approvals by then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like a solid proposal 👍
I have filed #2371 to add the project board. We will still need a |
this should be done now: #2372 (comment)
I've added this topic to this week's GC meeting agenda |
see #2377 |
The Opentelemetry community would like to work on K8s Semantic Conventions in order to add any missing attributes and/or metrics and stabilize the existing ones. The primary goal of this is to help with the adoption of the respective OTel Collector receivers and processors.
TODOS: