Skip to content

Commit 9786b09

Browse files
WriteMayurWriteMayur
authored
Merge pull request #23932 from newrelic/daily-release/04-05-26-morning
Daily release/04 05 26 morning
2 parents 8542c93 + 6b20fc1 commit 9786b09

447 files changed

Lines changed: 37272 additions & 29921 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎src/content/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx‎

Lines changed: 17 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -415,7 +415,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
415415
The .NET agent `v9.2.0` or higher automatically instruments the [Microsoft.Azure.Cosmos](https://www.nuget.org/packages/Microsoft.Azure.Cosmos) library.
416416

417417
* Minimum supported version: 3.17.0
418-
* Latest verified compatible version: 3.58.0
418+
* Latest verified compatible version: 3.59.0
419419
* Versions 3.35.0 and higher are supported beginning with .NET agent v10.32.0
420420
</td>
421421
</tr>
@@ -457,7 +457,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
457457

458458
<DNT>**Microsoft.Data.SqlClient**</DNT>
459459
* Minimum supported version: 1.0.19239.1
460-
* Latest verified compatible version: 7.0.0
460+
* Latest verified compatible version: 7.0.1
461461
</td>
462462
</tr>
463463

@@ -520,7 +520,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
520520
<td>
521521
Minimum supported version: 2.3.0
522522

523-
Latest verified compatible version: 3.7.1
523+
Latest verified compatible version: 3.8.0
524524

525525
Versions 3.0.0 and higher are supported beginning with .NET agent v10.40.0.
526526

@@ -552,7 +552,8 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
552552

553553
<DNT>**MySql.Data**</DNT>
554554
* Minimum supported version: 6.10.7
555-
* Latest verified compatible version: 9.6.0
555+
* Latest verified compatible version: 9.7.0
556+
* Versions 9.7.0 and higher are supported beginning with .NET agent v10.52.0
556557

557558
<DNT>**MySqlConnector**</DNT>
558559
* Minimum supported version: 1.0.1
@@ -773,7 +774,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
773774
10.37.0 (`InvokeModelAsync`, `ConverseAsync`)
774775
</td>
775776
<td>
776-
4.0.17.3
777+
4.0.17.5
777778
</td>
778779
</tr>
779780
<tr>
@@ -848,7 +849,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
848849
9.7.0
849850
</td>
850851
<td>
851-
3.3.0
852+
3.3.1
852853
</td>
853854

854855
</tr>
@@ -894,7 +895,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
894895
10.0.0
895896
</td>
896897
<td>
897-
10.0.6
898+
10.0.7
898899
</td>
899900
</tr>
900901
</tbody>
@@ -951,7 +952,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
951952

952953
* Minimum supported version: 5.0
953954

954-
* Latest verified compatible version: 10.1.2
955+
* Latest verified compatible version: 10.1.4
955956
</td>
956957
</tr>
957958

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

15131514
* Minimum supported version: 3.17.0
1514-
* Latest verified compatible version: 3.58.0
1515+
* Latest verified compatible version: 3.59.0
15151516
* Versions 3.35.0 and higher are supported beginning with .NET agent v10.32.0
15161517
</td>
15171518
</tr>
@@ -1577,7 +1578,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
15771578

15781579
<DNT>**Microsoft.Data.SqlClient**</DNT>
15791580
* Minimum supported version: 1.0.19239.1
1580-
* Latest verified compatible version: 7.0.0
1581+
* Latest verified compatible version: 7.0.1
15811582

15821583
<DNT>**System.Data**</DNT>
15831584
* Minimum supported version: .NET Framework 4.6.2
@@ -1638,7 +1639,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
16381639
<td>
16391640
Minimum supported version: 2.3.0
16401641

1641-
Latest verified compatible version: 3.7.1
1642+
Latest verified compatible version: 3.8.0
16421643

16431644
Versions 3.0.0 and higher are supported beginning with .NET agent v10.40.0.
16441645

@@ -1670,7 +1671,8 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
16701671

16711672
<DNT>**MySql.Data**</DNT>
16721673
* Minimum supported version: 6.10.7
1673-
* Latest verified compatible version: 9.6.0
1674+
* Latest verified compatible version: 9.7.0
1675+
* Versions 9.7.0 and higher are supported beginning with .NET agent v10.52.0
16741676

16751677
<DNT>**MySqlConnector**</DNT>
16761678
* Minimum supported version: 1.0.1
@@ -1990,7 +1992,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
19901992
10.37.0 (`InvokeModelAsync`, `ConverseAsync`)
19911993
</td>
19921994
<td>
1993-
4.0.17.3
1995+
4.0.17.5
19941996
</td>
19951997
</tr>
19961998
<tr>
@@ -2066,7 +2068,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
20662068
9.7.0
20672069
</td>
20682070
<td>
2069-
3.3.0
2071+
3.3.1
20702072
</td>
20712073
</tr>
20722074

@@ -2111,7 +2113,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co
21112113
9.7.0
21122114
</td>
21132115
<td>
2114-
10.0.6
2116+
10.0.7
21152117
</td>
21162118
</tr>
21172119
</tbody>

‎src/content/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/kubernetes-events-integration.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -104,7 +104,7 @@ SELECT event.involvedObject.kind, event.involvedObject.name, event.type, event.m
104104
WHERE category = 'kubernetes' AND clusterName = 'YOUR_CLUSTER_NAME'
105105
```
106106

107-
The events collected by New Relic will have the exact same attributes as given by Kubernetes. For a reference of these attributes, see the [Kubernetes event v1 core documentation](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.19/#event-v1-core).
107+
The events collected by New Relic will have the exact same attributes as given by Kubernetes. For a reference of these attributes, see the [Kubernetes event v1 core documentation](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#event-v1-core).
108108

109109

110110
## Optional: Collect metrics of the event collector [#events-metrics]

‎src/content/docs/logs/logs-context/configure-logs-context-nodejs.mdx‎

Lines changed: 0 additions & 85 deletions
Original file line numberDiff line numberDiff line change
@@ -113,8 +113,6 @@ If you're not using a supported framework, you may instead use the agent's log f
113113

114114
This option should not be used with in-agent forwarding. Using an [external log forwarder](/docs/logs/forward-logs/enable-log-management-new-relic#log-forwarding) to send logs to New Relic while in-agent forwarding is enabled will cause your logs to be sent up twice to New Relic. Depending on your account, this may result in double billing.
115115

116-
This option should also not be used with [the manual log decorating formatter](#3-old-formatter). If you have references to the manual formatter in your codebase, please remove them before enabling this option.
117-
118116
1. If you want to use this option, make sure you have the in-agent forwarding configuration option disabled.
119117

120118
newrelic.js:
@@ -159,19 +157,6 @@ If you're not using a supported framework, you may instead use the agent's log f
159157
The output log message will be an empty string.
160158

161159
Some attributes may be empty if the log occurred outside a transaction or if they are not applicable to your application's context.
162-
163-
We recommend this option over manually using one of our log enrichers.
164-
</Collapser>
165-
166-
<Collapser
167-
id="3-old-formatter"
168-
title="Option 3: Use the manual process to forward and decorate logs."
169-
>
170-
Before language agents had the ability to forward and decorate logs, you could enable logs in context by updating your application to use a framework-specific log enricher. This option is still supported, but is no longer encouraged. For instructions to use this approach, see [Manual logs in context option](#configure-nodejs).
171-
172-
Also, this method requires that you install a log forwarder before enabling logs in context. If you do not have a log forwarder, the New Relic UI will prompt you to use our [infrastructure agent](/docs/logs/forward-logs/forward-your-logs-using-infrastructure-agent/).
173-
174-
If you decide to use your existing log forwarding solution and later decide to update your agent to use automatic logs in context, be sure to <DNT>**disable your manual log forwarder**</DNT>. Otherwise, your app will be sending double log lines. Depending on your account, this could result in double billing. For more information, follow the procedures to disable your [specific log forwarder](/docs/logs/forward-logs/enable-log-management-new-relic#log-forwarding).
175160
</Collapser>
176161
</CollapserGroup>
177162

@@ -204,76 +189,6 @@ If you don't see any logs for errors or traces, there may not be any for your ap
204189

205190
APM logs in context automatically forwards APM agent log data. It is enabled by default. If you do enable application logging, it can have a negative impact on your security, compliance, billing, or system performance. For more information, or if you need to adjust the default setting, follow the procedures to [disable automatic logging](/docs/logs/logs-context/disable-automatic-logging).
206191

207-
## Manual logs in context option [#configure-nodejs]
208-
209-
To enable logs in context for <InlinePopover type="apm"/> apps monitored by Node.js, you can use our manual installation option.
210-
211-
1. Make sure you have already [set up logging in New Relic](/docs/logs/enable-log-management-new-relic/enable-log-monitoring-new-relic/enable-log-management-new-relic/). This includes configuring a supported log forwarder that collects your application logs and extends the metadata that is forwarded to New Relic.
212-
213-
2. [Install](/docs/agents/nodejs-agent/installation-configuration/update-nodejs-agent/) or [update](/docs/agents/nodejs-agent/installation-configuration/update-nodejs-agent/) to the latest Node.js agent version, and [enable distributed tracing](/docs/distributed-tracing/enable-configure/quick-start/). Use [Node.js agent version 6.2.0 or higher](/docs/release-notes/agent-release-notes/nodejs-release-notes/) for logs in context.
214-
215-
3. Install [a supported framework](#automatic) to enrich your log data, or directly use [the agent's log forwarding API](https://newrelic.github.io/node-newrelic/API.html#recordLogEvent).
216-
217-
4. In your agent configuration, set `application_logging.enabled` to `false`. (Otherwise, the agent will automatically instrument your logger and calling these enrichers yourself will do nothing.)
218-
219-
5. Configure logs in context for Node.js using the appropriate log extension.
220-
221-
<CollapserGroup>
222-
<Collapser
223-
id="nodejs-winston"
224-
title="Node.js configuration with Winston"
225-
>
226-
1. To install the Winston log enricher, enter the following command into your terminal or command line interface:
227-
228-
```bash
229-
npm install @newrelic/winston-enricher
230-
```
231-
2. In your application code, update your logging configuration to add the `newrelicFormatter`:
232-
233-
```js
234-
// index.js
235-
require('newrelic')
236-
const winston = require('winston')
237-
const newrelicFormatter = require('@newrelic/winston-enricher')(winston)
238-
```
239-
240-
The New Relic formatter can be used individually or combined with other formatters as the final format.
241-
242-
```js
243-
format: winston.format.combine(
244-
winston.format.label({label: 'test'}),
245-
newrelicFormatter()
246-
)
247-
```
248-
</Collapser>
249-
250-
<Collapser
251-
id="nodejs-pino"
252-
title="Node.js configuration with Pino"
253-
>
254-
1. To install the Pino log enricher, enter the following command into your terminal or command line interface:
255-
256-
```bash
257-
npm install @newrelic/pino-enricher
258-
```
259-
2. In your application code, update your logging configuration to add the New Relic Pino plugin:
260-
261-
```js
262-
// index.js
263-
require('newrelic')
264-
const nrPino = require('@newrelic/pino-enricher')
265-
const pino = require('pino')
266-
const logger = pino(nrPino())
267-
```
268-
269-
The New Relic formatter can be used individually or combined with other formatters as the final format.
270-
</Collapser>
271-
</CollapserGroup>
272-
273-
6. To verify that you have configured the log appender correctly, run your application, then check your [logs data in New Relic](/docs/logs/log-management/ui-data/use-logs-ui/) using the query operator `has:span.id has:trace.id`.
274-
275-
If everything is configured correctly and your data is being forwarded to New Relic with the enriched metadata, your logs should now be emitted as JSON and contain `trace.id` and `span.id` fields. If you don't see log data in the UI, follow the [troubleshooting procedures](/docs/logs/log-management/troubleshooting/no-log-data-appears-ui/). If you'd like to see a working example of logs in context, take a look at our [example application](https://github.com/newrelic/newrelic-node-examples/blob/main/logs-in-context/README.md).
276-
277192
## What's next? [#what-next]
278193

279194
After you set up <InlinePopover type="apm"/> logs in context, make the most of your logging data:

‎src/content/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1742.mdx‎

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
subject: Infrastructure agent
3+
releaseDate: '2026-05-04'
4+
version: 1.74.2
5+
---
6+
7+
A new version of the agent has been released. Follow standard procedures to [update the Infrastructure agent](/docs/infrastructure/install-configure-manage-infrastructure/update-or-uninstall/update-infrastructure-agent).
8+
New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. As of this release, the oldest supported version is [Infrastructure agent 1.64.0](/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1640/).
9+
10+
## Changed
11+
* Updated New Relic Fluent Bit output to version 3.5.1. [#2226](https://github.com/newrelic/infrastructure-agent/pull/2226)
12+
* Updated `nri-flex` to v1.18.1. [#2228](https://github.com/newrelic/infrastructure-agent/pull/2228)

‎src/content/docs/release-notes/nrdot-release-notes/nrdot-host-2026-04-30.mdx‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
---
22
subject: NRDOT
33
category: Host Monitoring
4+
title: NRDOT Host Monitoring v1.12.0
45
releaseDate: '2026-04-30'
56
version: 1.12.0
67
metaDescription: Release notes for NRDOT Host Monitoring use case version 1.12.0

‎src/content/docs/synthetics/synthetic-monitoring/private-locations/install-job-manager.mdx‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,9 +8,7 @@ metaDescription: Install New Relic's container based job manager that accepts an
88
freshnessValidatedDate: never
99
---
1010

11-
Our synthetic monitoring job managers are [Docker container](https://www.docker.com/resources/what-container)-based resources that accept and execute [synthetic monitors](/docs/synthetics/synthetic-monitoring/using-monitors/intro-synthetic-monitoring/#types-of-synthetic-monitors) assigned to [private locations](/docs/synthetics/synthetic-monitoring/private-locations/private-locations-overview-monitor-internal-sites-add-new-locations).
12-
13-
The job manager can operate in a Docker container system environment, a Podman container system environment, Kubernetes container orchestration system environment, or an OpenShift container system environment. The job manager auto-detects its environment to select the appropriate operating mode.
11+
Our synthetic monitoring job managers are [container](https://www.docker.com/resources/what-container)-based resources that accept and execute [synthetic monitors](/docs/synthetics/synthetic-monitoring/using-monitors/intro-synthetic-monitoring/#types-of-synthetic-monitors) assigned to [private locations](/docs/synthetics/synthetic-monitoring/private-locations/private-locations-overview-monitor-internal-sites-add-new-locations). The job manager can operate in a Docker container system environment, a Podman container system environment, Kubernetes container orchestration system environment, or an OpenShift container system environment.
1412

1513
<Callout variant="important">
1614
If you're migrating from Node.js 16 / Chrome 134 runtimes to Node.js 22 / Chrome 146, see the [private location runtime transition guide](/docs/synthetics/synthetic-monitoring/private-locations/runtime-transition-guide) for migration strategies, deployment examples, and troubleshooting steps.

‎src/content/docs/synthetics/synthetic-monitoring/private-locations/job-manager-maintenance-monitoring.mdx‎

Lines changed: 22 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -208,7 +208,17 @@ The default level of logging is set to only inform the user of key information a
208208
</Collapser>
209209
</CollapserGroup>
210210

211-
## Retrieve Kubernetes debugging information [#retrieve-kubernetes-debugging]
211+
212+
213+
## Retrieve debugging information [#retrieve-debugging-information]
214+
215+
You can retrieve debugging information about your synthetics job manager to help troubleshoot issues. This includes information about the synthetics job manager pod and the node it is running on.
216+
217+
<CollapserGroup>
218+
<Collapser
219+
id="retrieve-kubernetes-debugging"
220+
title="Retrieve for Kubernetes"
221+
>
212222

213223
If you experience issues with your synthetics job manager in a Kubernetes container orchestration system environment, you can retrieve information about the synthetics job manager pod and the node it is running on to help troubleshoot.
214224

@@ -224,7 +234,13 @@ To retrieve information for the node the synthetics job manager pod is running o
224234
kubectl describe node NODE_ASSOCIATED_WITH_YOUR_JOB_MANAGER_POD_NAME
225235
```
226236

227-
## Retrieve OpenShift debugging information [#retrieve-openshift-debugging]
237+
</Collapser>
238+
239+
<Collapser
240+
id="retrieve-openshift-debugging"
241+
title="Retrieve for OpenShift"
242+
>
243+
228244

229245
If you experience issues with your synthetics job manager in OpenShift system environment, you can retrieve information about the synthetics job manager pod and the node it is running on to help troubleshoot.
230246

@@ -234,6 +250,10 @@ To retrieve information for the synthetics job manager pod:
234250
oc describe pod -n <your-namespace> Your_JOB_MANAGER_NAME
235251
```
236252

253+
</Collapser>
254+
255+
</CollapserGroup>
256+
237257
## Monitor synthetics job managers with New Relic Infrastructure [#monitor-via-infrastructure]
238258

239259
[New Relic's infrastructure monitoring](/docs/infrastructure) supports [advanced Docker monitoring](/docs/infrastructure/new-relic-infrastructure/data-instrumentation/docker-instrumentation-infrastructure) and [advanced Kubernetes monitoring](/docs/integrations/kubernetes-integration/get-started/introduction-kubernetes-integration).

0 commit comments

Comments
 (0)