(chore) Resource -> Entity : Part 2 : Update all group ids, group id guidance and references to group ids. (#2244)

Author: jsuereth

.chloggen/2244.yaml

@@ -0,0 +1,22 @@
+# Use this changelog template to create an entry for release notes.
+#
+# If your change doesn't affect end users you should instead start
+# your pull request title with [chore] or use the "Skip Changelog" label.
+
+# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
+change_type: enhancement
+
+# The name of the area of concern in the attributes-registry, (e.g. http, cloud, db)
+component: all
+
+# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: "Renames all `resource.*` groups to be `entity.*`"
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+# The values here must be integers.
+issues: [2244]
+
+# (Optional) One or more lines of additional information to render under the primary note.
+# These lines will be padded with 2 spaces and then inserted directly into the document.
+# Use pipe (|) for multiline entries.
+subtext: Part of open-telemetry/opentelemetry-specification#4436

docs/general/semantic-convention-groups.md

@@ -13,7 +13,7 @@ Each group has a `type` property that could be one of the following:
 - `span` - defines semantic convention for a specific type of span, such as HTTP `CLIENT`
 - `metric` - defines semantic convention for a specific metric, such as HTTP client request duration
 - `event` - defines semantic conventions for a specific event, such as exception.
-- `resource` - defines semantic conventions for a specific entity the telemetry is collected within,
+- `entity` - defines semantic conventions for a specific entity the telemetry is collected within,
   such as `service`.
 
 Groups that have `attribute_group` type do not describe semantic convention and

docs/resource/README.md

@@ -67,7 +67,7 @@ as specified in the [Resource SDK specification](https://github.com/open-telemet
 
 ## Service
 
-<!-- semconv resource.service -->
+<!-- semconv entity.service -->
 <!-- NOTE: THIS TEXT IS AUTOGENERATED. DO NOT EDIT BY HAND. -->
 <!-- see templates/registry/markdown/snippet.md.j2 -->
 <!-- prettier-ignore-start -->
@@ -140,7 +140,7 @@ service.name = Shop.shoppingcart
 
 ## Telemetry SDK
 
-<!-- semconv resource.telemetry.sdk -->
+<!-- semconv entity.telemetry.sdk -->
 <!-- NOTE: THIS TEXT IS AUTOGENERATED. DO NOT EDIT BY HAND. -->
 <!-- see templates/registry/markdown/snippet.md.j2 -->
 <!-- prettier-ignore-start -->
@@ -193,7 +193,7 @@ All custom identifiers SHOULD be stable across different versions of an implemen
 
 ## Telemetry distro
 
-<!-- semconv resource.telemetry.distro -->
+<!-- semconv entity.telemetry.distro -->
 <!-- NOTE: THIS TEXT IS AUTOGENERATED. DO NOT EDIT BY HAND. -->
 <!-- see templates/registry/markdown/snippet.md.j2 -->
 <!-- prettier-ignore-start -->

docs/resource/android.md

@@ -1,6 +1,6 @@
 # Android
 
-<!-- semconv resource.android -->
+<!-- semconv entity.android -->
 <!-- NOTE: THIS TEXT IS AUTOGENERATED. DO NOT EDIT BY HAND. -->
 <!-- see templates/registry/markdown/snippet.md.j2 -->
 <!-- prettier-ignore-start -->

docs/resource/browser.md

@@ -1,6 +1,6 @@
 # Browser
 
-<!-- semconv resource.browser -->
+<!-- semconv entity.browser -->
 <!-- NOTE: THIS TEXT IS AUTOGENERATED. DO NOT EDIT BY HAND. -->
 <!-- see templates/registry/markdown/snippet.md.j2 -->
 <!-- prettier-ignore-start -->

docs/resource/cicd.md

@@ -24,7 +24,7 @@ See also:
 
 ### CICD pipeline
 
-<!-- semconv resource.cicd.pipeline -->
+<!-- semconv entity.cicd.pipeline -->
 <!-- NOTE: THIS TEXT IS AUTOGENERATED. DO NOT EDIT BY HAND. -->
 <!-- see templates/registry/markdown/snippet.md.j2 -->
 <!-- prettier-ignore-start -->
@@ -55,7 +55,7 @@ Since this resource is unique for each pipeline run, this means instantiating se
 
 Using the CICD pipeline run resource with metrics inherently causes high cardinality and may increase costs with some metric storage backends. Thus, using CICD pipeline run resource for metrics MUST be opt-in.
 
-<!-- semconv resource.cicd.pipeline.run -->
+<!-- semconv entity.cicd.pipeline.run -->
 <!-- NOTE: THIS TEXT IS AUTOGENERATED. DO NOT EDIT BY HAND. -->
 <!-- see templates/registry/markdown/snippet.md.j2 -->
 <!-- prettier-ignore-start -->
@@ -81,7 +81,7 @@ Using the CICD pipeline run resource with metrics inherently causes high cardina
 
 ### CICD worker
 
-<!-- semconv resource.cicd.worker -->
+<!-- semconv entity.cicd.worker -->
 <!-- NOTE: THIS TEXT IS AUTOGENERATED. DO NOT EDIT BY HAND. -->
 <!-- see templates/registry/markdown/snippet.md.j2 -->
 <!-- prettier-ignore-start -->
@@ -110,7 +110,7 @@ Using the CICD pipeline run resource with metrics inherently causes high cardina
 
 ### VCS repository
 
-<!-- semconv resource.vcs.repo -->
+<!-- semconv entity.vcs.repo -->
 <!-- NOTE: THIS TEXT IS AUTOGENERATED. DO NOT EDIT BY HAND. -->
 <!-- see templates/registry/markdown/snippet.md.j2 -->
 <!-- prettier-ignore-start -->
@@ -143,7 +143,7 @@ the `.git` extension.
 
 ### VCS reference
 
-<!-- semconv resource.vcs.ref -->
+<!-- semconv entity.vcs.ref -->
 <!-- NOTE: THIS TEXT IS AUTOGENERATED. DO NOT EDIT BY HAND. -->
 <!-- see templates/registry/markdown/snippet.md.j2 -->
 <!-- prettier-ignore-start -->

docs/resource/cloud-provider/aws/ecs.md

@@ -4,7 +4,7 @@ linkTitle: ECS
 
 # AWS ECS
 
-<!-- semconv resource.aws.ecs -->
+<!-- semconv entity.aws.ecs -->
 <!-- NOTE: THIS TEXT IS AUTOGENERATED. DO NOT EDIT BY HAND. -->
 <!-- see templates/registry/markdown/snippet.md.j2 -->
 <!-- prettier-ignore-start -->

docs/resource/cloud-provider/aws/eks.md

@@ -4,7 +4,7 @@ linkTitle: EKS
 
 # AWS EKS
 
-<!-- semconv resource.aws.eks -->
+<!-- semconv entity.aws.eks -->
 <!-- NOTE: THIS TEXT IS AUTOGENERATED. DO NOT EDIT BY HAND. -->
 <!-- see templates/registry/markdown/snippet.md.j2 -->
 <!-- prettier-ignore-start -->

docs/resource/cloud-provider/aws/logs.md

@@ -4,7 +4,7 @@ linkTitle: Logs
 
 # AWS logs
 
-<!-- semconv resource.aws.log -->
+<!-- semconv entity.aws.log -->
 <!-- NOTE: THIS TEXT IS AUTOGENERATED. DO NOT EDIT BY HAND. -->
 <!-- see templates/registry/markdown/snippet.md.j2 -->
 <!-- prettier-ignore-start -->

docs/resource/cloud-provider/gcp/apphub.md

@@ -12,7 +12,7 @@ See [Supported Resources](https://cloud.google.com/app-hub/docs/supported-resour
 
 ## Application
 
-<!-- semconv resource.gcp.apphub.application -->
+<!-- semconv entity.gcp.apphub.application -->
 <!-- NOTE: THIS TEXT IS AUTOGENERATED. DO NOT EDIT BY HAND. -->
 <!-- see templates/registry/markdown/snippet.md.j2 -->
 <!-- prettier-ignore-start -->
@@ -39,7 +39,7 @@ See [Supported Resources](https://cloud.google.com/app-hub/docs/supported-resour
 
 ## Service
 
-<!-- semconv resource.gcp.apphub.service -->
+<!-- semconv entity.gcp.apphub.service -->
 <!-- NOTE: THIS TEXT IS AUTOGENERATED. DO NOT EDIT BY HAND. -->
 <!-- see templates/registry/markdown/snippet.md.j2 -->
 <!-- prettier-ignore-start -->
@@ -92,7 +92,7 @@ See [Supported Resources](https://cloud.google.com/app-hub/docs/supported-resour
 
 ## Workload
 
-<!-- semconv resource.gcp.apphub.workload -->
+<!-- semconv entity.gcp.apphub.workload -->
 <!-- NOTE: THIS TEXT IS AUTOGENERATED. DO NOT EDIT BY HAND. -->
 <!-- see templates/registry/markdown/snippet.md.j2 -->
 <!-- prettier-ignore-start -->