Proposal: Service and Deployment Semantic Conventions

[janhvi31]

This PR proposes the formation of a new Special Interest Group: Service and Deployment semconv SIG.

The SIG will focus on stabilizing and extending semantic conventions for logical entities such as Service and Deployment, i.e., concepts that do not have a direct physical representation but are critical for how users tag, label, and reason about resources.

The work will proceed in three phases:

Phase 1: Extend the Service entity with new attributes such as service.owner and service.criticality.

Phase 2: Stabilize the deployment.environment.name attribute and complete the model for deployment-related entities.

Phase 3: Formulate a plan for tagging resources with sensitivity labels (e.g., data.sensitivity) and define how these interact with other telemetry.

The goal of this effort is to provide a shared semantic layer for these logical entities that can be adopted consistently across OpenTelemetry SDKs, resource detectors, and downstream observability, security, and governance tools. Standardization will reduce fragmentation, enable consistent cross-cloud attribution, and improve interoperability across platforms.

---

TODOs:

• Expand the list of domain experts and contributors
• Define meeting cadence and time
• Create Slack channel, agenda doc, calendar entry
• Set up GitHub project board to track deliverables

---

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: janhvi31 / name: Janhvi Gohri (5535c61, 1fa288d, 50525a8, 322156c, 772945f, eec65cf, b8f19d4, 198bc37, f0e7be2, 89194d4, 7de47ac, 193a2f3, 71c80f3, e6504bc, 4d51d70, bb0a5ee, af47b9f, b7913e7, 4958dfa, 6cfd0ad, 42b547a, a847224, 7d7924a)
• ✅ login: janhvi31 / name: janhvi31 (d7c1136, 33d6a90)
• ✅ login: trask / name: Trask Stalnaker (824c395, b24b11d, a86d608)

[danielgblanco]

cc @open-telemetry/specs-semconv-maintainers could you help us review this one?

[janhvi31]

Pinging relevant people here.
@jsuereth @ymotongpoo @trask @ralf0131 @horovits

[reyang]

@janhvi31 could you clear EasyCLA? Thanks!

[janhvi31]

Created the meeting cadence: https://strawpoll.com/2ayLQXNDBn4
@trask @reyang @ymotongpoo @ralf0131 @jsuereth @tylerkight Could you please vote or suggest alternative schedule as per your availability
Thanks!

[jpkrohling]

I'd love to join this effort.

[janhvi31]

Sent an invite for 9th Oct for the first SIG meeting. Feel free to invite/add more folks to it.

Here is the call details:
Service and Deployment Sem Conv SIG sync
Thursday, 9 October · 8:30 – 9:00pm
Time zone: Asia/Kolkata
Google Meet joining info
Video call link: https://meet.google.com/txs-tnjz-jkb
Or dial: ‪(IN) +91 22 7127 9696‬ PIN: ‪223 268 531 0078‬#
More phone numbers: https://tel.meet/txs-tnjz-jkb?pin=2232685310078

[svrnm]

Sent an invite for 9th Oct for the first SIG meeting. Feel free to invite/add more folks to it.

Here is the call details:

Service and Deployment Sem Conv SIG sync

Thursday, 9 October · 8:30 – 9:00pm

Time zone: Asia/Kolkata

Google Meet joining info

Video call link: https://meet.google.com/txs-tnjz-jkb

Or dial: ‪(IN) +91 22 7127 9696‬ PIN: ‪223 268 531 0078‬#

More phone numbers: https://tel.meet/txs-tnjz-jkb?pin=2232685310078

Invites for SIG meetings should come from the OpenTelemetry project account to ensure continuity

Please use this issue template:

https://github.com/open-telemetry/community/issues/new?template=sig-onboarding.yml