Merge branch 'main' into feat/add-doc-pt-libraries

.cspell/en-words.txt

@@ -107,6 +107,8 @@ recommendationservice
 redis
 relref
 Rexed
+runbook
+runbooks
 Rynn
 semconv
 servlet

.cspell/pt-palavras.txt

@@ -1 +1,3 @@
-desserializa
+desserializa
+autoinstrumentação
+autoconsistentes

.github/workflows/pr-actions.yml

@@ -101,9 +101,20 @@ jobs:
         env:
           GH_TOKEN: ${{ secrets.OPENTELEMETRYBOT_GITHUB_TOKEN }}
 
+      - name: Report success and ask to run full checks
+        if: ${{ !failure() && !cancelled() }}
+        run: |
+          gh pr comment $PR_NUM --body "$(cat <<EOF
+          \`fix:${PR_ACTION}\` was [successful]($GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID).
+          ### IMPORTANT: (RE-)RUN \`/fix:all\` to ensure that there are no remaining check issues.
+          EOF
+          )"
+        env:
+          GH_TOKEN: ${{ secrets.OPENTELEMETRYBOT_GITHUB_TOKEN }}
+
       - name: Report an error in the case of failure
         if: ${{ failure() || cancelled() }}
         run: |
-          gh pr comment $PR_NUM -b "fix:${PR_ACTION} run failed, please check $GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID for details"
+          gh pr comment $PR_NUM -b "fix:${PR_ACTION} failed or was cancelled. For details, see $GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID."
         env:
           GH_TOKEN: ${{ secrets.OPENTELEMETRYBOT_GITHUB_TOKEN }}

content/en/blog/2024/demo-skyscanner/index.md

@@ -6,7 +6,7 @@ linkTitle: Skyscanner using OTel Demo
 date: 2024-02-26
 author: >-
   [Jordi Bisbal Ansaldo](https://github.com/jordibisbal8) (Skyscanner)
-cSpell:ignore: Ansaldo Bisbal Jordi runbooks Skyscanner upskilled Yankova
+cSpell:ignore: Ansaldo Bisbal Jordi Skyscanner upskilled Yankova
 ---
 
 At [Skyscanner](https://www.skyscanner.net), as in many organizations, teams

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

@@ -0,0 +1,67 @@
+---
+title: Announcing the 2024 OpenTelemetry Governance Committee Election
+linkTitle: 2024 GC Election
+date: 2024-09-03
+author: OpenTelemetry Governance Committee
+aliases: [gc-elections-2024]
+---
+
+The OpenTelemetry project is excited to announce the 2024 OpenTelemetry
+Governance Committee (GC) election. Nominations are due by 11 October 2024 23:59
+UTC. The list of eligible candidates will be shared on 14 October 2024. Voting
+will take place between 21 October 2024 00:00 UTC and 23 October 2024 23:59 UTC,
+and the final election results will be announced 25 October 2024.
+
+## Vote!
+
+If you are a
+[member of standing](https://github.com/open-telemetry/community/blob/main/governance-charter.md#members-of-standing)
+in the OpenTelemetry community, we invite you to participate with your vote in
+this election to ensure that the community is well-represented in the Governance
+Committee. In this election four people must be elected, each with two-year
+terms.
+
+If you have made contributions to our ecosystem not measured by the automatic
+process, you can [request an exception](https://forms.gle/LBvyRpNwZvqcJxUbA) to
+participate in the election before 23:59 UTC on 18 October 2024. The voter roll
+with all members of standing and approved exceptions will be published by 4
+October 2024 and continuously updated until the exception deadline.
+
+Voting will be open between 21 October 2024 00:00 UTC and 23 October 2024 23:59
+UTC on
+[Helios Voting](https://vote.heliosvoting.org/helios/elections/176e7ca8-647d-11ef-9b9a-2a30e2a223da/view);
+voters will need to sign in with their GitHub account.
+
+To learn more about the election process, read about all the details
+[here](https://github.com/open-telemetry/community/blob/main/elections/2024/governance-committee-election.md).
+
+## Interested in joining the Governance Committee?
+
+If you’ve been working on OpenTelemetry and seeing it grow, or are an end-user
+that wants to help us make OpenTelemetry better, now’s the time to consider
+running for a seat on the Governance Committee. You can read about the
+Governance Committee's role in
+[this blog](/blog/2019/opentelemetry-governance-committee-explained/) post or
+refer to the
+[charter document](https://github.com/open-telemetry/community/blob/master/governance-charter.md).
+You may nominate yourself (or others!) by submitting a Pull Request against the
+[list of candidates](https://github.com/open-telemetry/community/blob/main/elections/2024/governance-committee-candidates.md)
+by 11 October 2024 23:59 UTC — more detailed requirements about the nomination
+and ratification process can be found
+[here](https://github.com/open-telemetry/community/blob/main/elections/2024/governance-committee-election.md).
+
+We would like to thank the GC members who have helped grow OpenTelemetry, and
+invite them to run for re-election if they so choose: Alolita Sharma, Daniel
+Dyla, Morgan McLean, and Trask Stalnaker.
+
+## Questions?
+
+For any election related questions, please file an issue on the
+[community repository](https://github.com/open-telemetry/community/issues)
+tagging the `@open-telemetry/otel-elections` team, email us at
+[[email protected]](mailto:[email protected]),
+or reach out to us on [CNCF Slack](https://slack.cncf.io/) in
+[#opentelemetry](https://cloud-native.slack.com/archives/CJFCJHG4Q) if you have
+an urgent access issue during voting.
+
+See you at the polls!

content/en/blog/2024/go-opentelemetry-io.md

@@ -0,0 +1,83 @@
+---
+title: Planned Migration for go.opentelemetry.io
+date: 2024-08-27
+author: '[Mike Dame](https://github.com/damemi) (Google)'
+body_class: otel-with-contributions-from
+issue: 5086
+sig: Go SIG
+cSpell:ignore: vanityurls Yahn
+---
+
+With contributions from Tyler Yahn and Austin Parker.
+
+## TL;DR
+
+The app that serves requests to [go.opentelemetry.io] will be migrating to a new
+host on September 5, 2024 at approximately 11:00AM Eastern Time. **There are no
+changes required from you**. We are making this announcement because it is
+possible, but unlikely, that there might be downtime during this transition.
+
+## Details
+
+OpenTelemetry is planning to migrate the application that serves all requests
+for `go.opentelemetry.io` to a new host project on September 5, 2024. On this
+date, the current DNS entries for `go.opentelemetry.io` will be updated to point
+to the new host.
+
+This should be a seamless transition, but there is the possibility of downtime
+during this time. The OpenTelemetry engineers will be actively monitoring the
+transition to minimize the risk.
+
+### Affected resources
+
+In the unlikely event of issues, the scope of these planned changes will affect
+Go package downloads for the following domains:
+
+- `go.opentelemetry.io/auto`
+- `go.opentelemetry.io/build-tools`
+- `go.opentelemetry.io/collector-contrib`
+- `go.opentelemetry.io/collector`
+- `go.opentelemetry.io/contrib`
+- `go.opentelemetry.io/otel`
+- `go.opentelemetry.io/proto`
+
+Note that this includes users of any of the following artifacts:
+
+- OpenTelemetry Go language libraries (including Contrib)
+- OpenTelemetry Go Auto-Instrumentation libraries
+- OpenTelemetry Collector libraries (including Contrib)
+- OpenTelemetry Collector Builder.
+
+## What you need to do
+
+**There is no action required from you.** All imports using
+`go.opentelemetry.io` (and submodule paths, for example
+`go.opentelemetry.io/otel`) will continue to work. There are no plans to change
+this.
+
+## What you might notice
+
+There is the possibility of the [go.opentelemetry.io] domain experiencing
+downtime during this transition. If this happens, you might see projects that
+import `go.opentelemetry.io` modules failing to compile.
+
+This could occur due to several factors, including delays in DNS propagation or
+misconfiguration. We will have multiple maintainers working synchronously during
+this time to minimize any downtime that occurs.
+
+If you experience any issues following this transition, please reach out on
+[Slack #otel-go](https://cloud-native.slack.com/archives/C01NPAXACKT) or
+[create an issue](https://github.com/open-telemetry/opentelemetry-go-vanityurls/issues/new)
+over
+[opentelemetry-go-vanityurls](https://github.com/open-telemetry/opentelemetry-go-vanityurls).
+
+## Why are we making this change?
+
+This transition both helps modernize the application serving requests and
+handles an ownership transfer, ensuring that we are able to continue providing
+OpenTelemetry Go packages in a secure and robust manner.
+
+For more details, see
+[the community GitHub issue proposing this change](https://github.com/open-telemetry/community/issues/2260).
+
+[go.opentelemetry.io]: https://go.opentelemetry.io

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.107.0
+  vers: 0.108.0
 weight: 270
 ---
 

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

@@ -26,9 +26,10 @@ get started.
 
 ## Step 1 - Install the builder
 
-The `ocb` binary is available as a downloadable asset from [OpenTelemetry
-Collector releases][releases]. You will find a list of assets named based on OS
-and chipset, so download the one that fits your configuration:
+The `ocb` binary is available as a downloadable asset from OpenTelemetry
+Collector [releases with `cmd/builder` tags][tags]. You will find a list of
+assets named based on OS and chipset, so download the one that fits your
+configuration:
 
 {{< tabpane text=true >}}
 
@@ -223,9 +224,6 @@ Further reading:
 
 [ocb]:
   https://github.com/open-telemetry/opentelemetry-collector/tree/main/cmd/builder
-[releases]:
-  https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/cmd%2Fbuilder%2F{{%
-
-version-from-registry collector-builder %}}
+[tags]: https://github.com/open-telemetry/opentelemetry-collector-releases/tags
 
 [^1]: Prior to v0.86.0 use the `loggingexporter` instead of `debugexporter`.

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

@@ -242,13 +242,13 @@ categorized by instrumentation type.
 | `http_client_active_requests`     | Number of active HTTP client requests.                                                    | Counter   |
 | `http_client_connection_duration` | Measures the duration of the successfully established outbound HTTP connections.          | Histogram |
 | `http_client_open_connections`    | Number of outbound HTTP connections that are active or idle on the client.                | Counter   |
-| `http_client_request_size`        | Measures the size of HTTP client request bodies.                                          | Histogram |
+| `http_client_request_size`        | Measures the size of HTTP client request bodies.                                          | Counter   |
 | `http_client_duration`            | Measures the duration of HTTP client requests.                                            | Histogram |
-| `http_client_response_size`       | Measures the size of HTTP client response bodies.                                         | Histogram |
+| `http_client_response_size`       | Measures the size of HTTP client response bodies.                                         | Counter   |
 | `http_server_active_requests`     | Number of active HTTP server requests.                                                    | Counter   |
-| `http_server_request_size`        | Measures the size of HTTP server request bodies.                                          | Histogram |
+| `http_server_request_size`        | Measures the size of HTTP server request bodies.                                          | Counter   |
 | `http_server_duration`            | Measures the duration of HTTP server requests.                                            | Histogram |
-| `http_server_response_size`       | Measures the size of HTTP server response bodies.                                         | Histogram |
+| `http_server_response_size`       | Measures the size of HTTP server response bodies.                                         | Counter   |
 | `rpc_client_duration`             | Measures the duration of outbound RPC.                                                    | Histogram |
 | `rpc_client_request_size`         | Measures the size of RPC request messages (uncompressed).                                 | Histogram |
 | `rpc_client_requests_per_rpc`     | Measures the number of messages received per RPC. Should be 1 for all non-streaming RPCs. | Histogram |

content/en/docs/kubernetes/operator/troubleshooting/prometheus-alerts-runbooks.md

@@ -0,0 +1,23 @@
+---
+title: Prometheus Alerts Runbooks
+---
+
+## Manager Rules
+
+### ReconcileErrors
+
+|            |                                                                                                                                   |
+| ---------: | --------------------------------------------------------------------------------------------------------------------------------- |
+|    Meaning | The OpenTelemetry Operator cannot succeed in the reconciliation step, probably because of a misconfigured OpenTelemetryCollector. |
+|     Impact | No impact on already running deployments or new correct ones.                                                                     |
+|  Diagnosis | Check manager logs for reasons why this might happen.                                                                             |
+| Mitigation | Find out which OpenTelemetryCollector is causing the errors and fix the config.                                                   |
+
+### WorkqueueDepth
+
+|            |                                                                                                          |
+| ---------: | -------------------------------------------------------------------------------------------------------- |
+|    Meaning | The working queue for the operator is larger than 0.                                                     |
+|     Impact | No impact if the queue depth reverts to 0 quickly. More investigation is needed if the problem persists. |
+|  Diagnosis | Check manager logs for reasons why this might happen.                                                    |
+| Mitigation | This could be caused by many errors. Act based on what the logs are showing.                             |

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

@@ -3,7 +3,7 @@ title: Exporters
 aliases: [exporting_data]
 weight: 50
 # prettier-ignore
-cSpell:ignore: otlplog otlploghttp otlpmetric otlpmetricgrpc otlpmetrichttp otlptrace otlptracegrpc otlptracehttp promhttp stdoutlog stdouttrace
+cSpell:ignore: otlplog otlploggrpc otlploghttp otlpmetric otlpmetricgrpc otlpmetrichttp otlptrace otlptracegrpc otlptracehttp promhttp stdoutlog stdouttrace
 ---
 
 {{% docs/languages/exporters/intro go %}}
@@ -86,6 +86,8 @@ Here's how you can create an exporter with default configuration:
 
 ```go
 import (
+  "context"
+
 	"go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp"
 	"go.opentelemetry.io/otel/sdk/trace"
 )
