[Internal]: Document new "Copy support info" button for agentless integrations + update agentless resources toggle location

Open Beginner friendly
#7,175 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
cloud
Domain
documentation

Research direction

Start by reviewing the Elastic Security agentless integrations FAQs and the merged Kibana PR 267660 for the current UI behavior. Document the agentless-only “Copy support info” action with its exact key=value fields, and update the location of the “Show agentless resources” toggle to Fleet → /app/fleet/_debug; done when both Elastic Cloud deployment methods are covered in the appropriate documentation.

Written by the indexing model from the issue text.

Description

enhancement Team:SKI triaged
Description

Kibana PR elastic/kibana#267660 (merged 2026-05-13) shipped two user-facing changes to agentless integrations that need doc updates:

  1. New "Copy support info" action
    A new context menu item was added to the agentless integration row on the package/integration details page (Actions menu → "Copy support info"). When clicked, it copies a key=value block to the clipboard that customers can paste into a support ticket:
elastic-support-bundle
deployment_id=   # or project_id= on Serverless
cluster_id=
policy_id=
integration=

This lets support engineers identify the underlying agentless container without back-and-forth. The button only appears for agentless policies. Support engineers reference this block format via an internal KB article, so getting the field names correct in docs matters.

  1. "Show agentless resources" toggle moved
    The toggle that shows/hides agentless resources in Fleet was moved from Fleet → Settings → Advanced to Fleet → /app/fleet/_debug (a new debug page).
Existing docs

There is Elastic Security agentless integrations FAQs but I'm not sure if it's the right place to document it.

Resources

Links

Which deployment methods does this change impact?

Elastic Cloud (Hosted and Serverless) only

Feature differences

It's basically used in Agentless, both ECH (Elastic Cloud Hosted) and Serverless.

What Elastic Stack release is this request related to?

N/A

Serverless release

No response

Collaboration model

The documentation team will create the first draft

Point of contact.

Main contact: @criamico

Stakeholders:

TriageBot — Complete
2026-07-02

Type: enhancement

Section check:

  • ✅ Problem statement: Two specific UI changes clearly described with technical detail and the business reason (support engineers need the key=value block)
  • ✅ Proposed outcome: Implied — document the new "Copy support info" action and the relocated "Show agentless resources" toggle

Ambiguity / scope notes:

  • Placement uncertainty ("I'm not sure if it's the right place") is appropriate hedging; the assignee can determine the correct location

Cross-references:

  • elastic/kibana#267660 — author confirms merged 2026-05-13
  • elastic/ingest-dev#7571 — external repo, not verified
  • (support.elastic.dev/redacted) — internal KB, not accessible externally

Next step: none — issue is complete

Generated by Gh Aw Issue Triage for issue #7175 · 34.6 AIC · ⌖ 9.94 AIC · ⊞ 9.1K · ◷

Dominant language
No language data
Stars
47
Forks
262
Avg merge
3d 8h
Merged PRs (30d)
127

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from elastic/docs-content

All issues in elastic/docs-content

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.