Merge branch 'main' into MSNev/EventModel

.chloggen/627.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: rpc
+
+# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Add link to specification for metrics defined by gRPC community.
+
+# 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: [627]
+
+# (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:

.chloggen/698.yaml

@@ -0,0 +1,7 @@
+change_type: breaking
+
+component: messaging
+
+note: Remove `network.transport` and `network.type` attributes from messaging semantic conventions, clarify when `network.peer.address|port` should be populated.
+
+issues: [690, 698]

.chloggen/738.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: db
+
+# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Update Elasticsearch attributes to use db.instance.id instead of db.elasticsearch.node.name
+
+# 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: [725]
+
+# (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:

.chloggen/817.yaml

@@ -0,0 +1,4 @@
+change_type: bug_fix
+component: network
+note: Clarifies that network.protocol.version represents negotiated version
+issues: [ 686 ]

.chloggen/add_new_container_metrics.yaml

@@ -0,0 +1,21 @@
+# 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: "container"
+
+# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: "Add new container metrics for `cpu`, `memory`, `disk` and `network`"
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+issues: [282, 72]
+
+# (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:

.chloggen/file.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: new_component
+
+# The name of the area of concern in the attributes-registry, (e.g. http, cloud, db)
+component: file
+
+# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Add new file namespace
+
+# 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: [732]
+
+# (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:

.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -0,0 +1,84 @@
+name: Bug report
+description: Create a report to help us improve
+labels: ["bug", "triage:needs-triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report! Please make sure to fill out the entire form below, providing as much context as you can in order to help us triage and track down your bug as quickly as possible.
+
+        Before filing a bug, please be sure you have searched through [existing bugs](https://github.com/open-telemetry/semantic-conventions/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3Abug) to see if an existing issue covers your bug.
+  - type: dropdown
+    id: area
+    attributes:
+      label: Area(s)
+      description: Which area(s) does your bug report concern? If none fits, please select `area:other`
+      multiple: true
+      options:
+        - area:other
+        # NOTE: The list below is autogenerated using `make generate-gh-issue-templates`
+        # DO NOT manually edit it.
+        # Start semconv area list
+        - area:android
+        - area:browser
+        - area:client
+        - area:cloud
+        - area:cloudevents
+        - area:code
+        - area:container
+        - area:db
+        - area:deployment
+        - area:destination
+        - area:device
+        - area:disk
+        - area:dns
+        - area:enduser
+        - area:error
+        - area:exception
+        - area:faas
+        - area:feature-flag
+        - area:file
+        - area:gcp-cloud-run
+        - area:gcp-gce
+        - area:host
+        - area:http
+        - area:k8s
+        - area:messaging
+        - area:network
+        - area:oci
+        - area:os
+        - area:process
+        - area:rpc
+        - area:server
+        - area:source
+        - area:thread
+        - area:tls
+        - area:url
+        - area:user-agent
+        # End semconv area list
+  - type: textarea
+    attributes:
+      label: What happened?
+      description: Please provide as much detail as you reasonably can.
+      value: |
+        ## Description
+
+        ## Steps to Reproduce (if any)
+
+        ## Expected Result
+
+        ## Actual Result
+    validations:
+      required: true
+
+  - type: input
+    attributes:
+      label: Semantic convention version
+      description: What version did you use? (e.g., `v1.24.0`, `1eb551b`, etc)
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Additional context
+      description: Any additional information you think may be relevant to this issue.

.github/ISSUE_TEMPLATE/change_proposal.yaml

@@ -0,0 +1,71 @@
+name: Propose changes to existing conventions
+description: Propose changes you'd like to be added to existing conventions
+labels: ["enhancement", "triage:needs-triage"]
+body:
+  - type: dropdown
+    id: area
+    attributes:
+      label: Area(s)
+      description: Which area(s) does your change request concern?
+      multiple: true
+      options:
+        # NOTE: The list below is autogenerated using `make generate-gh-issue-templates`
+        # DO NOT manually edit it.
+        # Start semconv area list
+        - area:android
+        - area:browser
+        - area:client
+        - area:cloud
+        - area:cloudevents
+        - area:code
+        - area:container
+        - area:db
+        - area:deployment
+        - area:destination
+        - area:device
+        - area:disk
+        - area:dns
+        - area:enduser
+        - area:error
+        - area:exception
+        - area:faas
+        - area:feature-flag
+        - area:file
+        - area:gcp-cloud-run
+        - area:gcp-gce
+        - area:host
+        - area:http
+        - area:k8s
+        - area:messaging
+        - area:network
+        - area:oci
+        - area:os
+        - area:process
+        - area:rpc
+        - area:server
+        - area:source
+        - area:thread
+        - area:tls
+        - area:url
+        - area:user-agent
+        # End semconv area list
+  - type: textarea
+    attributes:
+      label: Is your change request related to a problem? Please describe.
+      description: A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Describe the solution you'd like
+      description: A clear and concise description of what you want to happen.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Describe alternatives you've considered
+      description: A clear and concise description of any alternative solutions or features you've considered.
+  - type: textarea
+    attributes:
+      label: Additional context
+      description: Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/new-conventions.yaml

@@ -0,0 +1,80 @@
+name: Propose new semantic conventions
+description: Propose new conventions you'd like to be part of the OpenTelemetry project
+labels: ["enhancement", "triage:needs-triage", "experts needed"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Please make sure to fill out the entire form below, providing as much context as you can in order to help us triage the proposal as quickly as possible.
+
+        Before filing the proposal, please be sure you have searched through [existing issues](https://github.com/open-telemetry/semantic-conventions/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3Aenhancement+label%3Aarea:new) to see if an existing issue covers your proposal.
+
+        Additionally, make sure to read and follow the guidelines on [Project Proposal](https://github.com/open-telemetry/community/blob/main/project-management.md#project-management), in case the proposal is for a new set of conventions/working group.
+  - type: dropdown
+    id: area
+    attributes:
+      label: Area(s)
+      description: Which area(s) does your new conventions concern? If none fits, please select `area:new`
+      multiple: true
+      options:
+        - area:new
+        # NOTE: The list below is autogenerated using `make generate-gh-issue-templates`
+        # DO NOT manually edit it.
+        # Start semconv area list
+        - area:android
+        - area:browser
+        - area:client
+        - area:cloud
+        - area:cloudevents
+        - area:code
+        - area:container
+        - area:db
+        - area:deployment
+        - area:destination
+        - area:device
+        - area:disk
+        - area:dns
+        - area:enduser
+        - area:error
+        - area:exception
+        - area:faas
+        - area:feature-flag
+        - area:file
+        - area:gcp-cloud-run
+        - area:gcp-gce
+        - area:host
+        - area:http
+        - area:k8s
+        - area:messaging
+        - area:network
+        - area:oci
+        - area:os
+        - area:process
+        - area:rpc
+        - area:server
+        - area:source
+        - area:thread
+        - area:tls
+        - area:url
+        - area:user-agent
+        # End semconv area list
+  - type: textarea
+    attributes:
+      label: Is your change request related to a problem? Please describe.
+      description: A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Describe the solution you'd like
+      description: A clear and concise description of what you want to happen.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Describe alternatives you've considered
+      description: A clear and concise description of any alternative solutions or features you've considered.
+  - type: textarea
+    attributes:
+      label: Additional context
+      description: Add any other context or screenshots about the feature request here.

.github/workflows/checks.yml

@@ -97,3 +97,12 @@ jobs:
     - uses: actions/checkout@v1
     - name: verify schemas
       run: make schema-check
+
+  areas-dropdown-check:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v1
+    - name: Components dropdown in issue templates
+      run: |
+        make generate-gh-issue-templates
+        git diff --exit-code '.github/ISSUE_TEMPLATE' || (echo 'Dropdowns in issue templates is out of date, please run "make generate-gh-issue-templates" and commit the changes in this PR.' && exit 1)

.github/workflows/generate-registry-area-labels.yml

@@ -0,0 +1,24 @@
+name: 'Generate registry area labels'
+on:
+  push:
+    branches: [main]
+    paths:
+      - model/registry/**
+      - ./.github/workflows/generate-registry-area-labels.yml
+      - ./.github/workflows/scripts/generate-registry-area-labels.sh
+  workflow_dispatch:
+
+jobs:
+  generate-component-labels:
+    runs-on: ubuntu-latest
+    if: ${{ github.repository_owner == 'open-telemetry' }}
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Run update permissions
+        run: chmod +x ./.github/workflows/scripts/generate-registry-area-labels.sh
+
+      - name: Generate registry area labels
+        run: ./.github/workflows/scripts/generate-registry-area-labels.sh
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}