@@ -104,6 +106,8 @@ Here's how you can create an exporter with default configuration:
 
 ```go
 import (
+  "context"
+
 	"go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc"
 	"go.opentelemetry.io/otel/sdk/trace"
 )
@@ -138,6 +142,8 @@ Here's how you can create an exporter with default configuration:
 
 ```go
 import (
+  "context"
+
 	"go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp"
 	"go.opentelemetry.io/otel/sdk/metric"
 )
@@ -156,6 +162,8 @@ Here's how you can create an exporter with default configuration:
 
 ```go
 import (
+  "context"
+
 	"go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc"
 	"go.opentelemetry.io/otel/sdk/metric"
 )
@@ -178,6 +186,8 @@ default configuration:
 
 ```go
 import (
+  "context"
+
 	"go.opentelemetry.io/otel/exporters/prometheus"
 	"go.opentelemetry.io/otel/sdk/metric"
 )
@@ -202,6 +212,8 @@ Here's how you can create an exporter with default configuration:
 
 ```go
 import (
+  "context"
+
 	"go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp"
 	"go.opentelemetry.io/otel/sdk/log"
 )
@@ -210,3 +222,23 @@ func newExporter(ctx context.Context) (log.Exporter, error) {
 	return otlploghttp.New(ctx)
 }
 ```
