Skip to content

Commit

Permalink
Merge pull request #19351 from newrelic/daily-release/11-21-24-morning
Browse files Browse the repository at this point in the history
Daily release/11 21 24 morning
  • Loading branch information
adutta-newrelic authored Nov 21, 2024
2 parents fb1c328 + 09f1260 commit 8c1425c
Show file tree
Hide file tree
Showing 8 changed files with 238 additions and 47 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -275,20 +275,20 @@ version.
| --- | --- | --- | --- |
| `@apollo/gateway` | 2.3.0 | 2.9.3 | `@newrelic/[email protected]` |
| `@apollo/server` | 4.0.0 | 4.11.2 | `@newrelic/[email protected]` |
| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.691.0 | 11.13.0 |
| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.691.0 | 8.7.1 |
| `@aws-sdk/client-sns` | 3.0.0 | 3.691.0 | 8.7.1 |
| `@aws-sdk/client-sqs` | 3.0.0 | 3.691.0 | 8.7.1 |
| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.691.0 | 8.7.1 |
| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.696.0 | 11.13.0 |
| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.696.0 | 8.7.1 |
| `@aws-sdk/client-sns` | 3.0.0 | 3.696.0 | 8.7.1 |
| `@aws-sdk/client-sqs` | 3.0.0 | 3.696.0 | 8.7.1 |
| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.696.0 | 8.7.1 |
| `@aws-sdk/smithy-client` | 3.47.0 | 3.374.0 | 8.7.1 |
| `@elastic/elasticsearch` | 7.16.0 | 8.16.0 | 11.9.0 |
| `@elastic/elasticsearch` | 7.16.0 | 8.16.1 | 11.9.0 |
| `@grpc/grpc-js` | 1.4.0 | 1.12.2 | 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.18 | 11.13.0 |
| `@nestjs/cli` | 9.0.0 | 10.4.7 | 10.1.0 |
| `@nestjs/cli` | 9.0.0 | 10.4.8 | 10.1.0 |
| `@prisma/client` | 5.0.0 | 5.22.0 | 11.0.0 |
| `@smithy/smithy-client` | 2.0.0 | 3.4.3 | 11.0.0 |
| `@smithy/smithy-client` | 2.0.0 | 3.4.4 | 11.0.0 |
| `amqplib` | 0.5.0 | 0.10.4 | 2.0.0 |
| `apollo-server` | 3.0.0 | 3.13.0 | `@newrelic/[email protected]` |
| `apollo-server-express` | 3.0.0 | 3.13.0 | `@newrelic/[email protected]` |
Expand All @@ -310,7 +310,7 @@ version.
| `mysql` | 2.2.0 | 2.18.1 | 1.32.0 |
| `mysql2` | 2.0.0 | 3.11.4 | 1.32.0 |
| `next` | 13.4.19 | 15.0.3 | 12.0.0 |
| `openai` | 4.0.0 | 4.72.0 | 11.13.0 |
| `openai` | 4.0.0 | 4.73.0 | 11.13.0 |
| `pg` | 8.2.0 | 8.13.1 | 9.0.0 |
| `pg-native` | 3.0.0 | 3.2.0 | 9.0.0 |
| `pino` | 7.0.0 | 9.5.0 | 8.11.0 |
Expand Down
107 changes: 70 additions & 37 deletions src/content/docs/data-apis/manage-data/query-limits.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -57,8 +57,10 @@ From left to right, top to bottom:
id=""
title="Resource Consumption Limits as a %"
>
```
FROM Metric select rate(sum(newrelic.resourceConsumption.currentValue), 1 minute) /latest(newrelic.resourceConsumption.limitValue) * 100 facet limitName where limitTimeInterval = '1 minute' timeseries limit max
```sql
FROM Metric
SELECT rate(sum(newrelic.resourceConsumption.currentValue), 1 minute) / latest(newrelic.resourceConsumption.limitValue) * 100
FACET limitName WHERE limitTimeInterval = '1 minute' TIMESERIES LIMIT MAX
```
</Collapser>

Expand All @@ -67,8 +69,10 @@ From left to right, top to bottom:
id=""
title="Max % Consumption in an hour"
>
```
SELECT max(`usage`) FROM (FROM Metric select rate(sum(newrelic.resourceConsumption.currentValue), 1 minute) / latest(newrelic.resourceConsumption.limitValue) * 100 as 'usage' facet limitName timeseries ) facet limitName limit max
```sql
SELECT max(`usage`)
FROM (FROM Metric SELECT rate(sum(newrelic.resourceConsumption.currentValue), 1 minute) / latest(newrelic.resourceConsumption.limitValue) * 100 AS 'usage' FACET limitName TIMESERIES)
FACET limitName LIMIT MAX
```
</Collapser>

