Merge branch 'main' into chore/localize-exporter-of-concepts

.cspell/en-words.txt

@@ -111,7 +111,6 @@ quoteservice
 react-native-app
 recommendationservice
 redis
-relref
 Rexed
 runbook
 runbooks

.github/workflows/auto-update-community-members.yml

@@ -10,7 +10,7 @@ jobs:
   auto-update-versions:
     name: Auto-update community members page
     runs-on: ubuntu-24.04
-    # Remove the if statement below when testing againt a fork
+    # Remove the if statement below when testing against a fork
     if: github.repository == 'open-telemetry/opentelemetry.io'
     steps:
       - name: Checkout

.github/workflows/auto-update-registry.yml

@@ -10,7 +10,7 @@ jobs:
   auto-update-versions:
     name: Auto-update registry versions
     runs-on: ubuntu-20.04
-    # Remove the if statement below when testing againt a fork
+    # Remove the if statement below when testing against a fork
     if: github.repository == 'open-telemetry/opentelemetry.io'
     steps:
       - name: Checkout

.github/workflows/build-dev.yml

@@ -7,6 +7,11 @@ on:
         description: Regex of submodule paths to update to HEAD before building.
         default: content-modules
         type: string
+  workflow_call:
+    inputs:
+      submodule_path_regex:
+        type: string
+        required: true
 
 jobs:
   build-and-test:

.github/workflows/build-semconv-daily.yml

@@ -0,0 +1,25 @@
+name: Build Semantic Conventions (daily)
+
+on:
+  schedule:
+    # daily at 10:24 UTC
+    - cron: '24 10 * * *'
+  workflow_dispatch:
+
+jobs:
+  build-dev:
+    uses: ./.github/workflows/build-dev.yml
+    with:
+      submodule_path_regex: semantic-conventions
+
+  workflow-notification:
+    needs:
+      - build-dev
+    if: always()
+    uses: ./.github/workflows/reusable-workflow-notification.yml
+    with:
+      success: ${{ needs.build-dev.result == 'success' }}
+      repo: open-telemetry/semantic-conventions
+    secrets:
+      opentelemetrybot_github_token:
+        ${{ secrets.OPENTELEMETRYBOT_GITHUB_TOKEN }}

.github/workflows/component-owners.yml

@@ -10,6 +10,7 @@ jobs:
       contents: read
       issues: write
       pull-requests: write
+    if: github.repository_owner == 'open-telemetry'
     steps:
       - uses: dyladan/[email protected]
         with:

.github/workflows/reusable-workflow-notification.yml

@@ -0,0 +1,60 @@
+# this is useful because notifications for scheduled workflows are only sent to the user who
+# initially created the given workflow
+name: Reusable - Workflow notification
+
+on:
+  workflow_call:
+    inputs:
+      success:
+        type: boolean
+        required: true
+      repo:
+        type: string
+        required: false
+    secrets:
+      opentelemetrybot_github_token:
+        type: string
+        required: false
+
+jobs:
+  workflow-notification:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Open issue or add comment if issue already open
+        env:
+          # need to use opentelemetrybot token when opening issues in other repos
+          GH_TOKEN:
+            ${{ secrets.opentelemetrybot_github_token || secrets.GITHUB_TOKEN }}
+        run: |
+          if [ -z "${{ inputs.repo }}" ]; then
+            repo="$GITHUB_REPOSITORY"
+            title="Workflow failed: $GITHUB_WORKFLOW"
+            body="See [$GITHUB_WORKFLOW #$GITHUB_RUN_NUMBER](https://github.com/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID)."
+          else
+            repo="${{ inputs.repo }}"
+            title="Workflow failed: $GITHUB_REPOSITORY $GITHUB_WORKFLOW"
+            body="See [$GITHUB_REPOSITORY $GITHUB_WORKFLOW #$GITHUB_RUN_NUMBER](https://github.com/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID)."
+          fi
+
+          # TODO (trask) search doesn't support exact phrases, so it's possible that this could grab the wrong issue
+          number=$(gh issue list --repo $repo --search "in:title $title" --limit 1 --json number -q .[].number)
+
+          echo $number
+          echo ${{ inputs.success }}
+
+          if [[ $number ]]; then
+            if [[ "${{ inputs.success }}" == "true" ]]; then
+              gh issue close $number \
+                             --repo $repo
+            else
+              gh issue comment $number \
+                               --repo $repo \
+                               --body "$body"
+            fi
+          elif [[ "${{ inputs.success }}" == "false" ]]; then
+            gh issue create --repo $repo \
+                            --title "$title (#$GITHUB_RUN_NUMBER)" \
+                            --body "$body"
+          fi

