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 committed Feb 7, 2025
2 parents ad455eb + 6c4c747 commit d8ad38a
Show file tree
Hide file tree
Showing 17 changed files with 1,451 additions and 25 deletions.
6 changes: 3 additions & 3 deletions src/content/docs/data-apis/manage-data/view-system-limits.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -76,7 +76,7 @@ For every major limit incident, New Relic creates an [`NrIntegrationError` event
<tbody>
<tr>
<td>
category
`category`
</td>

<td>
Expand All @@ -86,7 +86,7 @@ For every major limit incident, New Relic creates an [`NrIntegrationError` event

<tr>
<td>
limitName
`limitName`
</td>

<td>
Expand All @@ -96,7 +96,7 @@ For every major limit incident, New Relic creates an [`NrIntegrationError` event

<tr>
<td>
message
`message`
</td>

<td>
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,9 @@ freshnessValidatedDate: never

<Callout variant="important">
Enable the [AWS CloudWatch Metric Streams integration](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) to monitor all CloudWatch metrics from your AWS services, including custom namespaces. Individual integrations are no longer our recommended option.

Currently, AWS CloudWatch metrics support only AWS Glue Spark ETL jobs. They do not support AWS Glue Python Shell jobs. An active feature request has been submitted to the AWS Glue team to include this support.

</Callout>

New Relic offers an integration for reporting your [AWS Glue](https://aws.amazon.com/glue/) data. This document explains how to activate this integration and describes the data that can be reported.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -176,7 +176,7 @@ First, you'll define a template variable. This is the variable that you'll use i
* <DNT>**Query**</DNT>: You can write a query that will return a dynamic list of options used in the dropdown menu. For example, the following query would return a dynamic list of `country` values:

```sql
SELECT uniques(countryCode) FROM PageAction since 2 days ago
SELECT uniques(countryCode) FROM PageAction SINCE 2 days ago
```

For rules and tips on writing queries, see [Query-type variables](#query-variable-rules).
Expand Down Expand Up @@ -336,8 +336,8 @@ FROM PageAction SELECT uniques(countryCode)
```

```sql
-- you can use the second param to define the maximum number of results to be listed.
From PageAction select uniques(countryCode, 10000) --> this will return up to 10k results
-- you can use the second param to define the maximum number of results to be listed.
FROM PageAction SELECT uniques(countryCode, 10000) --> this will return up to 10k results
```

With [`keyset`](/docs/nrql/nrql-syntax-clauses-functions/#keyset):
Expand Down Expand Up @@ -577,7 +577,7 @@ Here are some different types of template variable implementations.
Then you'd create a widget with the following query:

```sql
SELECT percentile(duration,{{percentile}}) FROM PageAction
SELECT percentile(duration, {{percentile}}) FROM PageAction
```

<img
Expand All @@ -594,7 +594,8 @@ Here are some different types of template variable implementations.
To use variables for filtering you only need to add the created variable on the right side of a `WHERE` clause, like this:

```sql
SELECT countryCode, city FROM PageAction WHERE countryCode IN ({{countryCode}})
SELECT countryCode, city FROM PageAction
WHERE countryCode IN ({{countryCode}})
```

<img
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -249,6 +249,8 @@ The Markdown editor contains a <DNT>**Markdown**</DNT> pane, where you enter you
You can also edit existing content by clicking the ellipses <Icon name="fe-more-horizontal"/>
icon on any Markdown widget and selecting <DNT>**Edit**</DNT>.

The Markdown widget now supports Mermaid diagrams. For more information, refer to [Mermaid syntax reference](https://mermaid.js.org/intro/syntax-reference.html#diagram-syntax).

Learn more about what you can do with the Markdown widget in the short video below (approx. 3:11 minutes):

<Video
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
---
subject: .NET agent
releaseDate: '2025-02-05'
version: 10.36.0
downloadLink: 'https://download.newrelic.com/dot_net_agent/latest_release'
features: ['Add .NET 8+ support for System.Data.Odbc.','Add support for instrumenting OpenSearchClient requests.']
bugs: ['Add Azure Function app name prefix to `faas.name` attribute in Azure Function transactions.','Custom attribute values of type float and decimal were not serialized correctly.','Improve error handling in AWS account ID parsing logic.']
security: []
---

### New features

* Add .NET 8+ support for System.Data.Odbc ([#2948](https://github.com/newrelic/newrelic-dotnet-agent/issues/2948)) ([7ee9825](https://github.com/newrelic/newrelic-dotnet-agent/commit/7ee9825b21fbd442c066ccfe9040a0bd129840dd))
* Add support for instrumenting OpenSearchClient requests. ([#2956](https://github.com/newrelic/newrelic-dotnet-agent/issues/2956)) ([4309938](https://github.com/newrelic/newrelic-dotnet-agent/commit/4309938c5d0593029398d7658a37b5ebe78c283c))

### Fixes

* Add Azure Function app name prefix to `faas.name` attribute in Azure Function transactions. ([#2973](https://github.com/newrelic/newrelic-dotnet-agent/issues/2973)) ([80d4c76](https://github.com/newrelic/newrelic-dotnet-agent/commit/80d4c7619cbe8876b0ceacbf561b55b458a1189b))
* Custom attribute values of type float and decimal were not serialized correctly. ([#2975](https://github.com/newrelic/newrelic-dotnet-agent/issues/2975)) ([8812fe1](https://github.com/newrelic/newrelic-dotnet-agent/commit/8812fe1127270937fa869370443afff7aeb862e3))
* Improve error handling in AWS account ID parsing logic ([#2984](https://github.com/newrelic/newrelic-dotnet-agent/issues/2984)) ([9b66750](https://github.com/newrelic/newrelic-dotnet-agent/commit/9b66750e3343bccd10f269701d257b056eb660cc))

### Checksums
| File | SHA - 256 Hash |
| ---| ---|
| newrelic-dotnet-agent-10.36.0-1.x86_64.rpm | 91BA7176F99AEE0BC3817F00371A13481356F63E000E57141FBEE2A7BAAFB68B |
| newrelic-dotnet-agent_10.36.0_amd64.deb | 807C95FE01ECAD96C7120D2264DBADFF9FBD4BA761B574BEE08D8CC0268A69E4 |
| newrelic-dotnet-agent_10.36.0_amd64.tar.gz | 9CA4753487DF4B87C99C5A64D9CF772BFF100EABD90F964682FDD4ECB4D87CD8 |
| newrelic-dotnet-agent_10.36.0_arm64.deb | E6DC9B2395CEEF228A53960321A9B41E056CA967805610E414973A4B6E3A30C9 |
| newrelic-dotnet-agent_10.36.0_arm64.tar.gz | F8AE80A25CE634BB4307D0035ABDC3DB8D5B11835C4BE3E353AF62F694409884 |
| NewRelicDotNetAgent_10.36.0_x64.msi | 52D24B0B05449CB09BF01DD659FCD4A50F5C10BF243BD248B16935A9660B8BB7 |
| NewRelicDotNetAgent_10.36.0_x64.zip | 22CF5D61002EFB0E7DD04B1E03F09ED0B2143CAF8D01C95D9C02EF21025EA5AF |
| NewRelicDotNetAgent_10.36.0_x86.msi | F66B1708D384D48603205768CA7AECACD700673CA86F361D9C7D0370944FDFEA |
| NewRelicDotNetAgent_10.36.0_x86.zip | 15588F3BC4D33756E117BC8680B3B8AAE02757751443ADBDA88EF0E75ABD09A1 |


### 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
Expand Up @@ -5,7 +5,7 @@ freshnessValidatedDate: '2024-11-04T00:00:00.000Z'
translationType: machine
---

monitoreo de IA es nuestra solución de Monitoreo del rendimiento de aplicaciones (APM)) para IA. Cuando habilita el monitoreo de IA, nuestro agente APM puede brindarle visibilidad de extremo a extremo del rendimiento, el costo y la calidad de [los modelos compatibles](/docs/ai-monitoring/compatibility-requirements-ai-monitoring) de proveedores como OpenAI y BedRock. Explore cómo el usuario interactúa con un asistente de IA, profundice en detalles a nivel de traza sobre la respuesta de un modelo a un evento de IA y compare el rendimiento de diferentes modelos en entornos de aplicaciones.
monitoreo de IA es nuestra solución de Monitoreo del rendimiento de aplicaciones (APM)) para IA. Cuando habilita el monitoreo de IA, nuestro agente APM puede brindarle visibilidad de extremo a extremo del rendimiento, el costo y la calidad de [los modelos compatibles](/docs/ai-monitoring/compatibility-requirements-ai-monitoring) de proveedores como OpenAI, Bedrock y DeepSeek. Explore cómo el usuario interactúa con un asistente de IA, profundice en detalles a nivel de traza sobre la respuesta de un modelo a un evento de IA y compare el rendimiento de diferentes modelos en entornos de aplicaciones.

<img title="Trace waterfall for AI monitoring" alt="A screenshot that shows the trace waterfall page for an individual AI response" src="/images/ai_screenshot-full_ai-responses-intro-page.webp" />

Expand All @@ -23,7 +23,7 @@ Cuando su asistente de IA recibe un símbolo y devuelve una respuesta, el agente
* Realice un seguimiento de las solicitudes y respuestas que pasan por cualquiera de nuestros modelos compatibles
* Correlacionar comentarios negativos o positivos sobre una respuesta de su usuario final

Puede acceder a toda esta información y más desde la plataforma New Relic , luego crear alertas y paneles de control para ayudarlo a gestionar eficazmente sus datos de IA y mejorar el rendimiento.
Puede acceder a toda esta información y más desde la plataforma New Relic , luego crear alertas y dashboards de control para ayudarlo a gestionar eficazmente sus datos de IA y mejorar el rendimiento.

## Mejore el rendimiento de la IA con el monitoreo de IA [#improve-performance]

Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,171 @@
---
title: Webhook de New Relic para el flujo de trabajo de Microsoft Teams
tags:
- Alerts
- Incident intelligence
- New Relic webhook for Microsoft Teams workflow
metaDescription: Read about how to add a New Relic webhook for Microsoft Teams workflow.
freshnessValidatedDate: never
translationType: machine
---

Microsoft retirará el servicio de conectores basado en webhooks de Microsoft 365 en Teams a fines de 2025. Para continuar recibiendo la notificación de alerta de New Relic, puede crear un flujo de trabajo dentro de Microsoft Teams usando la aplicación flujo de trabajo. Este documento proporciona instrucciones para actualizar sus destinos de alerta y flujo de trabajo de New Relic para garantizar una transición fluida y alertas ininterrumpidas en sus canales de Teams. Para obtener más información sobre cómo retirar los servicios de Conectores de Office 365, consulte [el blog para desarrolladores de Microsoft](https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/).

**Prerrequisitos:**

* Cree un nuevo flujo de trabajo en Microsoft Teams para las alertas de New Relic. Luego de crear el flujo de trabajo, copie la URL de la solicitud POST. Necesitarás esta URL en New Relic. Para obtener más información, consulte [la documentación de Microsoft para crear un flujo de trabajo en Teams](https://support.microsoft.com/en-us/office/create-incoming-webhooks-with-workflows-for-microsoft-teams-8ae491c7-0394-4861-ba59-055e33f75498).

**Para agregar un webhook de New Relic para el flujo de trabajo de Microsoft Teams:**

1. Actualizar el destino del webhook existente:

1. Vaya a **[one.newrelic.com &gt; All capabilities](https://one.newrelic.com/all-capabilities) &amp;gt; Alerts &amp;gt; Enrich and Notify &amp;gt; Destinations**.
2. Haga clic en el destino del webhook requerido vinculado a Microsoft Teams para editarlo.
3. Luego de crear un flujo de trabajo en Teams, en el campo **Endpoint URL**, reemplace la URL existente con una nueva URL.
<img title="Destinations update page" alt="Destinations update page." src="/images/alerts_destination_enpointurl.webp" />
4. Haga clic en **Update destination**.

2. Actualizar el flujo de trabajo del webhook existente:

1. Vaya a **[one.newrelic.com &gt; All capabilities](https://one.newrelic.com/all-capabilities) &amp;gt; Alerts &amp;gt; Enrich and Notify &amp;gt; Workflows**.
2. Para editar la carga útil de notificación, haga clic en el flujo de trabajo requerido vinculado con el destino.
<img title="Workflow update page" alt="Workflow update page." src="/images/alerts_workflow_payload.webp" />
3. En la pantalla <DNT>Edit notification message</DNT> , en el campo **Template** , copie y pegue la siguiente carga útil:

```json
{
"type": "message",
"attachments": [
{
"contentType": "application/vnd.microsoft.card.adaptive",
"contentUrl": null,
"content": {
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
"type": "AdaptiveCard",
"version": "1.2",
"msteams": { "width": "full" },
"body": [
{
"type": "ColumnSet",
"columns": [

{
"type": "Column",
"items": [
{
"type": "Image",
"style": "Person",
"url": "https://avatars.slack-edge.com/2022-06-02/3611814361970_f6a28959c2e7258660ea_512.png",
"size": "Small"
}
],
"width": "auto"
},

{
"type": "Column",
"items": [
{
"type": "TextBlock",
"size": "large",
"weight": "bolder",
"text": "{{ priorityText }} priority issue is {{#if issueClosedAt}}CLOSED{{else}}{{#if issueAcknowledgedAt}}ACKNOWLEDGED{{else}}ACTIVATED{{/if}}{{/if}}"
},
{
"type": "TextBlock",
"size": "large",
"wrap": "true",
"maxLines": "2",
"weight": "bolder",
"text": "[{{ issueTitle }}]({{ issuePageUrl }})"
}
],
"width": "stretch"
}
]
},
{{#if accumulations.conditionDescription.[0]}}
{
"type": "TextBlock",
"text": {{ json accumulations.conditionDescription.[0] }},
"wrap": true
},
{{/if}}
{{#eq "Not Available" violationChartUrl}}
{{else}}
{
"type": "Image",
"url": {{ json violationChartUrl }}
},
{{/eq}}
{
"type": "FactSet",
"facts": [
{
"title": "*Impacted entities:*",
"value": "{{#each entitiesData.names}}{{#lt @index 5}}{{this}}{{#unless @last}},{{/unless}}{{/lt}}{{/each}}"
},
{{#if accumulations.policyName }}
{
"title": "*Policy:*",
"value": {{ json accumulations.policyName.[0]}}
},
{{/if}}
{{#if accumulations.conditionName }}
{
"title": "*Condition:*",
"value": {{ json accumulations.conditionName.[0]}}
},
{{#eq impactedEntitiesCount 1}}
{{else}}
{
"title": "*Total Incidents:*",
"value": {{ json impactedEntitiesCount}}
},
{{/eq}}
{{/if}}
{
"title": "Workflow Name:",
"value": {{ json workflowName }}
}
]
},
{
"type": "ActionSet",
"actions": [
{
"type": "Action.OpenUrl",
"title": "📥 Acknowledge",
"url": {{ json issueAckUrl }}
},
{
"type": "Action.OpenUrl",
"title": "✔️ Close",
"url": {{ json issueCloseUrl }}
}
{{#if accumulations.deepLinkUrl}}
,{
"type": "Action.OpenUrl",
"title": "🔎 View Query",
"url": {{ json accumulations.deepLinkUrl.[0] }},
"mode": "secondary"
}
{{/if}}
{{#if accumulations.runbookUrl}}
,{
"type": "Action.OpenUrl",
"title": "📕 View Runbook",
"url": {{ json accumulations.runbookUrl.[0] }},
"mode": "secondary"
}
{{/if}}
]
}
]
}
}
]
}
```

4. Haga clic en **Save message**.
Loading

0 comments on commit d8ad38a

Please sign in to comment.