Expand All @@ -77,8 +81,9 @@ From left to right, top to bottom:
id=""
title="APM Agent API transaction events request per minute"
>
```
FROM Metric select rate(sum(newrelic.resourceConsumption.currentValue), 1 minute) where limitName = 'APM Agent API transaction events requests per minute' TIMESERIES
```sql
FROM Metric SELECT rate(sum(newrelic.resourceConsumption.currentValue), 1 minute)
WHERE limitName = 'APM Agent API transaction events requests per minute' TIMESERIES
```
</Collapser>

Expand All @@ -87,8 +92,11 @@ From left to right, top to bottom:
id=""
title="Trace API With limit line"
>
```
FROM Metric select rate(sum(newrelic.resourceConsumption.currentValue), 1 minute) as 'usage', latest(newrelic.resourceConsumption.limitValue) as 'limit' where limitName = 'Trace API requests per minute' TIMESERIES
```sql
FROM Metric
SELECT rate(sum(newrelic.resourceConsumption.currentValue), 1 minute) AS 'usage',
latest(newrelic.resourceConsumption.limitValue) AS 'limit'
WHERE limitName = 'Trace API requests per minute' TIMESERIES
```
</Collapser>

Expand All @@ -97,8 +105,9 @@ From left to right, top to bottom:
id=""
title="Impact FACET"
>
```
From Metric select rate(sum(newrelic.resourceConsumption.impact), 1 minute) facet dataType, impact, resource TIMESERIES 1 minute limit max
```sql
FROM Metric SELECT rate(sum(newrelic.resourceConsumption.impact), 1 minute)
FACET dataType, impact, resource TIMESERIES 1 minute LIMIT MAX
```
</Collapser>

Expand All @@ -107,8 +116,9 @@ From left to right, top to bottom:
id=""
title="NrIntegrationError by limit"
>
```
FROM NrIntegrationError select count(*) facet limitName TIMESERIES MAX since 1 day ago limit max
```sql
FROM NrIntegrationError SELECT count(*)
FACET limitName TIMESERIES MAX SINCE 1 day ago LIMIT MAX
```
</Collapser>

Expand All @@ -120,17 +130,23 @@ From left to right, top to bottom:
If you want to see limits for multiple accounts on one chart:

1. run this query from one of the accounts:
```
FROM Metric select rate(sum(newrelic.resourceConsumption.currentValue), 1 minute) / latest(newrelic.resourceConsumption.limitValue) * 100 facet limitName, consumingAccountId where limitTimeInterval = '1 minute' timeseries limit max
```sql
FROM Metric
SELECT rate(sum(newrelic.resourceConsumption.currentValue), 1 minute) / latest(newrelic.resourceConsumption.limitValue) * 100
WHERE limitTimeInterval = '1 minute'
FACET limitName, consumingAccountId TIMESERIES LIMIT MAX
```

2. Click <DNT>**Add another query**</DNT>.

3. Select a different account.

4. Then run this query again:
```
FROM Metric select rate(sum(newrelic.resourceConsumption.currentValue), 1 minute) / latest(newrelic.resourceConsumption.limitValue) * 100 facet limitName, consumingAccountId where limitTimeInterval = '1 minute' timeseries limit max
```sql
FROM Metric
SELECT rate(sum(newrelic.resourceConsumption.currentValue), 1 minute) / latest(newrelic.resourceConsumption.limitValue) * 100
WHERE limitTimeInterval = '1 minute'
FACET limitName, consumingAccountId TIMESERIES LIMIT MAX
```