.github/workflows/scripts/check-i18n-helper.sh

@@ -5,7 +5,7 @@ echo "For localization docs, see https://opentelemetry.io/docs/contributing/loca
 CHANGES=`git status --porcelain`
 
 if [[ -z $CHANGES ]]; then
-  echo "All localization pages have the requisit commit hash. <3"
+  echo "All localization pages have the requisite commit hash. <3"
   exit;
 fi
 

.gitmodules

@@ -2,13 +2,13 @@
 [submodule "themes/docsy"]
 	path = themes/docsy
 	url = https://github.com/google/docsy.git
-	docsy-pin = v0.11.0-32-ge6d94771
+	docsy-pin = v0.11.0-34-gef59ee75
 	docsy-note = "2024-04-01 Switching to google/docsy.git from cncf/docsy.git since we don't have any CNCF customizations."
 	docsy-reminder = "Ensure that any tag referenced by `docsy-pin` is present in the remote repo (url), otherwise add (push) the tags to the repo."
 [submodule "content-modules/opentelemetry-specification"]
 	path = content-modules/opentelemetry-specification
 	url = https://github.com/open-telemetry/opentelemetry-specification.git
-	spec-pin = v1.40.0
+	spec-pin = v1.41.0
 [submodule "content-modules/community"]
 	path = content-modules/community
 	url = https://github.com/open-telemetry/community

content/en/_index.md

@@ -5,7 +5,9 @@ description: >-
   observability
 outputs:
   - HTML
-  - REDIRECTS # Include this `content/en` ONLY
+  # Include the following for `content/en` ONLY
+  - REDIRECTS
+  - RSS
 developer_note:
   The blocks/cover shortcode (used below) will use as a background image any
   image file containing "background" in its name.

content/en/blog/2022/announcing-opentelemetry-demo-release/index.md

@@ -14,7 +14,7 @@ announce
 With this demo, you’ll be able to quickly run a complete end-to-end distributed
 system instrumented with 100% OpenTelemetry Traces and Metrics.
 
-![The system architecture of the demo application represented as directed acyclic graph in Jaeger UI](sytem-architecture.png)
+![The system architecture of the demo application represented as directed acyclic graph in Jaeger UI](system-architecture.png)
 
 One of our primary goals of this project has been to create a robust sample
 application for developers to use in learning OpenTelemetry, and we’re proud to

content/en/blog/2022/demo-announcement/index.md

@@ -7,7 +7,7 @@ author: '[Carter Socha](https://github.com/cartersocha)'
 
 ## TL;DR
 