+
+### OTLP logs over gRPC (Experimental)
+
+[`go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc`](https://pkg.go.dev/go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc)
+contains an implementation of OTLP logs exporter using gRPC.
+
+Here's how you can create an exporter with default configuration:
+
+```go
+import (
+	"context"
+
+	"go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc"
+	"go.opentelemetry.io/otel/sdk/log"
+)
+
+func newExporter(ctx context.Context) (log.Exporter, error) {
+	return otlploggrpc.New(ctx)
+}
+```

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

@@ -301,6 +301,8 @@ OpenTelemetry Go currently supports the following instruments:
   increments
 - Histogram, a synchronous instrument that supports arbitrary values that are
   statistically meaningful, such as histograms, summaries, or percentile
+- Synchronous Gauge, a synchronous instrument that supports non-additive values,
+  such as room temperature.
 - Asynchronous Gauge, an asynchronous instrument that supports non-additive
   values, such as room temperature
 - UpDownCounter, a synchronous instrument that supports increments and

content/en/docs/zero-code/python/_index.md

@@ -8,8 +8,10 @@ cSpell:ignore: devel distro mkdir myapp pyproject uninstrumented virtualenv Werk
 ---
 
 Automatic instrumentation with Python uses a Python agent that can be attached
-to any Python application. It dynamically injects bytecode to capture telemetry
-from many popular libraries and frameworks.
+to any Python application. This agent primarily uses
+[monkey patching](https://en.wikipedia.org/wiki/Monkey_patch) to modify library
+functions at runtime, allowing for the capture of telemetry data from many
+popular libraries and frameworks.
 
 ## Setup
 
@@ -37,7 +39,8 @@ packages installed in your active `site-packages` folder, and installs the
 corresponding instrumentation libraries for these packages, if applicable. For
 example, if you already installed the `flask` package, running
 `opentelemetry-bootstrap -a install` will install
-`opentelemetry-instrumentation-flask` for you.
+`opentelemetry-instrumentation-flask` for you. The OpenTelemetry Python agent
+will use monkey patching to modify functions in these libraries at runtime.
 
 Running `opentelemetry-bootstrap` without arguments lists the recommended
 instrumentation libraries to be installed. For more information, see