Merge branch 'main' into localization/pt-br/sampling

.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/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/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/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