Created What's new and EOL post for Synthetics IP #19808
Conversation
WIP. Please do not push.
|
Hi @mlakshmiharita 👋 Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days. We will automatically generate a preview of your request, and will comment with a link when the preview is ready (usually 10 to 20 minutes). |
✅ Deploy Preview for docs-website-netlify ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
Updated a table
|
Updated a table
|
|
Table update
|
WIP. Please do not merge. Updating for technical reviews
|
| eolEffectiveDate: '2025-03-31' | ||
| --- | ||
|
|
||
| Effective **March 31, 2025**, the IP ranges for New Relic Synthetics will change as part of our service enhancements. If your systems allowlist Synthetics traffic based on IP ranges, **you will need to update your configurations** to maintain monitor connectivity. Failure to do so may result in failed connections and trigger alerts. |
There was a problem hiding this comment.
If Synthetics traffic is part of your allowlist...
|
|
||
| ## What action is required? | ||
|
|
||
| **If you allowlist Synthetics traffic**, update your allow lists with the new IP ranges provided below before **March 31, 2025**. Failure to do so may result in failed connections and trigger alerts. |
There was a problem hiding this comment.
"Failure to do so may result in failed connections and trigger alerts." Repeated information. It is already there in para 1
| </tbody> | ||
| </table> | ||
|
|
||
| **NOTE:** If you do not allowlist by IP range, no action is required. |
There was a problem hiding this comment.
This should be at the top of the page.
| ## 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? |
There was a problem hiding this comment.
After the sentence on "If you allowlist Synthetics traffic..." add another sentence telling them they dont need to take any action if they dont use allowlist.
Following that, give it as a two-step process.
- Before March 31, 2025, add the new IP ranges to the allowlist.
|
|
||
| Failure to update your allowlist by **March 31, 2025**, may result in your synthetic checks failing to connect to your applications, potentially causing disruptions and alerts. | ||
|
|
||
| ## Next Steps |
There was a problem hiding this comment.
This section is just repeated information. Why do we have this?
Fixed the Vinay comments.
|
WIP. Please do not push. Still with the the technical reviews.