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.

Sign up for GitHub

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: Updates to troubleshooting #3329

Merged
merged 3 commits into from
Nov 7, 2023
Merged

Profiling: Updates to troubleshooting #3329

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a4a251f
Profiling: Replace APM server with Collector in Troubleshooting
christos68k Nov 1, 2023
3467c9d
Profiling: Troubleshooting for newer HA connecting to older stack
christos68k Nov 1, 2023
a24f29c
Profiling: Don't capitalize collector in Troubleshooting
christos68k Nov 3, 2023
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
16 changes: 13 additions & 3 deletions docs/en/observability/profiling-troubleshooting.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,15 +82,17 @@ Failed to report hostinfo (retrying...): rpc error: code = Unimplemented desc =
----
+
This typically means that your {ecloud} cluster has not been configured for Universal Profiling. To configure your {ecloud} cluster, follow the steps in <<profiling-configure-data-ingestion,configure data ingestion>>.
* The APM server (part of the backend in {ecloud} that receives data from the host-agent) ran out of memory. In this case, a similar message to the following is logged:
* The collector (part of the backend in {ecloud} that receives data from the host-agent) ran out of memory. In this case, a similar message to the following is logged:

+
[source,logs]
----
Error: failed to invoke XXX(): Unavailable rpc error: code = Unavailable desc = unexpected HTTP status code received from server: 502 (Bad Gateway); transport: received unexpected content-type "application/json; charset=UTF-8"
----
+
Verify that the APM server is running by navigating to *{ecloud} → Deployments → `<Deployment Name>` → Integrations Server* in https://cloud.elastic.co/home[Elastic Cloud]. If the *Copy endpoint* link next to *APM* is grayed out,
you need to restart the APM server by clicking *Force Restart* under *Integrations Server Management*.
Verify that the collector is running by navigating to *{ecloud} → Deployments → `<Deployment Name>` → Integrations Server* in https://cloud.elastic.co/home[Elastic Cloud]. If the *Copy endpoint* link next to *Profiling* is grayed out,
you need to restart the collector by clicking *Force Restart* under *Integrations Server Management*.

+
For non-demo workloads, verify that the Integrations Server has at least the recommended 4GB of RAM. You can check this on the Integrations Server page under *Instances*.
* The host-agent is incompatible with the {stack} version. In this case, the following message is logged:
Expand All @@ -101,6 +103,14 @@ rpc error: code = FailedPrecondition desc= HostAgent version is unsupported, ple
----
+
Follow the host-agent deployment instructions shown in Kibana which will always be correct for the {stack} version that you are using.
* You are using a host-agent from a newer {stack} version, configured to connect to an older {stack} version cluster. In this case, the following message is logged:
+
[source,logs]
----
rpc error: code = FailedPrecondition desc= Backend is incompatible with HostAgent, please check your configuration
----
+
Follow the host-agent deployment instructions shown in Kibana which will always be correct for the {stack} version that you are using.

If you're unable to find a solution to the host-agent failure, you can raise a support request indicating `Universal Profiling` and `host-agent` as the source of the problem.

Expand Down