-The OpenTelemetry community has taken a good pre-existing demo (thanks,
+The OpenTelemetry community has taken a good preexisting demo (thanks,
 [Google](https://github.com/GoogleCloudPlatform/microservices-demo)!) and is in
 the process of making it even better. Every GA SDK (besides Swift) will be
 represented, demo support will be extended to Metrics and Logs, and canonical
@@ -66,8 +66,8 @@ backend choice, and they’re overly reliant on instrumentation libraries.
 As a starting point, we have selected a fork of the popular GCP microservices
 demo. Our first feature additions have been to simplify local deployment by
 consolidating the project onto a single docker compose file, updating the
-documentation, and replacing a pre-existing service with a Ruby example.
-Otherwise the pre-existing feature set from the GCP demo remains the same:
+documentation, and replacing a preexisting service with a Ruby example.
+Otherwise the preexisting feature set from the GCP demo remains the same:
 
 - 10 application microservice with support for 6 languages (C#, Go, Java,
   Node.js, Python, and Ruby)

content/en/blog/2023/exponential-histograms.md

@@ -190,12 +190,13 @@ OpenTelemetry’s Exponential Histograms in Prometheus][]
 
 _A version of this article was [originally posted][] to the author's blog._
 
-<!-- prettier-ignore-start -->
 [Using OpenTelemetry’s Exponential Histograms in Prometheus]:
   https://www.youtube.com/watch?v=W2_TpDcess8
-[OTEP 149]: https://github.com/open-telemetry/oteps/blob/976c9395e4cbb3ea933d3b51589eba94b87a17bd/text/0149-exponential-histogram.md
-[specification for exponential histogram aggregations]: /docs/specs/otel/metrics/sdk/#base2-exponential-bucket-histogram-aggregation
-[Why Histograms?]: {{% relref "why-histograms" %}}
-[Histograms vs Summaries]: {{% relref "histograms-vs-summaries" %}}
+[OTEP 149]:
+  https://github.com/open-telemetry/oteps/blob/976c9395e4cbb3ea933d3b51589eba94b87a17bd/text/0149-exponential-histogram.md
+[specification for exponential histogram aggregations]:
+  /docs/specs/otel/metrics/sdk/#base2-exponential-bucket-histogram-aggregation
+[Why Histograms?]: ../why-histograms/
+[Histograms vs Summaries]: ../histograms-vs-summaries/
+
 [originally posted]: {{% param canonical_url %}}
-<!-- prettier-ignore-end -->

content/en/blog/2023/histograms-vs-summaries/index.md

@@ -3,7 +3,7 @@ title: Histograms vs Summaries
 date: 2023-05-15
 author: '[Daniel Dyla](https://github.com/dyladan)'
 canonical_url: https://dyladan.me/histograms/2023/05/03/histograms-vs-summaries/
-cSpell:ignore: aggregatable Björn Ganesh Kovalov Rabenstein Ruslan Vernekar
+cSpell:ignore: aggregable Björn Ganesh Kovalov Rabenstein Ruslan Vernekar
 ---
 
 In many ways, histograms and summaries appear quite similar. They both roll up
@@ -34,9 +34,9 @@ could be off by as much as 60ms (`360 - 300`), a relative error of 17%
 (`60 / 360`). This error can be mitigated by configuring more and smaller
 buckets around your SLO values, but never eliminated.
 
-One important property of histograms is that they are _aggregatable_, meaning
-that as long as the bucket boundaries line up, an arbitrary number of histograms
-can be combined into a single histogram with no loss of data or precision. This
+One important property of histograms is that they are _aggregable_, meaning that
+as long as the bucket boundaries line up, an arbitrary number of histograms can
+be combined into a single histogram with no loss of data or precision. This
 means that an arbitrary number of hosts can report histogram data structures to
 a server, which can aggregate and compute quantiles from all of them as if they
 were reported by a single host. By collecting histograms from 1 or more hosts

content/en/blog/2023/humans-of-otel.md

@@ -4,7 +4,7 @@ linkTitle: Humans of OTel
 date: 2023-12-22
 author: '[Adriana Villela](https://github.com/avillela) (Lightstep)'
 # prettier-ignore
-cSpell:ignore: adiana alex aronoff bogdan boten caramanolis constance dapr drutu jacob juraci kanal kröhling paixāo purvi tyler utopic villela yahn youtube
+cSpell:ignore: alex aronoff bogdan boten caramanolis constance dapr drutu jacob juraci kanal kröhling paixāo purvi tyler utopic villela yahn youtube
 ---
 
 What a year it has been for OpenTelemetry!

content/en/blog/2023/lambda-release.md

@@ -21,7 +21,7 @@ had a
 and they've been available on AWS for years.
 
 You're totally correct. Rest assured, we're not reinventing the wheel. However,
-there are some pre-existing problems that may impact users:
+there are some preexisting problems that may impact users:
 
 - The OTel Lambda layers were only released as part of the
   [AWS Distribution for OTel (ADOT)](https://aws-otel.github.io/), and the

content/en/blog/2023/otel-in-focus-09.md

@@ -4,7 +4,7 @@ linkTitle: OTel in Focus 2023/09
 date: 2023-10-01
 author: '[Austin Parker](https://github.com/austinlparker)'
 # prettier-ignore
-cSpell:ignore: attributesprocessor Autoscaler checkapi Contribfest coreinternal gopkg jaegerthrifthttp obsreport ottl resourcedetection resourceprocessor structs tailsampling ucum unmanaged
+cSpell:ignore: attributesprocessor Autoscaler checkapi Contribfest coreinternal jaegerthrifthttp obsreport ottl resourcedetection resourceprocessor structs tailsampling ucum unmanaged
 ---
 
 Welcome back to **OpenTelemetry in Focus** for September, 2023! The autumn winds

content/en/blog/2023/otel-in-focus-10.md

@@ -4,7 +4,7 @@ linkTitle: OTel in Focus 2023/10
 date: 2023-11-01
 author: '[Austin Parker](https://github.com/austinlparker)'
 # prettier-ignore
-cSpell:ignore: Contribfest distro dockerstats dockerstatsreceiver k8sclusterreceiver parquetexporter pdata Pekko receiver resourcetype signalfxexporter splunkhecexporter structs
+cSpell:ignore: Contribfest distro dockerstatsreceiver k8sclusterreceiver parquetexporter pdata Pekko resourcetype signalfxexporter splunkhecexporter structs
 ---
 
 Welcome back to **OpenTelemetry in Focus** for October, 2023! It's been another

content/en/blog/2024/_index.md

@@ -1,5 +1,4 @@
 ---
 title: 2024
 weight: -2024
-outputs: [HTML, RSS]
 ---

content/en/blog/2024/llm-observability.md

@@ -5,7 +5,7 @@ title:
 linkTitle: LLM Observability
 date: 2024-06-04
 author: '[Ishan Jain](https://github.com/ishanjainn) (Grafana)'
-cSpell:ignore: associated chatbots Ishan ishan_jainn ishanjainn Jain llm
+cSpell:ignore: chatbots Ishan ishan_jainn ishanjainn Jain llm
 ---
 
 Large Language Models (LLMs) are really popular right now, especially

content/en/blog/2024/otel-collector-container-log-parser/index.md

@@ -81,7 +81,7 @@ combine them into one at first place:
 
 ```text
 2024-04-06T00:17:10.113242941Z stdout P This is a very very long line th
-2024-04-06T00:17:10.113242941Z stdout P at is really really long and spa
+2024-04-06T00:17:10.113242941Z stdout P at is really, really, long and spa
 2024-04-06T00:17:10.113242941Z stdout F ns across multiple log entries
 ```
 

content/en/blog/2024/otel-generative-ai/index.md

@@ -48,7 +48,7 @@ The [Semantic Conventions for Generative AI](/docs/specs/semconv/gen-ai/) focus
 on capturing insights into AI model behavior through three primary signals:
 [Traces](/docs/concepts/signals/traces/),
 [Metrics](/docs/concepts/signals/metrics/), and
-[Events](/docs/specs/otel/logs/event-api/).
+[Events](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.40.0/specification/logs/event-api.md).
 
 Together, these signals provide a comprehensive monitoring framework, enabling
 better cost management, performance tuning, and request tracing.
@@ -74,13 +74,19 @@ model responses, providing a granular view of model interactions. These insights
 are invaluable for debugging and optimizing AI applications where unexpected
 behaviors may arise.
 
-{{% alert title="Note" color="info" %}} Note that we decided to use
-[events emitted](/docs/specs/otel/logs/api/#emit-an-event) with the
+{{% alert title="Note" color="info" %}}
+
+Note that we decided to use [events emitted] with the
 [Logs API](/docs/specs/otel/logs/api/) specification in the Semantic Conventions
 for Generative AI. Events allows for us to define specific
 [semantic conventions](/docs/specs/semconv/general/events/) for the user prompts
 and model responses that we capture. This addition to the API is in development
-and considered unstable.{{% /alert %}}
+and considered unstable.
+
+[events emitted]:
+  https://github.com/open-telemetry/opentelemetry-specification/blob/v1.40.0/specification/logs/api.md#emit-an-event
+
+{{% /alert %}}
 
 ### Extending Observability with Vendor-Specific Attributes
 

content/en/blog/2024/otel-operator-q-and-a/index.md

@@ -4,9 +4,7 @@ title:
   Operator Q&A
 linkTitle: OTel Operator Q&A
 date: 2024-05-13
-author: >-
-  [Adriana Villela](https://github.com/avillela) (ServiceNow),
-
+author: '[Adriana Villela](https://github.com/avillela) (ServiceNow)'
 canonical_url: https://adri-v.medium.com/81d63addbf92?
 cSpell:ignore: automagically mycollector
 ---

content/en/blog/2024/prometheus-compatibility-survey/index.md

@@ -175,10 +175,10 @@ existing conventions.
 
 For the most part, this feedback aligns with the future plans in the
 OpenTelemetry and Prometheus communities. The OpenTelemetry semantic conventions
-SIG is working on stabilizing conventions for a a wide variety of
-instrumentation. The OpenTelemetry Prometheus interoperability SIG is working on
-incorporating the results of this survey into the compatibility specification.
-The Prometheus community has
+SIG is working on stabilizing conventions for a wide variety of instrumentation.
+The OpenTelemetry Prometheus interoperability SIG is working on incorporating
+the results of this survey into the compatibility specification. The Prometheus
+community has
 [ambitious plans](https://prometheus.io/blog/2024/03/14/commitment-to-opentelemetry/)
 to add support for OpenTelemetry concepts.
 

content/en/blog/2025/_index.md

@@ -1,7 +1,6 @@
 ---
 title: 2025
 weight: -2025
-outputs: [HTML, RSS]
 ---
 
 ## Happy New Year!