Merge branch 'main' into zero-code

.cspell.yml

@@ -5,6 +5,7 @@ version: '0.2'
 language: en-US
 import:
   - '@cspell/dict-es-es/cspell-ext.json'
+  - '@cspell/dict-fr-fr/cspell-ext.json'
   - '@cspell/dict-pt-br/cspell-ext.json'
 caseSensitive: true
 ignorePaths:
@@ -31,6 +32,8 @@ dictionaryDefinitions:
     path: .cspell/en-words.txt
   - name: es-palabras
     path: .cspell/es-palabras.txt
+  - name: fr-mots
+    path: .cspell/fr-mots.txt
   - name: pt-palavras
     path: .cspell/pt-palavras.txt
 dictionaries:
@@ -40,6 +43,7 @@ dictionaries:
   # Local word lists
   - en-words
   - es-palabras
+  - fr-mots
   - pt-palavras
   # Programming languages and software terms
   - cpp

.cspell/es-palabras.txt

@@ -1,2 +1,15 @@
 observabilidad
-telemetría
+telemetría
+inicialización
+configurarlo
+correlacionan
+microservicios
+extensibilidad
+correlacionarse
+deserializa
+proprietarias
+aspiracional
+deserializar
+Muestreadores
+muestreadores
+monitoreo

.cspell/fr-mots.txt

@@ -0,0 +1,49 @@
+analyse
+analyser
+avec
+collecter
+collectez
+comportement
+contenant
+créez
+dans
+découvrez
+définie
+démo
+dessous
+données
+d'utiliser
+efficace
+entièrement
+être
+générer
+gratuit
+indépendant
+instrumenter
+intégrations
+langages
+librairies
+logiciels
+métriques
+nombreux
+nombreuses
+observabilité
+outils
+permet
+permettant
+projet
+projets
+peut
+qualité
+savoir
+s'intègre
+supporte
+supporté
+tant
+télémétrie
+transmettez
+universelle
+utilisé
+visuel
+votre
+vous

.cspell/pt-palavras.txt

@@ -1,5 +1,6 @@
 desserializa
+desserializar
 autoinstrumentação
 autoconsistentes
 serialização
-verbosidade
+verbosidade

.github/component-label-map.yml

