feat(profiling): document how to work around broken fleet policies (#2539)

add known issue about broken profiling endpoint on cluster upgrade

provide workaround steps on how to delete the broken policies

Closes #1860

---------

Co-authored-by: Benjamin Ironside Goldstein <[email protected]>

Author: kruskall

release-notes/elastic-observability/known-issues.md

@@ -102,4 +102,30 @@ For more information, check:
 - [#220339](https://github.com/elastic/kibana/issues/220339)
 - [#220342](https://github.com/elastic/kibana/issues/220342)
 
-::::
+::::
+
+::::{dropdown} Profiling Collector and Symbolizer endpoints are not configured after upgrading a cluster
+
+Applies to: {{stack}} 9.x, 8.x
+
+**Details**
+
+After upgrading a cluster, Collector and Symbolizer endpoints may not be configured even when Universal Profiling is enabled in Kibana and the "Add data" instructions appear on the Universal Profiling landing page.
+
+**Workaround**
+
+1. Run the following query to retrieve the `id`s of the `elastic-universal-profiling-collector` and `elastic-universal-profiling-symbolizer` package policies:
+
+    ```sh
+    GET kbn:/api/fleet/package_policies
+    ```
+
+2. Delete the package policies:
+
+    ```sh
+    DELETE kbn:/api/fleet/package_policies/<elastic-universal-profiling-collector-id>?force=true
+    DELETE kbn:/api/fleet/package_policies/<elastic-universal-profiling-symbolizer-id>?force=true
+    ```
+
+
+::::