Skip to content
Merged
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,11 @@ On the **{{fleet}}** page, agents associated with agentless integrations have na
3. From the **Actions** menu, select **Request diagnostics .zip**.
4. Download and unzip the [diagnostics bundle](/troubleshoot/ingest/fleet/common-problems.md#trb-collect-agent-diagnostics). Refer to [Common problems with {{fleet}} and {{agent}}](/troubleshoot/ingest/fleet/common-problems.md) for more information.

::::{note}
In {{ech}} deployments on {{stack}} versions 9.0.0-9.1.5, the connection between agentless integrations and {{fleet-server}} can be broken if the default {{fleet-server}} host URL value in {{fleet}} is modified or if a different host URL is set as the default. This can result in agentless agents having an `Unhealthy` status.

This issue is resolved in {{stack}} 9.1.6 and 9.2.0. In these versions, agentless integration policies are assigned to a default managed {{fleet-server}} host which cannot be modified.
::::

## How do I delete an agentless integration? [_how_do_i_delete_an_agentless_integration]

Expand All @@ -72,4 +77,4 @@ When you create a new agentless CSPM integration, a new agent policy appears wit

## Can agentless integrations use a specific range of static IP addresses for configuring allow and deny rules for traffic?

No, agentless integrations can not use a specific range of static IP addresses for configuring ingress and egress allow and deny rules.
No, agentless integrations can not use a specific range of static IP addresses for configuring ingress and egress allow and deny rules.