[Internal]: Update agentless troubleshooting docs

[kpollich]

Description

https://www.elastic.co/docs/solutions/security/get-started/agentless-integrations-faq#why-isnt-my-agentless-agent-appearing-in-fleet and https://www.elastic.co/docs/solutions/security/get-started/agentless-integrations-faq#_how_do_i_troubleshoot_an_unhealthy_agent need to be updated to capture two new concerns:

1. We've removed the query parameter in favor of a toggle under Fleet > Settings
2. Agentless containers no longer ship system metrics/logs to the user's cluster by default, so logs aren't visible in product and diagnostics need to be generated to view logs

Resources

#3108

elastic/kibana#237528

elastic/kibana#237639

Which documentation set does this change impact?

Elastic On-Prem and Cloud (all)

Feature differences

N/A

What release is this request related to?

N/A

Serverless release

N/A

Collaboration model

The documentation team

Point of contact.

Main contact: @kpollich

Stakeholders: @elastic/agentless-team

[kpollich]

cc @benironside as we worked together on the previous agentless troubleshooting docs.

[kpollich]

For reference, the setting to show agentless resources is available under Fleet -> Settings -> Advanced settings, e.g.

@benironside Is your 9.2 environment from an earlier BC perhaps? I see this on a fresh 9.2 deployment on ECH so hopefully I'm not missing some conditional rendering issue or something.

For the second point, generating diagnostics, the workflow should look as follows

1. Enable "Show agentless resources" in Fleet settings
2. Navigate to the agent running the integration in question (its name will align with the integration policy name)

3. Request diagnostics for the agent

4. Download and unzip the generated diagnostics bundle once it's ready to explore the agent's logs, health status, etc. See https://www.elastic.co/docs/troubleshoot/ingest/fleet/common-problems#trb-collect-agent-diagnostics.

[benironside]

@kpollich to clarify, is the current answer for https://www.elastic.co/docs/solutions/security/get-started/agentless-integrations-faq#_how_do_i_troubleshoot_an_unhealthy_agent accurate for versions 9.0 and 9.1 of Elastic? The new instructions you gave apply to Serverless and versions 9.2+, correct?

[kpollich]

I think that "unhealthy agent" instruction is highly specific to the Cloud Security Posture Management integration and is not generically applicable to all agentless integrations.