Skip to content

Commit

Permalink
Merge pull request #11644 from bpeckNR/LegacyUpgradeCleanup
Browse files Browse the repository at this point in the history
chore(removeLegacy): Removed legacy runtime upgrade details
  • Loading branch information
rhetoric101 authored Feb 21, 2023
2 parents 80c845c + 18e00e8 commit 6aed3d0
Showing 1 changed file with 6 additions and 83 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -29,90 +29,13 @@ Read on to learn how to:

## Use different runtimes environments [#how_to]

<CollapserGroup>
<Collapser
id="NewUpgrade"
title={<>Upgrade to Chrome 100, Node.js 16, or newer</>}
>

Existing monitors default to the runtime used at their time of creation. To prevent your critical monitors from breaking during future end of life processes, we recommend you convert your public monitors sooner rather than later. To convert:

1. Go to **[one.newrelic.com](https://one.newrelic.com/all-capabilities) > Synthetics**, then select the monitor you want to upgrade.
2. From the **Settings** tab, click **General**.
3. Use the dropdown menu to switch the current runtime version.
4. Click **Validate** to check that your monitors function in the new runtime. Make any script modifications if needed.
5. Save.

</Collapser>

<Collapser
id="LegacyUpgrade"
title={<>Switch between legacy runtimes</>}
>
Existing monitors default to the runtime used at their time of creation. To prevent your critical monitors from breaking during future end of life processes, we recommend you convert your public monitors sooner rather than later. To convert:

To ensure your monitors have access to new features and perform as expected, upgrade your monitors whenever you see the **Upgrade monitors** button. You can also upgrade your monitors by going to **[one.newrelic.com](https://one.newrelic.com/all-capabilities) > Synthetic monitoring >Upgrade monitors**.

When you select **Upgrade monitors**, here are the options:

When editing your scripted monitors, you can click the **Validate** button to check if your monitors are compatible with the latest runtime. The validation process allows you to correct any errors that the latest runtime might cause with existing monitors before your monitors are upgraded.

When you select **Upgrade monitors**, here are the options:

<table>
<thead>
<tr>
<th>
Task
</th>

<th>
Description
</th>
</tr>
</thead>

<tbody>
<tr>
<td>
Upgrade an incompatible monitor
</td>

<td>
If a monitor appears under **Incompatible monitors**:

1. Select the monitor in the **Name** column, which opens the individual monitor so you can view your scripts.
2. Select **Validate latest** and correct any errors with your monitor script.
3. When the monitor is validated successfully, select **Upgrade**.
</td>
</tr>

<tr>
<td>
Upgrade any validated monitors
</td>

<td>
If you have some passing monitors, upgrade them by selecting **Upgrade all passing monitors to latest runtime**.
</td>
</tr>

<tr>
<td>
Upgrade all monitors (including failing monitors)
</td>

<td>
<Callout variant="caution">
Upgrading without validation may cause monitor outages.
</Callout>

If you have some failing monitors, you can skip validation and correct errors later by selecting **Upgrade all monitors on account to latest runtime**.
</td>
</tr>
</tbody>
</table>
</Collapser>
</CollapserGroup>
1. Go to **[one.newrelic.com](https://one.newrelic.com/all-capabilities) > Synthetics**, then select the monitor you want to upgrade.
2. From the **Settings** tab, click **General**.
3. Use the dropdown menu to switch the current runtime version.
4. Click **Validate** to check that your monitors function in the new runtime. Make any script modifications if needed.
5. Save.

## View synthetic monitoring upgrade history [#query]

Expand Down

0 comments on commit 6aed3d0

Please sign in to comment.