-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #19947 from newrelic/daily-release/02-11-25-morning
Daily release/02 11 25 morning
- Loading branch information
Showing
16 changed files
with
263 additions
and
32 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
14 changes: 14 additions & 0 deletions
14
...es/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6088.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
13 changes: 13 additions & 0 deletions
13
...es/mobile-apps-release-notes/new-relic-ios-release-notes/new-relic-ios-6089.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
89
src/content/whats-new/2025/02/whats-new-01-31-synthetics-ip.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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/). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.