Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Profiling: Drop known issues section about no longer supported versions #4041

Merged
merged 1 commit into from
Jul 1, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 0 additions & 25 deletions docs/en/observability/profiling-get-started.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -84,31 +84,6 @@ If you're upgrading from a previous version with Universal Profiling enabled, se
IMPORTANT: When upgrading, you must remove all existing profiling data.
We still recommend upgrading as the latest version contains several improvements and new features.

[discrete]
[[profiling-upgrade-known-issues]]
==== Known issue when configuring data ingestion

If your {ecloud} deployment originated from version 7.x or earlier and is currently running a version between 8.9.0 and 8.10.2, you may encounter a problem while trying to enable Universal Profiling.

Specifically, clicking the *Set up Universal Profiling* button triggers an error message that reads `Error while setting up Universal Profiling`.
Upgrade to version *8.10.3* or more recent to fix this issue.


If you previously enabled Universal Profiling in {ecloud} version 8.9.0, and you're re-executing the setup, you may also encounter
Copy link
Contributor

@rockdaboot rockdaboot Jun 26, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In theory, this still happen when upgrading from an older version to 8.15 ("If upgrading does not solve the issue, complete the following step").
I am thinking of that has been reported recently

[instance-0000000003] Aborting index creation as index [.profiling-returnpads-private-v001] is considered too old.

this error. If upgrading to 8.10.3 does not solve the issue, complete the following step.


Open *Dev Tools* from the navigation menu and execute the following command:


WARNING: When running the following command, customizations of APM and Fleet configurations will be erased.

[source,console]
----
POST kbn:/internal/fleet/reset_preconfigured_agent_policies/policy-elastic-agent-on-cloud
----


[discrete]
[[profiling-install-profiling-agent]]
== Install the Universal Profiling Agent
Expand Down
Loading