5. Finally, save it.
Expand All @@ -141,15 +157,20 @@ From left to right, top to bottom:
id=""
title="Limit list and NrIntegrationError"
>
```
FROM Metric, NrIntegrationError select rate(sum(newrelic.resourceConsumption.currentValue), 1 minute) as 'Per Minute Count',latest(newrelic.resourceConsumption.limitValue) as ' limit Value',(rate(sum(newrelic.resourceConsumption.currentValue), 1 minute)/latest(newrelic.resourceConsumption.limitValue)*100)as 'Percent Used', filter (count(*), where NrIntegrationError.limitValue is not null) as 'limit reached count' facet limitName limit 1000
```sql
FROM Metric, NrIntegrationError
SELECT rate(sum(newrelic.resourceConsumption.currentValue), 1 minute) AS 'Per Minute Count',
latest(newrelic.resourceConsumption.limitValue) AS 'Limit Value',
(rate(sum(newrelic.resourceConsumption.currentValue), 1 minute) / latest(newrelic.resourceConsumption.limitValue) * 100) AS 'Percent Used',
filter(count(*), WHERE NrIntegrationError.limitValue is not null) AS 'Limit Reached Count'
FACET limitName LIMIT 1000
```
</Collapser>
</CollapserGroup>

## Limit metrics

These metrics, used in the dashboard queries above, can hone in on a single limit or resource. Or, with the help of `FACET limitName or resource` provide a view across all your limits.
These metrics, used in the dashboard queries above, can hone in on a single limit or resource. Or, with the help of `FACET limitName OR resource` provide a view across all your limits.

<CollapserGroup>
<Collapser
Expand All @@ -161,14 +182,16 @@ These metrics, used in the dashboard queries above, can hone in on a single limi

* Example for Metric API requests per minute.

```
FROM Metric select latest(newrelic.resourceConsumption.limitValue) where limitName = 'Metric API requests per minute'
```sql
FROM Metric SELECT latest(newrelic.resourceConsumption.limitValue)
WHERE limitName = 'Metric API requests per minute'
```

* To show all limits, add `FACET limitName` and consider grouping by `limitTimeInterval`.

```
FROM Metric select latest(newrelic.resourceConsumption.limitValue) WHERE limitTimeInterval = '1 minute' FACET limitName limit max
```sql
FROM Metric SELECT latest(newrelic.resourceConsumption.limitValue)
WHERE limitTimeInterval = '1 minute' FACET limitName LIMIT MAX
```
</Collapser>

Expand All @@ -181,14 +204,16 @@ These metrics, used in the dashboard queries above, can hone in on a single limi

* Example for Metric API request per minute:

```
FROM Metric select rate(sum(newrelic.resourceConsumption.currentValue),1 minute) where limitName = 'Metric API requests per minute'
```sql
FROM Metric SELECT rate(sum(newrelic.resourceConsumption.currentValue), 1 minute)
WHERE limitName = 'Metric API requests per minute'
```

* To show all limits, add `FACET limitName` and consider grouping by `limitTimeInterval`.

```
FROM Metric select rate(sum(newrelic.resourceConsumption.currentValue),1 minute) where limitTimeInterval = '1 minute' FACET limitName limit max
```sql
FROM Metric SELECT rate(sum(newrelic.resourceConsumption.currentValue), 1 minute)
WHERE limitTimeInterval = '1 minute' FACET limitName LIMIT MAX
```
</Collapser>

Expand All @@ -201,8 +226,9 @@ These metrics, used in the dashboard queries above, can hone in on a single limi

The most granular we have is `dataType`. It is possible for multiple instances of `limitName` to impact a single type, such as Metric RPM and DPM. If we know, we will display `limitName`.

```
From Metric select rate(sum(newrelic.resourceConsumption.impact), 1 minute) facet dataType, resource, impact, limitName TIMESERIES limit max
```sql
FROM Metric SELECT rate(sum(newrelic.resourceConsumption.impact), 1 minute)
FACET dataType, resource, impact, limitName TIMESERIES LIMIT MAX
```
</Collapser>
</CollapserGroup>
Expand Down Expand Up @@ -240,8 +266,10 @@ You can use the following NRQL queries to create alerts. Learn about creating al
id=""
title="Limits faceted by LimitName and scoped by Timewindow"
>
```
From Metric select (rate(sum(newrelic.resourceConsumption.currentValue), 1 minute)/latest(newrelic.resourceConsumption.limitValue))*100 facet limitName
```sql
FROM Metric
SELECT (rate(sum(newrelic.resourceConsumption.currentValue), 1 minute) / latest(newrelic.resourceConsumption.limitValue)) * 100
FACET limitName
```
</Collapser>

Expand All @@ -250,8 +278,10 @@ You can use the following NRQL queries to create alerts. Learn about creating al
id=""
title="Alert on a single limit"
>
```
From Metric select (rate(sum(newrelic.resourceConsumption.currentValue), 1 minute)/latest(newrelic.resourceConsumption.limitValue))*100 where limitName = 'my limit'
```sql
FROM Metric
SELECT (rate(sum(newrelic.resourceConsumption.currentValue), 1 minute) / latest(newrelic.resourceConsumption.limitValue)) * 100
WHERE limitName = 'my limit'
```
</Collapser>

