[Phrase] Translation Updates - 2026-05-21#36903
Conversation
janine-c
left a comment
There was a problem hiding this comment.
Spot checked for the sake of time. There are some odd things in here, but the build is executing properly.
| {{% /tab %}} | ||
| {{% tab "Gauge" %}} | ||
| Para una métrica GAUGE con el siguiente esquema de etiquetado se envían **cuatro** combinaciones de valores únicos de etiqueta: | ||
| {{% tab "gauge" %}} |
There was a problem hiding this comment.
This should be capitalized
| ``` | ||
|
|
||
| El listener proporciona una variable `%%extra_dbm%%` que puede utilizarse para activar o desactivar DBM para la instancia. Este valor es por defecto `true` si la etiqueta `datadoghq.com/dbm:true` está presente. Para especificar una etiqueta personalizada para este valor, utiliza `dbm_tag`: | ||
| The listener provides an `%%extra_dbm%%` variable that can be used to enable or disable DBM for the instance. This value defaults to `true` if the tag `datadoghq.com/dbm:true` is present. To specify a custom tag for this value use `dbm_tag`: |
There was a problem hiding this comment.
Shouldn't have been un-translated
| The `%%extra_dbm%%` value is true if the tag is present, and false otherwise. It does not set its value to the value of the tag. | ||
|
|
||
| ### Create a configuration template | ||
| The listener provides an `%%extra_global_view_db%%` variable that can be used to set the `global_view_db` for the instance. This value defaults to the value of the tag `datadoghq.com/global_view_db`. To specify a custom tag for this value use `global_view_db_tag`: |
There was a problem hiding this comment.
Should have been translated
| ### Create a configuration template | ||
|
|
||
| The Datadog Agent supports configuration templates for the Postgres and MySQL integrations. Define a configuration template for the Aurora clusters you wish to monitor. |
There was a problem hiding this comment.
Should be translated, and it's odd that the heading doesn't have an ID attached
| @@ -249,17 +291,17 @@ instances: | |||
| - "region:%%extra_region%%" | |||
| ``` | |||
|
|
|||
| En este ejemplo, las variables de plantilla `%%host%%`, `%%port%%`, `%%extra_dbclusteridentifier%%`, `%%extra_dbm%%` y `%%extra_region%%` se rellenan dinámicamente con información del clúster de Aurora. | |||
| In this example, the template variables `%%host%%`, `%%port%%`, `%%extra_dbclusteridentifier%%`, `%%extra_dbm%%`, and `%%extra_region%%` are dynamically populated with information from the Aurora cluster. | |||
There was a problem hiding this comment.
Shouldn't have been un-translated
| DD_API_KEY=<YOUR_DD_API_KEY> DD_SITE="<YOUR_DD_SITE>" DD_APM_INSTRUMENTATION_ENABLED=host DD_APM_INSTRUMENTATION_LIBRARIES=python:4 DD_ENV=<AGENT_ENV> bash -c "$(curl -L https://install.datadoghq.com/scripts/install_script_agent7.sh)" | ||
| ``` | ||
|
|
||
| Replace `<YOUR_DD_API_KEY>` with your [Datadog API key][2], `<YOUR_DD_SITE>` with your [Datadog site][7], and `<AGENT_ENV>` with the environment your Agent is installed on (for example, `development`). |
There was a problem hiding this comment.
Interesting that this was un-translated, but other content between the code blocks wasn't, maybe because they're not paragraphs?
| ##### IAM Authentication | ||
|
|
||
| Pour utiliser l'[authentification IAM][2] afin de vous connecter à votre cluster Aurora, utilisez le modèle suivant : | ||
| To use [IAM authentication][2] to connect to your Aurora cluster, use the following template: |
There was a problem hiding this comment.
More headings with no IDs and un-translated content in this file
| 1. Configure the Datadog Lambda Library and Datadog Lambda Extension layers | ||
|
|
||
| - The available `<RUNTIME>` options are: {{< latest-lambda-layer-version layer="python-versions" >}}. |
| pip install datadog-lambda -t ./ | ||
| ``` | ||
|
|
||
| **Note**: `datadog-lambda` depends on `ddtrace`, which uses native extensions; therefore it must be installed and compiled in a Linux environment on the right architecture (`x86_64` or `arm64`). For example, you can use [dockerizePip][2] for the Serverless Framework and [--use-container][3] for AWS SAM. For more details, see [how to add dependencies to your function deployment package][4]. |
| 2. Définissez le paramètre `extensionLayerVersion` sur la dernière version de l'extension : La dernière version de l'extension est `{{< latest-lambda-layer-version layer="extension" >}}`. | ||
| 3. Set the required parameters `site` and `apiKeySecretArn`. | ||
| 4. Set the `env`, `service`, and `version` parameters if you previously set them as Lambda resource tags. The construct will automatically set them through the Datadog reserved environment variables instead, such as `DD_ENV`, when using the extension. | ||
| 5. Remove the `paramètre forwarderArn` : |
There was a problem hiding this comment.
Why English, and why the colon at the end? Doesn't seem to be in the English version of the page.
Automated translation updates from Phrase
Preview: https://docs-staging.datadoghq.com/guacbot/phrase-translations-2026-05-21