Skip to content

Commit

Permalink
Merge pull request #19947 from newrelic/daily-release/02-11-25-morning
Browse files Browse the repository at this point in the history
Daily release/02 11 25 morning
  • Loading branch information
WriteMayur authored Feb 11, 2025
2 parents 2d7f50f + bebb24d commit 3b87b9d
Show file tree
Hide file tree
Showing 16 changed files with 263 additions and 32 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -476,4 +476,4 @@ Additional restrictions include:

## Restricted metric values [#restricted-metric-values]

Any metric data submitted to the Metric API with a `value` equal to `NaN` (not a number), `positive infinity`, or `negative infinity` will be dropped.
Any metric data submitted to the Metric API with a `value` equal to `NaN` (not a number), `positive infinity`, or `negative infinity` will be dropped. Non-finite values may cause [`NrIntegrationError`](https://docs.newrelic.com/docs/data-apis/ingest-apis/metric-api/troubleshoot-nrintegrationerror-events/) events to be emitted.
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
---
subject: Mobile app for iOS
releaseDate: '2025-01-23'
version: '6.8.8'
downloadLink: 'https://itunes.apple.com/us/app/new-relic/id594038638?mt=8'
redirects:
- /docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6088
---

### Analytics & Fixes

* Added Page Session Tracking Events
* Added click events
* Bug fix related to incorrect page session creation via bottom tabs.
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
---
subject: Mobile app for iOS
releaseDate: '2025-02-10'
version: '6.8.9'
downloadLink: 'https://itunes.apple.com/us/app/new-relic/id594038638?mt=8'
redirects:
- /docs/release-notes/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6089
---

### Analytics & Fixes
* Measure time taken by pages of Top Flows in :Requesting and Loading API Response, and Page Rendering
* Page Session Time Instrumentation for Explorer and Logs
* Fix to stop the Page Session when app goes to background and start again when app comes to foreground
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,18 @@ Minions are deployed on servers, and the agents are activated using non-personal

IP addresses for released locations are subject to change. If a change is needed, we'll attempt to proactively notify customers prior to any changes via e-mail. You can also check the [Support Forum](https://discuss.newrelic.com/) for updates. The IP ranges listed are reserved for use by New Relic and cannot be used by anyone else.

<Callout variant="important">
If you are adding Synthetics traffic to the allowlist from any public locations using IP addresses, you must update your allowlists with the new IP ranges. New IP ranges to allowlist:

* 152.38.128.0/19
* 212.32.0.0/20
* 64.251.192.0/20

<DNT>**If no action is taken**</DNT>

If you do not update your allowlists by **April 14, 2025**, your Synthetics checks may fail to connect to your applications, which may result in failed connections and trigger alerts.
</Callout>

<table style={{ width: "300px" }}>
<thead>
<tr>
Expand All @@ -54,6 +66,10 @@ IP addresses for released locations are subject to change. If a change is needed
</thead>
</table>

<Callout variant="important">
The IP range list in JSON format will change after **April 14, 2025** as some older IPs will be replaced by the new ranges specified above. Please ensure you whitelist the newly mentioned ranges.
</Callout>

## Public minion locations and location labels [#location]

The following table cross-references the synthetic's public minion locations with their location labels. You can [query](/docs/query-your-data) the `location` and `locationLabel` attributes from the [SyntheticCheck](/docs/insights/explore-data/attributes/synthetics-default-attributes-insights#syntheticcheck-table) and [SyntheticRequest](/docs/insights/explore-data/attributes/synthetics-default-attributes-insights#syntheticrequest-table) events.
Expand Down
89 changes: 89 additions & 0 deletions src/content/eol/2025/02/eol-01-31-25-synthetics-ip.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,89 @@
---
title: 'Update to New Relic Synthetics IP ranges'
summary: 'Updating Synthetics IP ranges.'
publishDate: '2025-02-11'
eolEffectiveDate: '2025-04-14'
---

In order to ensure the best service to our customers, New Relic will change the IP ranges for New Relic Synthetics checks **effective April 14, 2025.**

If Synthetics traffic is part of your allowlist, **you will need to update your configurations** to maintain monitor connectivity.

Failure to update your allowlist by **April 14, 2025**, may result in your synthetic checks failing to connect to your applications, potentially causing disruptions and alerts.

**NOTE:** If you do not allowlist by IP range, no action is required.

## What's changing?
We will be migrating the IP address range for the New Relic service used by Synthetics public locations to align with our standard IP ranges used across other data ingest.

## What action is required?

* Before **April 14, 2025**, update your allow lists with the new IP ranges provided below.

**New IP ranges to allowlist:**

* `152.38.128.0/19`

* `212.32.0.0/20`

* `64.251.192.0/20`

* After **April 14, 2025**, remove the old IP ranges from the allowlist. Failure to do so may result in failed connections and trigger alerts.

**Old IP ranges to remove:** Please refer to the table below for a complete list of current IP ranges **that need to be removed after April 14, 2025**.

<table>
<thead>
<tr>
<th>Region Name</th>
<th>Region Location</th>
<th>Current CIDR Block Range</th>
</tr>
</thead>
<tbody>
<tr>
<td>us-east-1</td>
<td>Washington, DC, USA</td>
<td>44.202.178.0/24 <br>44.202.180.0/23 <br> 44.210.68.0/24 <br> 44.210.110.0/25</td>
</tr>
<tr>
<td>us-east-2</td>
<td>Columbus, OH, USA</td>
<td>3.145.224.0/24 <br> 3.145.225.0/25 <br> 3.145.234.0/24</td>
</tr>
<tr>
<td>us-west-1</td>
<td>San Francisco, CA, USA</td>
<td>3.101.204.0/23 <br> 3.101.212.0/24 <br> 3.101.209.192/26</td>
</tr>
<tr>
<td>us-west-2</td>
<td>Portland, OR, USA</td>
<td>35.89.46.0/23 <br> 35.92.27.0/24</td>
</tr>
<tr>
<td>ap-southeast-2</td>
<td>Sydney, AU</td>
<td>3.26.252.0/24 <br> 3.26.245.128/25 <br> 3.27.51.0/25</td>
</tr>
<tr>
<td>eu-central-1</td>
<td>Frankfurt, DE</td>
<td>3.71.170.0/24 <br> 3.71.103.96/27 <br> 3.75.4.128/25</td>
</tr>
<tr>
<td>eu-west-1</td>
<td>Dublin, IE</td>
<td>3.251.231.0/24 <br> 3.251.230.64/26 <br> 3.252.47.0/25</td>
</tr>
<tr>
<td>eu-west-2</td>
<td>London, England, UK</td>
<td>13.40.201.0/24 <br> 13.40.208.0/25 <br> 13.41.206.128/25 <br> 13.41.206.64/26</td>
</tr>
</tbody>
</table>

## Additional Support

We understand that these changes may require some adjustments to your routine. Please know that we’re committed to supporting you throughout this process. If you have any questions or need further assistance, please don't hesitate to reach out to our [support team](https://support.newrelic.com/s/).
89 changes: 89 additions & 0 deletions src/content/whats-new/2025/02/whats-new-01-31-synthetics-ip.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,89 @@
---
title: 'Update to New Relic Synthetics IP ranges'
summary: 'Updating Synthetics IP ranges change'
releaseDate: '2025-02-11'
learnMoreLink: 'https://docs.newrelic.com/docs/new-relic-solutions/get-started/networks/#synthetics'
---

In order to ensure the best service to our customers, New Relic will change the IP ranges for New Relic Synthetics checks **effective April 14, 2025.**

If Synthetics traffic is part of your allowlist, **you will need to update your configurations** to maintain monitor connectivity.

Failure to update your allowlist by **April 14, 2025**, may result in your synthetic checks failing to connect to your applications, potentially causing disruptions and alerts.

**NOTE:** If you do not allowlist by IP range, no action is required.

## What’s changing?
We will be migrating the IP address range for the New Relic service used by Synthetics public locations to align with our standard IP ranges used across other data ingest.

## What action is required?

* Before **April 14, 2025**, update your allow lists with the new IP ranges provided below.

**New IP ranges to allowlist:**

* `152.38.128.0/19`

* `212.32.0.0/20`

* `64.251.192.0/20`

* After **April 14, 2025**, remove the old IP ranges from the allowlist. Failure to do so may result in failed connections and trigger alerts.

**Old IP ranges to remove:** Please refer to the table below for a complete list of current IP ranges **that need to be removed after April 14, 2025**.

<table>
<thead>
<tr>
<th>Region Name</th>
<th>Region Location</th>
<th>Current CIDR Block Range</th>
</tr>
</thead>
<tbody>
<tr>
<td>us-east-1</td>
<td>Washington, DC, USA</td>
<td>44.202.178.0/24 <br>44.202.180.0/23 <br> 44.210.68.0/24 <br> 44.210.110.0/25</td>
</tr>
<tr>
<td>us-east-2</td>
<td>Columbus, OH, USA</td>
<td>3.145.224.0/24 <br> 3.145.225.0/25 <br> 3.145.234.0/24</td>
</tr>
<tr>
<td>us-west-1</td>
<td>San Francisco, CA, USA</td>
<td>3.101.204.0/23 <br> 3.101.212.0/24 <br> 3.101.209.192/26</td>
</tr>
<tr>
<td>us-west-2</td>
<td>Portland, OR, USA</td>
<td>35.89.46.0/23 <br> 35.92.27.0/24</td>
</tr>
<tr>
<td>ap-southeast-2</td>
<td>Sydney, AU</td>
<td>3.26.252.0/24 <br> 3.26.245.128/25 <br> 3.27.51.0/25</td>
</tr>
<tr>
<td>eu-central-1</td>
<td>Frankfurt, DE</td>
<td>3.71.170.0/24 <br> 3.71.103.96/27 <br> 3.75.4.128/25</td>
</tr>
<tr>
<td>eu-west-1</td>
<td>Dublin, IE</td>
<td>3.251.231.0/24 <br> 3.251.230.64/26 <br> 3.252.47.0/25</td>
</tr>
<tr>
<td>eu-west-2</td>
<td>London, England, UK</td>
<td>13.40.201.0/24 <br> 13.40.208.0/25 <br> 13.41.206.128/25 <br> 13.41.206.64/26</td>
</tr>
</tbody>
</table>

## Additional Support

We understand that these changes may require some adjustments to your routine. Please know that we’re committed to supporting you throughout this process. If you have any questions or need further assistance, please don't hesitate to reach out to our [support team](https://support.newrelic.com/s/).
3 changes: 2 additions & 1 deletion src/data/whats-new-ids.json
Original file line number Diff line number Diff line change
Expand Up @@ -360,5 +360,6 @@
"/whats-new/2025/01/whats-new-01-17-cross-account-alerts": "43017",
"/whats-new/2025/01/whats-new-03-01-rest-api-keys-eol": "43018",
"/whats-new/2025/01/whats-new-01-22-React18-upgrade": "43019",
"/whats-new/2025/01/whats-new-01-23-msconnector-eol": "43020"
"/whats-new/2025/01/whats-new-01-23-msconnector-eol": "43020",
"/whats-new/2025/02/what-new-10-02-sessions-replay": "43021"
}
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ UIが提供するよりも詳細な情報が必要な場合は、[リソース
<tbody>
<tr>
<td>
カテゴリ
`category`
</td>

<td>
Expand All @@ -79,7 +79,7 @@ UIが提供するよりも詳細な情報が必要な場合は、[リソース

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

<td>
Expand All @@ -89,7 +89,7 @@ UIが提供するよりも詳細な情報が必要な場合は、[リソース

<tr>
<td>
メッセージ
`message`
</td>

<td>
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,8 @@ translationType: machine

<Callout variant="important">
[AWS CloudWatch Metric Streams統合](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/)を有効にして、カスタムネームスペースを含むAWSサービスからのすべてのCloudWatchメトリクスをモニターします。個別の統合は、もはや推奨されるオプションではありません。

現在、 AWS CloudWatchメトリクスはAWS Glue Spark ETL ジョブのみをサポートしています。 AWS Glue Python Shell ジョブはサポートされていません。 このサポートを含めるためのアクティブな機能リクエストが AWS Glue チームに送信されました。
</Callout>

New Relic では、 [AWS Glue](https://aws.amazon.com/glue/) のデータをレポートするための統合を提供しています。このドキュメントでは、この統合を有効にする方法と、レポート可能なデータについて説明します。
Expand All @@ -30,7 +32,7 @@ New Relic では、 [AWS Glue](https://aws.amazon.com/glue/) のデータをレ

## データを見つけて使用する [#find-data]

インテグレーションデータを検索するには、 <DNT>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure > AWS**</DNT>に移動してインテグレーションを選択してください。
インテグレーションデータを検索するには、 <DNT>**[one.newrelic.com &gt; All capabilities](https://one.newrelic.com/all-capabilities) &amp;gt; Infrastructure &amp;gt; AWS**</DNT>に移動してインテグレーションを選択してください。

次の[イベントタイプ](/docs/data-apis/understand-data/new-relic-data-types/#event-data)を使用して、[データのクエリと探索](/docs/using-new-relic/data/understand-data/query-new-relic-data)を行うことができます。

Expand Down Expand Up @@ -402,4 +404,4 @@ New Relic では、 [AWS Glue](https://aws.amazon.com/glue/) のデータをレ
</td>
</tr>
</tbody>
</table>
</table>
Original file line number Diff line number Diff line change
Expand Up @@ -166,7 +166,7 @@ include 変数の制限:
* <DNT>**Query**</DNT>: ドロップダウン メニューで使用されるオプションの動的なリストを返すクエリを作成できます。 たとえば、次のクエリは`country`値の動的なリストを返します。

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

クエリを作成する際の規則とヒントについては、「[クエリ型変数](#query-variable-rules)」を参照してください。
Expand Down Expand Up @@ -317,8 +317,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
```

[`keyset`](/docs/nrql/nrql-syntax-clauses-functions/#keyset)の場合:
Expand Down Expand Up @@ -484,7 +484,7 @@ FROM PageAction SELECT keyset() SINCE 1 day ago
次に、次のクエリを使用してウィジェットを作成します。

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

<img title="Adding the widget for dynamically change the percentile" alt="Adding the widget for dynamically change the percentile" src="/images/dashboards_screenshot-crop_add-widget-dynamic-percentile.webp" />
Expand All @@ -494,7 +494,8 @@ FROM PageAction SELECT keyset() SINCE 1 day ago
フィルタリングに変数を使用するには、次のように、作成した変数を`WHERE`句の右側に追加するだけです。

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

<img title="Use variables to filter" alt="Use variables to filter" src="/images/dashboards_screenshot-crop_variables-to-filter.webp" />
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ UI가 제공하는 것보다 더 자세한 정보를 원하면 [리소스 사용
<tbody>
<tr>
<td>
범주
`category`
</td>

<td>
Expand All @@ -79,7 +79,7 @@ UI가 제공하는 것보다 더 자세한 정보를 원하면 [리소스 사용

<tr>
<td>
제한 이름
`limitName`
</td>

<td>
Expand All @@ -89,7 +89,7 @@ UI가 제공하는 것보다 더 자세한 정보를 원하면 [리소스 사용

<tr>
<td>
메시지
`message`
</td>

<td>
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,8 @@ translationType: machine

<Callout variant="important">
[AWS CloudWatch Metric Streams 통합](/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-metric-stream/) 을 활성화하여 사용자 지정 네임스페이스를 포함하여 AWS 서비스의 모든 CloudWatch 지표를 모니터링합니다. 개별 통합은 더 이상 권장되는 옵션이 아닙니다.

현재 AWS CloudWatch 지표는 AWS Glue Spark ETL 작업만 지원합니다. AWS Glue 웹 Shell 작업은 지원하지 않습니다. 이 지원을 포함하기 위해 AWS Glue 팀에 활성 기능 요청이 제출되었습니다.
</Callout>

New Relic은 [AWS Glue](https://aws.amazon.com/glue/) 데이터 보고를 위한 통합을 제공합니다. 이 문서에서는 이 통합을 활성화하는 방법과 보고할 수 있는 데이터에 대해 설명합니다.
Expand All @@ -30,7 +32,7 @@ AWS Glue 통합에 대한 기본 [폴링](/docs/infrastructure/amazon-integratio

## 데이터 찾기 및 사용 [#find-data]

통합 데이터를 찾으려면 <DNT>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure > AWS**</DNT> 으로 이동하여 통합을 선택하세요.
통합 데이터를 찾으려면 <DNT>**[one.newrelic.com &gt; All capabilities](https://one.newrelic.com/all-capabilities) &amp;gt; Infrastructure &amp;gt; AWS**</DNT> 으로 이동하여 통합을 선택하세요.

다음 [이벤트 유형](/docs/data-apis/understand-data/new-relic-data-types/#event-data) 을 사용 [하여 데이터를 쿼리하고 탐색할](/docs/using-new-relic/data/understand-data/query-new-relic-data) 수 있습니다.

Expand Down Expand Up @@ -402,4 +404,4 @@ AWS Glue 통합에 대한 기본 [폴링](/docs/infrastructure/amazon-integratio
</td>
</tr>
</tbody>
</table>
</table>
Loading

0 comments on commit 3b87b9d

Please sign in to comment.