Expand All @@ -260,8 +290,9 @@ You can use the following NRQL queries to create alerts. Learn about creating al
id=""
title="Alert on limit impact faceted by dataType, impact, resource, and reason"
>
```
From Metric select rate(sum(newrelic.resourceConsumption.impact), 1 minute) facet dataType, impact, resource, reason
```sql
FROM Metric SELECT rate(sum(newrelic.resourceConsumption.impact), 1 minute)
FACET dataType, impact, resource, reason
```
</Collapser>

Expand All @@ -270,8 +301,10 @@ You can use the following NRQL queries to create alerts. Learn about creating al
id=""
title="Alert on impact of a single dataType"
>
```
From Metric select rate(sum(newrelic.resourceConsumption.impact), 1 minute) facet dataType, impact, resource, reason WHERE dataType = 'important things'
```sql
FROM Metric SELECT rate(sum(newrelic.resourceConsumption.impact), 1 minute)
WHERE dataType = 'important things'
FACET dataType, impact, resource, reason
```
</Collapser>
</CollapserGroup>
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ We think you'll find these features downright invaluable. Let's get started!

<Steps>
<Step>
Standard deviation mesaures the amount of variation or dispersion within a set of values. It uses a scale from low (values close to the average) to high (values far from the average). The `stddev()`function lets you look between the lines of averages and understand reported values on a deeper level. In this example, you compare the standard deviation of transaction response time ("duration") for the last day to the previous day.
Standard deviation measures the amount of variation or dispersion within a set of values. It uses a scale from low (values close to the average) to high (values far from the average). The `stddev()`function lets you look between the lines of averages and understand reported values on a deeper level. In this example, you compare the standard deviation of transaction response time ("duration") for the last day to the previous day.