@@ -22,6 +22,10 @@ lang:es:
   - changed-files:
       - any-glob-to-any-file:
           - content/es/**
+lang:fr:
+  - changed-files:
+      - any-glob-to-any-file:
+          - content/fr/**
 sig:cpp:
   - changed-files:
       - any-glob-to-any-file:

.github/component-owners.yml

@@ -80,3 +80,6 @@ components:
   content/es:
     - open-telemetry/docs-maintainers
     - open-telemetry/docs-es-approvers
+  content/fr:
+    - open-telemetry/docs-maintainers
+    - open-telemetry/docs-fr-approvers

.gitmodules

@@ -7,7 +7,7 @@
 [submodule "content-modules/opentelemetry-specification"]
 	path = content-modules/opentelemetry-specification
 	url = https://github.com/open-telemetry/opentelemetry-specification.git
-	spec-pin = v1.37.0
+	spec-pin = v1.38.0
 [submodule "content-modules/community"]
 	path = content-modules/community
 	url = https://github.com/open-telemetry/community
@@ -19,7 +19,7 @@
 [submodule "content-modules/semantic-conventions"]
 	path = content-modules/semantic-conventions
 	url = https://github.com/open-telemetry/semantic-conventions
-	semconv-pin = v1.27.0
+	semconv-pin = v1.28.0
 [submodule "content-modules/opamp-spec"]
 	path = content-modules/opamp-spec
 	url = https://github.com/open-telemetry/opamp-spec

.htmltest.yml

@@ -36,6 +36,7 @@ IgnoreURLs: # list of regexs of paths or URLs to be ignored
   - ^https://(www\.|eng\.)?uber\.com/(blog|flipr)/ # 406
   - ^https://kofo.dev
   - ^https://platform.openai.com
+  - ^https://openai.com
   - ^https://star-history.com
   - ^https://twitter.com
   - ^https://www.chathamhouse.org

README.md

@@ -4,6 +4,8 @@ This is the source repository for the [OpenTelemetry][] website, project
 documentation, and blog. The site is [built][contributing.md] using [Hugo][] and
 is hosted on [Netlify][].
 
+Public analytics for the website is [available here][].
+
 ## Get involved
 
 To learn how to contribute fixes and new content to this project, read the
@@ -101,3 +103,5 @@ contributed][contributors]!
 [slack]: https://slack.cncf.io/
 [hugo]: https://gohugo.io
 [netlify]: https://netlify.com
+[available here]:
+  https://lookerstudio.google.com/reporting/34c2a65a-39e8-44aa-afa0-094975fee55d/page/4VDGB

content/en/blog/2024/gc-candidates.md

@@ -0,0 +1,36 @@
+---
+title:
+  Announcing the 2024 OpenTelemetry Governance Committee Election Candidates
+linkTitle: 2024 GC Candidates
+date: 2024-10-15
+author: OpenTelemetry Governance Committee
+cSpell:ignore: Baeyens Danielson Marylia
+---
+
+The OpenTelemetry election committee is excited to announce the final list of
+candidates for the upcoming 2024 OpenTelemetry Governance Committee Election!
+
+If you are an
+[eligible voter](https://github.com/open-telemetry/community/blob/main/elections/2024/governance-committee-election.md#voter-eligibility),
+you’ll have the opportunity to continue shaping the future of OpenTelemetry by
+casting your vote between 21 October 2024 00:00 UTC and 23 October 2024 23:59
+UTC. You'll be selecting your preferred candidates to fill the four available
+seats in this year's election.
+
+You can find the candidates' pictures, profile link, and descriptions on the
+[candidates page](https://github.com/open-telemetry/community/blob/main/elections/2024/governance-committee-candidates.md).
+Here are their names:
+
+- Adriana Villela
+- Alolita Sharma
+- Daniel Dyla
+- Jamie Danielson
+- Marylia Gutierrez
+- Morgan McLean
+- Pablo Baeyens Fernández
+- Trask Stalnaker
+
+You can check your eligibility by reviewing
+[this GitHub issue](https://github.com/open-telemetry/community/issues/2329). If
+you are not listed there but believe you have the right to vote, kindly
+[fill out this registration form](https://forms.gle/LBvyRpNwZvqcJxUbA).

content/en/blog/2024/prom-and-otel/index.md

@@ -130,7 +130,7 @@ endpoint. Note that
 The Prometheus exporter allows you to ship data in the Prometheus format, which
 is then scraped by a Prometheus server. It's used to report metrics via the
 Prometheus scrape HTTP endpoint. You can learn more by trying out this
-[example](https://github.com/open-telemetry/opentelemetry-go/tree/main/example/prometheus).
+[example](https://github.com/open-telemetry/opentelemetry-go-contrib/tree/main/examples/prometheus).
 However, the scraping won't really scale, as all the metrics are sent in a
 single scrape.
 

content/en/docs/collector/_index.md

@@ -3,7 +3,7 @@ title: Collector
 description: Vendor-agnostic way to receive, process and export telemetry data.
 aliases: [collector/about]
 cascade:
-  vers: 0.110.0
+  vers: 0.111.0
 weight: 270
 ---
 

content/en/docs/collector/architecture.md

@@ -34,8 +34,8 @@ processing (or modification), and finally to export.
 Pipelines can operate on three telemetry data types: traces, metrics, and logs.
 The data type is a property of the pipeline defined by its configuration.
 Receivers, processors, and exporters used in a pipeline must support the
-particular data type, otherwise the `ErrDataTypeIsNotSupported` exception is
-reported when the configuration loads.
+particular data type, otherwise the `pipeline.ErrSignalNotSupported` exception
+is reported when the configuration loads.
 
 The following diagram represents a typical pipeline:
 

content/en/docs/collector/building/receiver.md

@@ -520,8 +520,8 @@ func createTracesReceiver(_ context.Context, params receiver.CreateSettings, bas
 ```
 
 You now have all the necessary components to successfully instantiate your
-receiver factory using the `receiver.NewFactory` function. Go ahead and and
-update your `NewFactory()` function in your `factory.go` file as follow:
+receiver factory using the `receiver.NewFactory` function. Go ahead and update
+your `NewFactory()` function in your `factory.go` file as follows:
 
 ```go
 // NewFactory creates a factory for tailtracer receiver.

content/en/docs/collector/custom-collector.md

@@ -164,6 +164,13 @@ processors:
 receivers:
   - gomod:
       go.opentelemetry.io/collector/receiver/otlpreceiver {{% version-from-registry collector-receiver-otlp %}}
+
+providers:
+  - gomod: go.opentelemetry.io/collector/confmap/provider/envprovider v1.17.0
+  - gomod: go.opentelemetry.io/collector/confmap/provider/fileprovider v1.17.0
+  - gomod: go.opentelemetry.io/collector/confmap/provider/httpprovider v1.17.0
+  - gomod: go.opentelemetry.io/collector/confmap/provider/httpsprovider v1.17.0
+  - gomod: go.opentelemetry.io/collector/confmap/provider/yamlprovider v1.17.0
 ```
 
 {{% alert color="primary" title="Tip" %}}

content/en/docs/collector/internal-telemetry.md

@@ -36,11 +36,11 @@ service:
   telemetry:
     metrics:
       readers:
-        pull:
-          exporter:
-            prometheus:
-              host: '0.0.0.0'
-              port: 8888
+        - pull:
+            exporter:
+              prometheus:
+                host: '0.0.0.0'
+                port: 8888
 ```
 
 You can adjust the verbosity of the Collector metrics output by setting the

content/en/docs/concepts/glossary.md

@@ -358,4 +358,4 @@ on web pages when requested. See [more][zpages].
 [trace]: /docs/specs/otel/overview#traces
 [tracer]: /docs/specs/otel/trace/api#tracer
 [zpages]:
-  https://github.com/open-telemetry/opentelemetry-specification/blob/main/experimental/trace/zpages.md
+  https://github.com/open-telemetry/opentelemetry-specification/blob/main/development/trace/zpages.md

content/en/docs/concepts/signals/traces.md

@@ -26,8 +26,8 @@ verbose.
 {
   "name": "hello",
   "context": {
-    "trace_id": "0x5b8aa5a2d2c872e8321cf37308d69df2",
-    "span_id": "0x051581bf3cb55c13"
+    "trace_id": "5b8aa5a2d2c872e8321cf37308d69df2",
+    "span_id": "051581bf3cb55c13"
   },
   "parent_id": null,
   "start_time": "2022-04-29T18:52:58.114201Z",
@@ -57,10 +57,10 @@ Note that it has a `trace_id` field indicating the trace, but has no
 {
   "name": "hello-greetings",
   "context": {
-    "trace_id": "0x5b8aa5a2d2c872e8321cf37308d69df2",
-    "span_id": "0x5fb397be34d26b51"
+    "trace_id": "5b8aa5a2d2c872e8321cf37308d69df2",
+    "span_id": "5fb397be34d26b51"
   },
-  "parent_id": "0x051581bf3cb55c13",
+  "parent_id": "051581bf3cb55c13",
   "start_time": "2022-04-29T18:52:58.114304Z",
   "end_time": "2022-04-29T22:52:58.114561Z",
   "attributes": {
@@ -96,10 +96,10 @@ that matches the `span_id` of the `hello` span.
 {
   "name": "hello-salutations",
   "context": {
-    "trace_id": "0x5b8aa5a2d2c872e8321cf37308d69df2",
-    "span_id": "0x93564f51e1abe1c2"
+    "trace_id": "5b8aa5a2d2c872e8321cf37308d69df2",
+    "span_id": "93564f51e1abe1c2"
   },
-  "parent_id": "0x051581bf3cb55c13",
+  "parent_id": "051581bf3cb55c13",
   "start_time": "2022-04-29T18:52:58.114492Z",
   "end_time": "2022-04-29T18:52:58.114631Z",
   "attributes": {

content/en/docs/contributing/issues.md

@@ -29,7 +29,8 @@ One of the best ways to help make OTel docs better is to fix an existing issue.
    <!-- prettier-ignore -->
    > **NOTE**: we **_do not_ assign issues** to those who
    > have not already made contributions to the [OpenTelemetry
-   > organization][org].
+   > organization][org], unless part of a mentorship or onboarding
+   > process.
    {.mt-3}
 
    <!-- prettier-ignore -->

content/en/docs/demo/architecture.md

@@ -129,7 +129,7 @@ subgraph tdf[Telemetry Data Flow]
         subgraph oc[OTel Collector]
             style oc fill:#97aef3,color:black;
             oc-grpc[/"OTLP Receiver<br/>listening on<br/>grpc://localhost:4317"/]
-            oc-http[/"OTLP Receiver<br/>listening on <br/>localhost:4318<br/>localhost:4318"/]
+            oc-http[/"OTLP Receiver<br/>listening on <br/>localhost:4318<br/>"/]
             oc-proc(Processors)
             oc-prom[/"OTLP HTTP Exporter"/]
             oc-otlp[/"OTLP Exporter"/]

content/en/docs/kubernetes/collector/components.md

@@ -554,7 +554,7 @@ started.
 
 For objects configuring for pulling, the receiver will use the Kubernetes API to
 periodically list all the objects in the Cluster. Each object will be converted
-to its own log. For objects configured for watching, the receiver creates a a
+to its own log. For objects configured for watching, the receiver creates a
 stream with the Kubernetes API and which receives updates as the objects change.
 
 To see which objects are available for collection run in your cluster run

content/en/docs/kubernetes/operator/automatic.md

@@ -428,9 +428,16 @@ spec:
           instrumentation>
 ```
 
+See the
+[Python agent configuration docs](/docs/zero-code/python/configuration/#disabling-specific-instrumentations)
+for more details.
+
 #### Learn more {#python-learn-more}
 
-[See the Python agent Configuration docs for more details.](/docs/zero-code/python/configuration/#disabling-specific-instrumentations)
+For Python-specific quirks, see
+[Python OpenTelemetry Operator docs](/docs/zero-code/python/operator/#python-specific-topics)
+and the
+[Python agent configuration docs](/docs/zero-code/python/configuration/).
 
 ### Go
 

content/en/docs/languages/erlang/propagation.md

@@ -25,7 +25,7 @@ propagators. By default the global propagators used are the W3C
 [Trace Context](https://w3c.github.io/trace-context/) and
 [Baggage](https://www.w3.org/TR/baggage/) formats.
 
-You can configure global propagators using the the OTP application environment
+You can configure global propagators using the OTP application environment
 variable `text_map_propagators`:
 
 {{< tabpane text=true >}} {{% tab Erlang %}}

content/en/docs/languages/go/examples.md

@@ -1,6 +1,6 @@
 ---
 title: Examples
-redirect: https://github.com/open-telemetry/opentelemetry-go/tree/main/example
+redirect: https://github.com/open-telemetry/opentelemetry-go-contrib/tree/main/examples
 manualLinkTarget: _blank
 _build: { render: link }
 weight: 220

content/en/docs/languages/go/exporters.md

@@ -200,7 +200,7 @@ func newExporter(ctx context.Context) (metric.Reader, error) {
 ```
 
 To learn more on how to use the Prometheus exporter, try the
-[prometheus example](https://github.com/open-telemetry/opentelemetry-go/tree/main/example/prometheus)
+[prometheus example](https://github.com/open-telemetry/opentelemetry-go-contrib/tree/main/examples/prometheus)
 
 ### OTLP logs over HTTP (Experimental)