Skip to content

Commit

Permalink
Merge branch 'develop' into NR-356329-browser-logs
Browse files Browse the repository at this point in the history
  • Loading branch information
@adutta-newrelic
adutta-newrelic committed Feb 22, 2025
2 parents b0cdb24 + 9f18d2a commit 7d469a9
Show file tree
Hide file tree
Showing 20 changed files with 603 additions and 53 deletions.
91 changes: 74 additions & 17 deletions ...s/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -398,7 +398,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
The .NET agent `v9.2.0` or higher automatically instruments the [Microsoft.Azure.Cosmos](https://www.nuget.org/packages/Microsoft.Azure.Cosmos) library.

* Minimum supported version: 3.17.0
* Latest verified compatible version: 3.46.1
* Latest verified compatible version: 3.47.0
* Versions 3.35.0 and higher are supported beginning with .NET agent v10.32.0
</td>
</tr>
Expand Down Expand Up @@ -610,7 +610,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
Use [AWSSDK.DynamoDBv2](https://www.nuget.org/packages/AWSSDK.DynamoDBv2).

* Minimum supported version: 3.5.0
* Latest verified compatible version: 3.7.405.13
* Latest verified compatible version: 3.7.405.22

* Minimum agent version required: 10.33.0
</td>
Expand All @@ -631,7 +631,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
<td>
Use [System.Data.Odbc](https://www.nuget.org/packages/System.Data.Odbc/).
* Minimum supported version: 8.0.0
* Latest verified compatible version: 9.0.1
* Latest verified compatible version: 9.0.2
* Minimum agent version required: 10.35.0


Expand Down Expand Up @@ -732,12 +732,40 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
3.7.200.0
</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>
</table>
Expand Down Expand Up @@ -814,7 +842,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
9.7.0
</td>
<td>
5.3.15
5.4.0
</td>
</tr>

Expand All @@ -829,7 +857,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
10.0.0
</td>
<td>
9.0.1
9.0.2
</td>
</tr>
</tbody>
Expand Down Expand Up @@ -886,7 +914,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co

* Minimum supported version: 5.0

* Latest verified compatible version: 9.2.4
* Latest verified compatible version: 9.2.6
</td>
</tr>

Expand Down Expand Up @@ -940,7 +968,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co

* Minimum supported version: 3.7.0

* Latest verified compatible version: 3.7.400.86
* Latest verified compatible version: 3.7.400.95
</td>
</tr>

Expand Down Expand Up @@ -1341,7 +1369,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
The .NET agent `v9.2.0` or higher automatically instruments [Microsoft.Azure.Cosmos](https://www.nuget.org/packages/Microsoft.Azure.Cosmos) library.

* Minimum supported version: 3.17.0
* Latest verified compatible version: 3.46.1
* Latest verified compatible version: 3.47.0
* Versions 3.35.0 and higher are supported beginning with .NET agent v10.32.0
</td>
</tr>
Expand Down Expand Up @@ -1649,7 +1677,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
Use [AWSSDK.DynamoDBv2](https://www.nuget.org/packages/AWSSDK.DynamoDBv2).

* Minimum supported version: 3.5.0
* Latest verified compatible version: 3.7.405.13
* Latest verified compatible version: 3.7.405.22

* Minimum agent version required: 10.33.0
</td>
Expand Down Expand Up @@ -1807,12 +1835,41 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
3.7.200.0
</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>
</table>
</Collapser>
Expand Down Expand Up @@ -1888,7 +1945,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
9.7.0
</td>
<td>
5.3.15
5.4.0
</td>
</tr>

Expand All @@ -1903,7 +1960,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
9.7.0
</td>
<td>
9.0.1
9.0.2
</td>
</tr>
</tbody>
Expand Down Expand Up @@ -2023,7 +2080,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co

* Minimum supported version: 3.7.0

* Latest verified compatible version: 3.7.400.86
* Latest verified compatible version: 3.7.400.95
</td>
</tr>

Expand Down
22 changes: 11 additions & 11 deletions ...agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -274,23 +274,23 @@ version.

| Package name | Minimum supported version | Latest supported version | Introduced in* |
| --- | --- | --- | --- |
| `@apollo/gateway` | 2.3.0 | 2.9.3 | `@newrelic/apollo-server-plugin@1.0.0` |
| `@apollo/gateway` | 2.3.0 | 2.10.0 | `@newrelic/apollo-server-plugin@1.0.0` |
| `@apollo/server` | 4.0.0 | 4.11.3 | `@newrelic/apollo-server-plugin@2.1.0` |
| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.744.0 | 11.13.0 |
| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.744.0 | 8.7.1 |
| `@aws-sdk/client-sns` | 3.0.0 | 3.744.0 | 8.7.1 |
| `@aws-sdk/client-sqs` | 3.0.0 | 3.744.0 | 8.7.1 |
| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.744.0 | 8.7.1 |
| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.750.0 | 11.13.0 |
| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.750.0 | 8.7.1 |
| `@aws-sdk/client-sns` | 3.0.0 | 3.750.0 | 8.7.1 |
| `@aws-sdk/client-sqs` | 3.0.0 | 3.750.0 | 8.7.1 |
| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.750.0 | 8.7.1 |
| `@aws-sdk/smithy-client` | 3.47.0 | 3.374.0 | 8.7.1 |
| `@elastic/elasticsearch` | 7.16.0 | 8.17.0 | 11.9.0 |
| `@grpc/grpc-js` | 1.4.0 | 1.12.6 | 8.17.0 |
| `@hapi/hapi` | 20.1.2 | 21.3.12 | 9.0.0 |
| `@koa/router` | 11.0.2 | 13.1.0 | 3.2.0 |
| `@langchain/core` | 0.1.17 | 0.3.40 | 11.13.0 |
| `@nestjs/cli` | 9.0.0 | 11.0.2 | 10.1.0 |
| `@nestjs/cli` | 9.0.0 | 11.0.4 | 10.1.0 |
| `@opensearch-project/opensearch` | 2.1.0 | 3.3.0 | 12.10.0 |
| `@prisma/client` | 5.0.0 | 6.3.1 | 11.0.0 |
| `@smithy/smithy-client` | 2.0.0 | 4.1.3 | 11.0.0 |
| `@smithy/smithy-client` | 2.0.0 | 4.1.5 | 11.0.0 |
| `amqplib` | 0.5.0 | 0.10.5 | 2.0.0 |
| `apollo-server` | 3.0.0 | 3.13.0 | `@newrelic/apollo-server-plugin@1.0.0` |
| `apollo-server-express` | 3.0.0 | 3.13.0 | `@newrelic/apollo-server-plugin@1.0.0` |
Expand All @@ -312,9 +312,9 @@ version.
| `mysql` | 2.2.0 | 2.18.1 | 1.32.0 |
| `mysql2` | 2.0.0 | 3.12.0 | 1.32.0 |
| `next` | 13.4.19 | 15.1.7 | 12.0.0 |
| `openai` | 4.0.0 | 4.84.0 | 11.13.0 |
| `pg` | 8.2.0 | 8.13.2 | 9.0.0 |
| `pg-native` | 3.0.0 | 3.2.1 | 9.0.0 |
| `openai` | 4.0.0 | 4.85.1 | 11.13.0 |
| `pg` | 8.2.0 | 8.13.3 | 9.0.0 |
| `pg-native` | 3.0.0 | 3.2.2 | 9.0.0 |
| `pino` | 7.0.0 | 9.6.0 | 8.11.0 |
| `q` | 1.3.0 | 1.5.1 | 1.26.2 |
| `redis` | 3.1.0 | 4.7.0 | 1.31.0 |
Expand Down
100 changes: 99 additions & 1 deletion ...nt/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -122,12 +122,110 @@ OpenTelemetry instrumentation. These relationships are synthesized
automatically when the appropriate relationship criteria is met. Below are the
relationships that are currently supported and their required criteria.

### Service to host [#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:

* [Hosts](#service-to-host)
* [Containers](#service-to-container)

#### Hosts [#service-to-host]

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

#### Containers [#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'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:

* [Hosts](#service-to-infra-nr-infra-agent-hosts)
* [Containers](#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'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'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's
identity so that you can understand how to properly set the service'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'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

Your infrastructure hosted in AWS can be monitored with New Relic's integration
Expand Down
39 changes: 39 additions & 0 deletions .../docs/release-notes/agent-release-notes/net-release-notes/net-agent-10-37-0.mdx
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
---
subject: .NET agent
releaseDate: '2025-02-19'
version: 10.37.0
downloadLink: 'https://download.newrelic.com/dot_net_agent/latest_release'
features: ['Add AI Monitoring instrumentation for `AmazonBedrockRuntimeClient.ConverseAsync()`.','Add AI Monitoring instrumentation for OpenAI and Azure.AI.OpenAI.','Add support for .NET Framework Azure Function Apps.','Improve logging and validation for license keys.']
bugs: []
security: []
---

### New features

* Add AI Monitoring instrumentation for `AmazonBedrockRuntimeClient.ConverseAsync()` ([#2997](https://github.com/newrelic/newrelic-dotnet-agent/issues/2997)) ([cdc2f6c](https://github.com/newrelic/newrelic-dotnet-agent/commit/cdc2f6c6de6640a72ad2c729f8f3abe31a14289c))
* Add AI Monitoring instrumentation for OpenAI and Azure.AI.OpenAI ([#2987](https://github.com/newrelic/newrelic-dotnet-agent/issues/2987)) ([aa06d9d](https://github.com/newrelic/newrelic-dotnet-agent/commit/aa06d9db633f12f345fdfa6a574dd9e1a8fbec85))
* Add support for .NET Framework Azure Function Apps ([#2992](https://github.com/newrelic/newrelic-dotnet-agent/issues/2992)) ([5b077f3](https://github.com/newrelic/newrelic-dotnet-agent/commit/5b077f3dc898f57a3637de01d5da4bf4a3b5e143))
* Improve logging and validation for license keys. ([#2982](https://github.com/newrelic/newrelic-dotnet-agent/issues/2982)) ([19e8387](https://github.com/newrelic/newrelic-dotnet-agent/commit/19e8387a49e01d706691512dea1bb32e8d124b87))

### Checksums
| File | SHA - 256 Hash |
| ---| ---|
| newrelic-dotnet-agent-10.37.0-1.x86_64.rpm | 3852B2A27A75FB1983C34D9403091BA3311F7FCC43EA48A1321A8733739AC505 |
| newrelic-dotnet-agent_10.37.0_amd64.deb | 20A384451D5C3949B5442E0C742ECD9573A2CEE8776789893B8D8F56F81DA2B5 |
| newrelic-dotnet-agent_10.37.0_amd64.tar.gz | FC0263475AF6C49BBD925C060F2A8BD97CA01731040B685A307E01F6040CD433 |
| newrelic-dotnet-agent_10.37.0_arm64.deb | 7B0BA1986BE52D7254C5A7455A93862634C3BC89C0AC22D3D4859AB665864C2B |
| newrelic-dotnet-agent_10.37.0_arm64.tar.gz | FD60250AF6AD1437CA114ABD660B22E7407C153CC55EC9EC870641AEF6BB4F47 |
| NewRelicDotNetAgent_10.37.0_x64.msi | 7945D0F524C43278F69761F84D4CA11A915A90974E87A0D0FF22C124F1557C3A |
| NewRelicDotNetAgent_10.37.0_x64.zip | 1C31D39F5F315F2C131E9190E2061F496D0C27F54CD3A8EC14FB2E9BE959965A |
| NewRelicDotNetAgent_10.37.0_x86.msi | AEB95BA464DD51D72AF7899DD4F6351E2D183A7D84AF0A0F9C2838BBF2DC19D5 |
| NewRelicDotNetAgent_10.37.0_x86.zip | E8BDF4C2F98124DF0428BA541028B3FF8F8C6BD7FC654B5533D8709036E7E24A |


### Updating your agent

* Follow standard procedures to [update the .NET agent](/docs/agents/net-agent/installation-configuration/update-net-agent).
* If you're using a particularly old agent, review the list of major changes and procedures for [updating legacy .NET agents](/docs/apm/agents/net-agent/installation/update-net-agent/#updating_older_net).

We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about [keeping your agent up to date](/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent).
See the New Relic .NET agent [EOL policy doc](/docs/apm/agents/net-agent/getting-started/net-agent-eol-policy) for information about agent releases and support dates.

Loading

0 comments on commit 7d469a9

Please sign in to comment.