Docs 210

pages/doc/integrations_new_changed.md

@@ -41,7 +41,7 @@ We **deprecated** a number of integrations in October 2023, and moved these inte
 * AWS Lambda Functions
 * nodejs
 
-{% include important.html content= "The deprecated integrations in the list above will reach **end-of-life** in January, 2024 and will be removed from the product. If you are using any of these integrations and need assistance, reach out to our [Technical Support team](wavefront_support_feedback.html)." %}
+{% include important.html content= "The deprecated integrations will reach **end-of-life** in January, 2024 and will be removed from the product. If you are using any of these integrations and need assistance, reach out to our [Technical Support team](wavefront_support_feedback.html)." %}
 
 Also, we made improvements to the following integrations in October 2023:
 

pages/doc/metrics_security.md

@@ -220,13 +220,15 @@ The following annotated screenshot gives an overview of rule management options:
 
 <!---Have to change screenshot to show Save instead of Apply--->
 
+{% include note.html content="With the 2023-45.x release, the metrics security policy moved to a new framework. Therefore, new updates you make to your security policy start from version 1 on the **Version History** page. For details, see [2023-45.x Release Notes](wavefront_release_notes.html#2023-45x-release-notes)." %}
+
 Here's a tour:
 
 1. Click **Version History** to:
   * Revert to an earlier version of the policy.
   * Look at information on who last edited the security policy and when that happened.
 1. Examine the **Metric Prefix** column to see the metrics affected by a rule.
-2. Look at the **Access** column to see whether the rule allows or blocks access.
+1. Look at the **Access** column to see whether the rule allows or blocks access.
 1. Select the check box to the left of a rule to select it, then use the icons above to clone or delete the selected rule.
 1. Select the check boxes to the left of multiple rules to select them, use the icons to indicate changes, and click **Save** to commit the changes.
 1. Click the six-dot icon to explicitly drag a rule where you want it and change the rule prioritization.

pages/doc/wavefront_release_notes.md

@@ -36,6 +36,18 @@ In October, 2023, we start to incrementally [**onboard**](csp_migration.html) al
 
 {% include warning.html content="The Operations for Applications authentication and authorization will be **deprecated** in the future. Therefore, after onboarding to VMware Cloud services, **replace** [your service accounts with server to server apps](csp_migration.html#how-to-replace-a-service-account-with-a-server-to-server-app) and [your Operations for Applications API tokens with VMware Cloud Services access tokens](csp_migration.html#how-to-replace-an-operations-for-applications-api-token-with-a-vmware-cloud-services-access-token), including [the Operations for Application API tokens of your Wavefront proxies](csp_migration.html#how-to-replace-the-operations-for-application-api-token-of-a-wavefront-proxy)." %}
 
+## 2023-45.x Release Notes
+
+### Original and Onboarded Subscriptions
+
+**Metrics Security Policy Version History Update**: With this release, we move the metrics security policy to a new framework. When you update your metrics security policy:
+* The version history is tracked for the new version, and the version history starts from number 1 again. But you don’t lose the previous version history.
+  <br/>Example: In the screenshot below, you have updated the security policy 38 times before this release. When you update the policy after this release, it is numbered as version 1, and you have the older versions listed below it.  
+  ![A screenshot of the version history, which starts with 1 again at the top.](images/metrics_security_policy_new_version_history.png)
+* You won’t be able to revert the metrics security policy to the duplicate version number in the old framework because it will be deactivated. 
+  <br/>Example: In the screenshot below, you don’t see the vertical ellipsis next to number 1 because it is a duplicate value and a version of the old framework.
+  ![A screenshot of the version history, which starts with 1 again at the top.](images/metrics_security_policy_revert_deactivated.png)
+
 ## 2023-40.x Release Notes
 
 ### Original and Onboarded Subscriptions