```sql
SELECT stddev(duration)
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
---
subject: .NET agent
releaseDate: '2024-11-19'
version: 10.34.0
downloadLink: 'https://download.newrelic.com/dot_net_agent/latest_release'
features: ['Add Distributed Tracing support for Azure Functions HTTPTrigger.','The .NET agent now allows you to opt-in to adding your custom tags (labels) to agent-forwarded logs.']
bugs: ['Don''t instrument certain processes in Azure Linux App Service deployments.','Fix a bug in `run.sh`.']
security: []
---

### Notice

* The .NET agent now allows you to opt-in to adding your custom tags (labels) to agent-forwarded logs. With custom tags on logs, platform engineers can easily filter, search, and correlate log data for faster and more efficient troubleshooting, improved performance, and optimized resource utilization. To learn more about this feature see the [documentation](https://docs.newrelic.com/docs/logs/logs-context/Custom-tags-agent-forwarder-logs).(https://github.com/newrelic/newrelic-dotnet-agent/pull/2831) ([d1e29ea](https://github.com/newrelic/newrelic-dotnet-agent/commit/d1e29eaa5103fede483c7248fed5ace0620c6ccd))

### New features

* Add Distributed Tracing support for Azure Functions HTTPTrigger. ([#2868](https://github.com/newrelic/newrelic-dotnet-agent/issues/2868)) ([0278836](https://github.com/newrelic/newrelic-dotnet-agent/commit/0278836fc9b538f9eceabd47af7b5da46ed13274))
* The .NET agent now allows you to opt-in to adding your custom tags (labels) to agent-forwarded logs. With custom tags on logs, platform engineers can easily filter, search, and correlate log data for faster and more efficient troubleshooting, improved performance, and optimized resource utilization. To learn more about this feature see the [documentation](https://docs.newrelic.com/docs/logs/logs-context/Custom-tags-agent-forwarder-logs).(https://github.com/newrelic/newrelic-dotnet-agent/pull/2831) ([d1e29ea](https://github.com/newrelic/newrelic-dotnet-agent/commit/d1e29eaa5103fede483c7248fed5ace0620c6ccd))

### Fixes

* Don't instrument certain processes in Azure Linux App Service deployments. Resolves [#2871](https://github.com/newrelic/newrelic-dotnet-agent/issues/2871). ([7ed945b](https://github.com/newrelic/newrelic-dotnet-agent/commit/7ed945b659be8a670d27c5a266738ffd5a712a41))
* Fix a bug in `run.sh`. Resolves [#2887](https://github.com/newrelic/newrelic-dotnet-agent/issues/2887) ([#2888](https://github.com/newrelic/newrelic-dotnet-agent/issues/2888)) ([df17cfd](https://github.com/newrelic/newrelic-dotnet-agent/commit/df17cfdf6d777ed623c437c2f9dd5dfab3651260))

### Checksums
| File | SHA - 256 Hash |
| ---| ---|
| newrelic-dotnet-agent-10.34.0-1.x86_64.rpm | 6D79C44A4C2E96286CF3F1C12E07838DC65CE9A474CC86407F6B4DF6D346656C |
| newrelic-dotnet-agent_10.34.0_amd64.deb | 444BF2BA93B0E95FCE916CE7BFCA26A9A221830B368D86F1B738B47B50F38D1F |
| newrelic-dotnet-agent_10.34.0_amd64.tar.gz | 338120A20039D49F27CB48D1CB940540660F0F9FB4BBEC98CAF097810ED8C88B |
| newrelic-dotnet-agent_10.34.0_arm64.deb | 371269E295ECB425FAE120DF2E7AB0A1AFA2520A451B8A83BE16BCBE0ABD3957 |
| newrelic-dotnet-agent_10.34.0_arm64.tar.gz | A008918C7A97D988023DBE43E46C4A118EDB2073E25DF9D95B3794F71E7674B5 |
| NewRelicDotNetAgent_10.34.0_x64.msi | 8B889669F8CB6DBD437D626B3C4252B5C95C223FACEB3CFB02544C62FCAFDE5B |
| NewRelicDotNetAgent_10.34.0_x64.zip | 629A6FD8A3F856AE40F6F77C60DF17321E92003B44F88960CA1A32734B269455 |
| NewRelicDotNetAgent_10.34.0_x86.msi | E1BE19B96B41C3640067FDD20DCCF5DDB43ED38DA0786C34A2B8D0DE8F4459A6 |
| NewRelicDotNetAgent_10.34.0_x86.zip | 5292B803BCB1D01F0F50F74383D2D37EB9F5874CDD5FD7C3822B8F695789F7AE |


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

Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
---
title: Agregue una etiqueta personalizada al registro de la aplicación
tags:
- Logs
- Enable log management in New Relic
- Logs in context
- Tag
- Labels
metaDescription: 'For apps monitored by New relic language agents, learn how to add custome tags (labels) to logs.'
freshnessValidatedDate: never
translationType: machine
---

New Relic APM ahora le permite optar por agregar su etiqueta personalizada al registro reenviado por el agente. Con una etiqueta de registro personalizada, DevOps y los ingenieros de plataformas pueden filtrar, buscar y correlacionar datos log para una resolución de problemas más rápida y eficiente, un rendimiento mejorado y una utilización optimizada de los recursos.

## Habilitar etiqueta personalizada (etiquetas) en el registro de aplicación

Cuando está habilitado, el agente de lenguaje de New Relic agrega todas las etiquetas personalizadas al registro reenviado por el agente.

Idiomas admitidos:

* [.NET](/docs/apm/agents/net-agent/configuration/net-agent-configuration)
* [Ruby](/docs.newrelic.com/docs/apm/agents/ruby-agent/configuration/ruby-agent-configuration/)
* Go: próximamente
* Java: próximamente
* Node.js: próximamente
* PHP: próximamente
* Python: próximamente
Loading

0 comments on commit 8c1425c

Please sign in to comment.