Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated translations - (machine translation) #20040

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

Updated translations - (machine translation) #20040

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
123 changes: 98 additions & 25 deletions ...s/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -343,7 +343,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum
El agente .NET `v9.2.0` o superior instrumentó automáticamente la biblioteca [Microsoft.Azure.Cosmos](https://www.nuget.org/packages/Microsoft.Azure.Cosmos) .

* Versión mínima admitida: 3.17.0
* Última versión compatible verificada: 3.46.1
* Latest verified compatible version: 3.47.0
* Las versiones 3.35.0 y superiores son compatibles a partir del agente .NET v10.32.0
</td>
</tr>
Expand Down Expand Up @@ -538,7 +538,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum

* Versión mínima compatible: 3.5.0

* Última versión compatible verificada: 3.7.405.13
* Latest verified compatible version: 3.7.405.22

* Versión mínima del agente requerida: 10.33.0
</td>
Expand All @@ -557,7 +557,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum
Emplee [System.Data.Odbc](https://www.nuget.org/packages/System.Data.Odbc/).

* Versión mínima admitida: 8.0.0
* Última versión compatible verificada: 9.0.1
* Latest verified compatible version: 9.0.2
* Versión mínima del agente requerida: 10.35.0

Las siguientes características admitidas para llamadas de almacenamiento de datos ODBC en .NET Framework (usando el namespace System.Data integrado) no son compatibles con .NET 8+:
Expand Down Expand Up @@ -651,11 +651,47 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum
</td>

<td>
10.23.0
10.23.0 (`InvokeModelAsync`) 10.37.0 (`InvokeModelAsync`, `ConverseAsync`)
</td>

<td>
3.7.412.4
3.7.412.13
</td>
</tr>

<tr>
<td>
OpenAI
</td>

<td>
2.0.0
</td>

<td>
10.37.0 (`CompleteChat`, `CompleteChatAsync`)
</td>

<td>
2.1.0
</td>
</tr>

<tr>
<td>
Azure.AI.OpenAI
</td>

<td>
2.0.0
</td>

<td>
10.37.0 (`CompleteChat`, `CompleteChatAsync`)
</td>

<td>
2.1.0
</td>
</tr>
</tbody>
Expand Down Expand Up @@ -737,7 +773,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum
</td>

<td>
5.3.15
5.4.0
</td>
</tr>

Expand All @@ -755,7 +791,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum
</td>

<td>
9.0.1
9.0.2
</td>
</tr>
</tbody>
Expand Down Expand Up @@ -811,7 +847,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum

* Versión mínima soportada: 5.0

* Última versión compatible verificada: 9.2.4
* Latest verified compatible version: 9.2.6
</td>
</tr>

Expand Down Expand Up @@ -865,7 +901,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum

* Versión mínima compatible: 3.7.0

* Última versión compatible verificada: 3.7.400.86
* Latest verified compatible version: 3.7.400.95
</td>
</tr>
</tbody>
Expand Down Expand Up @@ -1177,13 +1213,6 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum

Para instrumentar automáticamente el rendimiento de las llamadas de la aplicación .NET framework a estos almacenes de datos, asegúrese de tener la [versión 8.14 o superior del agente .NET](/docs/release-notes/agent-release-notes/net-release-notes):

Emplee el namespace `System.Data.ODBC` integrado del marco .NET.

* Disponible en todas las versiones del agente .NET Framework compatibles actualmente.
* Se verificó que todas las versiones del marco .NET actualmente compatibles con Microsoft son compatibles.
* Última versión compatible verificada: 4.0.40
* Versiones incompatibles conocidas: 4.0.44 o superior

<table>
<thead>
<tr>
Expand Down Expand Up @@ -1215,7 +1244,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum
El agente .NET `v9.2.0` o superior instrumenta automáticamente la biblioteca [Microsoft.Azure.Cosmos](https://www.nuget.org/packages/Microsoft.Azure.Cosmos) .

* Versión mínima admitida: 3.17.0
* Última versión compatible verificada: 3.46.1
* Latest verified compatible version: 3.47.0
* Las versiones 3.35.0 y superiores son compatibles a partir del agente .NET v10.32.0
</td>
</tr>
Expand Down Expand Up @@ -1294,7 +1323,12 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum
<Icon style={{color: '#328787'}} name="fe-check" />
</td>

<td />
<td>
Emplee el namespace `System.Data.ODBC` integrado del marco .NET.

* Disponible en todas las versiones del agente .NET Framework compatibles actualmente.
* Se verificó que todas las versiones del marco .NET actualmente compatibles con Microsoft son compatibles.
</td>
</tr>

<tr>
Expand Down Expand Up @@ -1410,7 +1444,10 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum
<Icon style={{color: '#328787'}} name="fe-check" />
</td>

<td />
<td>
* Última versión compatible verificada: 4.0.40
* Versiones incompatibles conocidas: 4.0.44 o superior
</td>
</tr>

<tr>
Expand Down Expand Up @@ -1490,7 +1527,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum

* Versión mínima compatible: 3.5.0

* Última versión compatible verificada: 3.7.405.13
* Latest verified compatible version: 3.7.405.22

* Versión mínima del agente requerida: 10.33.0
</td>
Expand Down Expand Up @@ -1637,11 +1674,47 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum
</td>

<td>
10.23.0
10.23.0 (`InvokeModelAsync`) 10.37.0 (`InvokeModelAsync`, `ConverseAsync`)
</td>

<td>
3.7.412.13
</td>
</tr>

<tr>
<td>
OpenAI
</td>

<td>
2.0.0
</td>

<td>
10.37.0 (`CompleteChat`, `CompleteChatAsync`)
</td>

<td>
2.1.0
</td>
</tr>

<tr>
<td>
Azure.AI.OpenAI
</td>

<td>
2.0.0
</td>

<td>
10.37.0 (`CompleteChat`, `CompleteChatAsync`)
</td>

<td>
3.7.412.4
2.1.0
</td>
</tr>
</tbody>
Expand Down Expand Up @@ -1723,7 +1796,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum
</td>

<td>
5.3.15
5.4.0
</td>
</tr>

Expand All @@ -1741,7 +1814,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum
</td>

<td>
9.0.1
9.0.2
</td>
</tr>
</tbody>
Expand Down Expand Up @@ -1859,7 +1932,7 @@ Para el marco y la biblioteca que no se [instrumentan automáticamente](#instrum

* Versión mínima compatible: 3.7.0

* Última versión compatible verificada: 3.7.400.86
* Latest verified compatible version: 3.7.400.95
</td>
</tr>
</tbody>
Expand Down
59 changes: 58 additions & 1 deletion ...es/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -100,10 +100,67 @@ Consulte el ejemplo Redis en [el recolector de monitoreo de infraestructura](/do

New Relic soporta relaciones entre entidades provenientes de la instrumentación OpenTelemetry . Estas relaciones se sintetizan automáticamente cuando se cumplen los criterios de relación adecuados. A continuación se detallan las relaciones que se admiten actualmente y sus criterios requeridos.

### Servicio de hospedaje [#service-to-host]
### Service to infrastructure relationships using the OpenTelemetry Collector [#service-to-infra-otel-collector]

The OpenTelemetry Collector can be used to [monitor your infrastructure](/docs/opentelemetry/get-started/collector-infra-monitoring/opentelemetry-collector-infra-intro). Entity relationships are supported between OpenTelemetry instrumented services the infrastructure entities created from the OpenTelemetry Collector.

The following relationships to your services are supported:

* [Hospedadores](#service-to-host)
* [Contenedor](#service-to-container)

#### Hospedadores [#service-to-host]

Las relaciones entre un servicio y una entidad host requieren que el servicio incluya el atributo de recurso `host.id` y que coincida con el `host.id` del host en el que se ejecuta.

#### Contenedor [#service-to-container]

Relationships between a service and container entity require that the service includes the `container.id` resource attribute and that it matches the `container.id` of the container it is running in.

### Service to infrastructure relationships using the New Relic infrastructure agent [#service-to-infra-nr-infra-agent]

The [New Relic infrastructure agent](/docs/infrastructure/choose-infra-install-method) can be used to monitor your infrastructure. Entity relationships are supported between OpenTelemetry instrumented services and infrastructure entities created from the New Relic infrastructure agent.

For these relationships to work, the telemetry emitted from your service must be configured so that it can be correlated with the telemetry emitted by the infrastructure agent. This requires the telemetry of your service to include resource attributes that identify the host, container, etc that the service is running on. This is usually as easy as configuring [resource detectors](https://opentelemetry.io/docs/concepts/resources/#resource-detectors) provided by the OpenTelemetry SDK for your language or using the OpenTelemetry Collector&amp;apos;s [resource detection processor](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/processor/resourcedetectionprocessor/README.md).

The following relationships to your services are supported:

* [Hospedadores](#service-to-infra-nr-infra-agent-hosts)
* [Contenedor](#service-to-infra-nr-infra-agent-containers)

#### Hosts monitored with the New Relic infrastructure agent [#service-to-infra-nr-infra-agent-hosts]

Host relationships between OpenTelemetry instrumented services and host entities generated from the New Relic infrastructure agent require two things:

* The `host.id` resource attribute must be present on the telemetry from the service.
* The `host.id` must correlate with the [host&apos;s identity](#service-to-infra-nr-infra-derive-host-identity) derived by the infrastructure agent.

##### Deriving host identity [#service-to-infra-nr-infra-derive-host-identity]

<Callout variant="important">
The host identity derived by the New Relic infrastructure agent does not exactly match the semantics of OpenTelemetry&apos;s `host.id` resource attribute in all circumstances. This can cause difficulties in correlating services to hosts monitored with the infrastructure agent. Read this section carefully to understand potential challenges.
</Callout>

The host identity derived by the New Relic infrastructure agent depends on hosting environment and agent configuration.

For services to be properly correlated to hosts monitored by the New Relic infrastructure agent, the `host.id` resource attribute emitted by the service must match the host identity computed by the agent. The following sections describe, in priority order, how the infrastructure agent computes a host&amp;apos;s identity so that you can understand how to properly set the service&amp;apos;s `host.id`.

###### Infrastructure agent configured with a `display_name` [#service-to-infra-nr-infra-display-name]

If the infrastructure agent is configured to use a [`display_name`](/docs/infrastructure/infrastructure-agent/configuration/infrastructure-agent-configuration-settings/#display-name) then it will use that as the host&amp;apos;s identity. Your OpenTelemetry instrumented service must be configured to emit a `host.id` that is equal to the `display_name`.

###### Host running in a cloud environment [#service-to-infra-nr-infra-cloud-environment]

If the host is running in a cloud environment (e.g., AWS or Azure) then the agent will use the instance ID assigned by the cloud provider. Your OpenTelemetry instrumented service should be configured to use a resource detector appropriate for your cloud environment.

###### Host running in a non-cloud environment [#service-to-infra-nr-infra-non-cloud]

In non-containerized environments the infrastructure agent computes a fully-qualified domain name (FQDN) of the host. How the agent determines the FQDN differs based on a variety of factors such as the operating system. Resource detectors cannot be relied on to compute the same value as the FQDN resolved by the infrastructure agent. It is recommended that you explicitly configure a `display_name` for the infrastructure agent and the `host.id` of your service so that they match.

#### Service to containers monitored with the New Relic infrastructure agent [#service-to-infra-nr-infra-agent-containers]

Relationships between a service and container entity require that the service be configured with an appropriate resource detector that includes the `container.id` resource attribute.

### Amazon CloudWatch Metric Streams

Su infraestructura alojada en AWS se puede monitorear con la integración de New Relic con [Amazon CloudWatch Metric Streams](/install/aws-cloudwatch/). Esta no es una solución OpenTelemetry para monitorear su infraestructura. Sin embargo, New Relic admite un serial de relaciones entre los servicios instrumentados OpenTelemetry y la infraestructura monitoreada mediante Amazon CloudWatch Metric Streams.
Expand Down
6 changes: 3 additions & 3 deletions ...toring/azure-function-monitoring/compatibility-requirement-azure-monitoring.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,15 +34,15 @@ Según su entorno de hospedaje, se admiten las siguientes pilas de tiempo de eje

<TabsPages>
<TabsPageItem id="1">
* .NET: versión 6 - 9, solo modelo aislado
* .NET stack: .NET 6 - 9, Isolated model only
</TabsPageItem>

<TabsPageItem id="2">
* .NET: versiones 6 - 9
* .NET stack: .NET 4.8 (.NET agent version 10.37.0 and later) and .NET 6 - 9, Isolated model only
</TabsPageItem>

<TabsPageItem id="3">
* .NET: versión 6 - 9, solo modelo aislado
* .NET stack: .NET 6 - 9, Isolated model only
</TabsPageItem>
</TabsPages>
</Tabs>
Expand Down
4 changes: 2 additions & 2 deletions ...s/apm/agents/php-agent/getting-started/php-agent-compatibility-requirements.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -795,7 +795,7 @@ Les bases de données et bibliothèques suivantes sont prises en charge :
</td>

<td>
RabbitMQ (php-amqplib 3.7 library only)
RabbitMQ (bibliothèque php-amqplib 3.7 uniquement)
</td>
</tr>

Expand Down Expand Up @@ -825,7 +825,7 @@ Les bases de données et bibliothèques suivantes sont prises en charge :
</td>

<td>
SQS (aws-sdk-php 3 library only)
SQS (bibliothèque aws-sdk-php 3 uniquement)
</td>
</tr>

Expand Down
Loading
Loading