Skip to content

Render accordion in integration readme#223916

Merged
haetamoudi merged 17 commits intoelastic:mainfrom
haetamoudi:82-kibana-support-for-collapsible-sections-on-integration-overview-page
Jun 24, 2025
Merged

Render accordion in integration readme#223916
haetamoudi merged 17 commits intoelastic:mainfrom
haetamoudi:82-kibana-support-for-collapsible-sections-on-integration-overview-page

Conversation

@haetamoudi
Copy link
Contributor

@haetamoudi haetamoudi commented Jun 13, 2025 •
edited by kibanamachine
Loading

Summary

Support collapsible section in Integration README
The public Integrations docs page recently added support for collapsible sections (e.g., for field tables and sample events). This PR brings the same functionality to Kibana to reduce scrolling and help users focus on the most relevant information.

To display an accordion, the README should include the following markup:

<details>
  <summary>Click to expand</summary>
  This content is hidden by default.
</details>

However, we do not want to modify the integration READMEs directly. Doing so would cause these tags to appear as raw HTML in older versions of Kibana
Bumping the minimum supported Kibana version for each integration is also not a solution, as it would complicate backports and maintenance.

Proposed solution

Detect in Kibana parts that should be collapsible, like exported fields and update the markdown with the necessary markups. Similar to what the integration-docs does in https://github.com/elastic/integration-docs/issues/342

Dependencies added:

  • rehype-raw: Parse and render HTML inside Markdown.
  • rehype-sanitize: Sanitize potentially unsafe HTML.

Version pinning for compatibility

  • rehype-sanitize@4.0.0: Uses hast-util-sanitize@3+, which provides a built-in default schema and is compatible with CommonJS environments.
  • rehype-raw@5.1.0: The latest version that supports CommonJS. Later versions are ESM-only.
collapse.mov

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

  • Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
  • Documentation was added for features that require explanation or tutorials
  • Unit or functional tests were updated or added to match the most common scenarios
  • If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
  • This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
  • Flaky Test Runner was used on any tests changed
  • The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines

Identify risks

Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.
@kibanamachine kibanamachine requested a review from a team June 13, 2025 13:35
@kibanamachine
Copy link
Contributor

kibanamachine commented Jun 13, 2025

Dependency Review Bot Analysis 🔍

Found 3 new third-party dependencies:

Package Version Vulnerabilities Health Score
rehype-sanitize ^6.0.0 🔴 C: 0, 🟠 H: 0, 🟡 M: 0, 🟢 L: 0 rehype-sanitize
hast-util-sanitize ^5.0.2 🔴 C: 0, 🟠 H: 0, 🟡 M: 0, 🟢 L: 0 hast-util-sanitize
rehype-raw 6 🔴 C: 0, 🟠 H: 0, 🟡 M: 0, 🟢 L: 0 rehype-raw

Self Checklist

To help with the review, please update the PR description to address the following points for each new third-party dependency listed above:

  • Purpose: What is this dependency used for? Briefly explain its role in your changes.
  • Justification: Why is adding this dependency the best approach?
  • Alternatives explored: Were other options considered (e.g., using existing internal libraries/utilities, implementing the functionality directly)? If so, why was this dependency chosen over them?
  • Existing dependencies: Does Kibana have a dependency providing similar functionality? If so, why is the new one preferred?

Thank you for providing this information!
@haetamoudi haetamoudi changed the title render accordion in integration readme Jun 13, 2025
@haetamoudi haetamoudi added Team:Security-Scalability Security Integrations Scalability Team enhancement New value added to drive a business result release_note:enhancement backport:prev-minor labels Jun 18, 2025
@haetamoudi haetamoudi changed the title (WIP) render accordion in integration readme Jun 18, 2025
@haetamoudi haetamoudi marked this pull request as ready for review June 18, 2025 13:18
@haetamoudi haetamoudi requested a review from a team as a code owner June 18, 2025 13:18
@elasticmachine
Copy link
Contributor

elasticmachine commented Jun 18, 2025

Pinging @elastic/security-scalability (Team:Security-Scalability)
@kibanamachine
[CI] Auto-commit changed files from 'node scripts/capture_oas_snapsho…
390b17c 
…t --include-path /api/status --include-path /api/alerting/rule/ --include-path /api/alerting/rules --include-path /api/actions --include-path /api/security/role --include-path /api/spaces --include-path /api/streams --include-path /api/fleet --include-path /api/dashboards --include-path /api/saved_objects/_import --include-path /api/saved_objects/_export --include-path /api/maintenance_window --update'
@botelastic botelastic bot added the Team:Fleet Team label for Observability Data Collection Fleet team label Jun 18, 2025
@elasticmachine
Copy link
Contributor

elasticmachine commented Jun 18, 2025

Pinging @elastic/fleet (Team:Fleet)
@haetamoudi haetamoudi requested a review from kgeller June 18, 2025 13:39
@haetamoudi haetamoudi added backport:version Backport to applied version labels v8.19.0 and removed backport:prev-minor labels Jun 18, 2025
@elena-shostak elena-shostak self-requested a review June 19, 2025 13:00
elena-shostak
elena-shostak approved these changes Jun 19, 2025
View reviewed changes
Copy link
Contributor

@elena-shostak elena-shostak left a comment

Choose a reason for hiding this comment

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

Dependency review - approved ✅
rehype-sanitize provides a granular control over sanitization of user-generated content and has good health score.

We don't have any other dependencies regarding sanitization, like DOMPurify or sanitize-html, so adopting rehype-sanitize is feasible.
@haetamoudi
Copy link
Contributor Author

haetamoudi commented Jun 20, 2025

@juliaElastic I have added a EuiSpacer after each accordion

Screenshot 2025-06-20 at 11 26 50
juliaElastic
juliaElastic approved these changes Jun 20, 2025
View reviewed changes
Copy link
Contributor

@juliaElastic juliaElastic left a comment

Choose a reason for hiding this comment

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

LGTM
@haetamoudi haetamoudi requested a review from mjwolf June 20, 2025 11:37
@elasticmachine
Copy link
Contributor

elasticmachine commented Jun 24, 2025

💚 Build Succeeded

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id before after diff
fleet 1249 1361 +112

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
fleet 1.8MB 2.1MB ⚠️ +318.7KB

History
@haetamoudi haetamoudi merged commit 869e162 into elastic:main Jun 24, 2025
11 checks passed
@kibanamachine
Copy link
Contributor

kibanamachine commented Jun 24, 2025

Starting backport for target branches: 8.19

https://github.com/elastic/kibana/actions/runs/15849098264
@kibanamachine
Copy link
Contributor

kibanamachine commented Jun 24, 2025

💔 All backports failed

Status Branch Result
❌ 8.19 Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

node scripts/backport --pr 223916

Questions ?

Please refer to the Backport tool documentation
@kibanamachine kibanamachine mentioned this pull request Jun 24, 2025
Merged
1 task
akowalska622 pushed a commit to akowalska622/kibana that referenced this pull request Jun 25, 2025
@haetamoudi @kibanamachine @akowalska622
Render accordion in integration readme (elastic#223916)
da7b0d4 
## Summary

[Support collapsible section in Integration
README](elastic/integration-experience#82)
The public Integrations docs page recently added support for collapsible
sections (e.g., for field tables and sample events). This PR brings the
same functionality to Kibana to reduce scrolling and help users focus on
the most relevant information.

To display an accordion, the README should include the following markup:
```
<details>
  <summary>Click to expand</summary>
  This content is hidden by default.
</details>
```
However, we do not want to modify the integration READMEs directly.
Doing so would cause these tags to appear as raw HTML in older versions
of Kibana
Bumping the minimum supported Kibana version for each integration is
also not a solution, as it would complicate backports and maintenance.

#### Proposed solution
Detect in Kibana parts that should be collapsible, like `exported
fields` and update the markdown with the necessary markups. Similar to
what the `integration-docs` does in
elastic/integration-docs#342


#### Dependencies added:
- `rehype-raw`: Parse and render HTML inside Markdown.
- `rehype-sanitize`: Sanitize potentially unsafe HTML.

#### Version pinning for compatibility
- `rehype-sanitize@4.0.0`: Uses hast-util-sanitize@3+, which provides a
built-in default schema and is compatible with CommonJS environments.
- `rehype-raw@5.1.0`: The latest version that supports CommonJS. Later
versions are ESM-only.



https://github.com/user-attachments/assets/15f0822b-9b36-45e6-a47e-c8fa0dedd4c3



### Checklist

Check the PR satisfies following conditions. 

Reviewers should verify this PR satisfies this list as well.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)

### Identify risks

Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
@kibanamachine kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label Jun 25, 2025
@kibanamachine
Copy link
Contributor

kibanamachine commented Jun 25, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 223916 locally
cc: @haetamoudi
@haetamoudi haetamoudi mentioned this pull request Jun 25, 2025
Merged
@haetamoudi
Copy link
Contributor Author

haetamoudi commented Jun 25, 2025

💚 All backports created successfully

Status Branch Result
✅ 8.19

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation
haetamoudi added a commit that referenced this pull request Jun 25, 2025
@haetamoudi
[8.19] Render accordion in integration readme (#223916) (#225312)
2e10941 
# Backport

This will backport the following commits from `main` to `8.19`:
- [Render accordion in integration readme
(#223916)](#223916)

<!--- Backport version: 10.0.1 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Hanna
Tamoudi","email":"hanna.tamoudi@elastic.co"},"sourceCommit":{"committedDate":"2025-06-24T11:22:55Z","message":"Render
accordion in integration readme (#223916)\n\n## Summary\n\n[Support
collapsible section in
Integration\nREADME](https://github.com/elastic/integration-experience/issues/82)\nThe
public Integrations docs page recently added support for
collapsible\nsections (e.g., for field tables and sample events). This
PR brings the\nsame functionality to Kibana to reduce scrolling and help
users focus on\nthe most relevant information.\n\nTo display an
accordion, the README should include the following
markup:\n```\n<details>\n <summary>Click to expand</summary>\n This
content is hidden by default.\n</details>\n```\nHowever, we do not want
to modify the integration READMEs directly.\nDoing so would cause these
tags to appear as raw HTML in older versions\nof Kibana\nBumping the
minimum supported Kibana version for each integration is\nalso not a
solution, as it would complicate backports and maintenance.\n\n####
Proposed solution\nDetect in Kibana parts that should be collapsible,
like `exported\nfields` and update the markdown with the necessary
markups. Similar to\nwhat the `integration-docs` does
in\nhttps://github.com/elastic/integration-docs/issues/342\n\n\n####
Dependencies added:\n- `rehype-raw`: Parse and render HTML inside
Markdown.\n- `rehype-sanitize`: Sanitize potentially unsafe
HTML.\n\n#### Version pinning for compatibility\n-
`rehype-sanitize@4.0.0`: Uses hast-util-sanitize@3+, which provides
a\nbuilt-in default schema and is compatible with CommonJS
environments.\n- `rehype-raw@5.1.0`: The latest version that supports
CommonJS. Later\nversions are
ESM-only.\n\n\n\nhttps://github.com/user-attachments/assets/15f0822b-9b36-45e6-a47e-c8fa0dedd4c3\n\n\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [ ] Any text
added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n###
Identify risks\n\nDoes this PR introduce any risks? For example,
consider risks like hard\nto test bugs, performance regression,
potential of data loss.\n\nDescribe the risk, its severity, and
mitigation for each identified\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"869e162812a449742aad9ddd99f1acf838c278f1","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","enhancement","backport
missing","Team:Fleet","Team:Security-Scalability","backport:version","v9.1.0","v8.19.0"],"title":"Render
accordion in integration
readme","number":223916,"url":"https://github.com/elastic/kibana/pull/223916","mergeCommit":{"message":"Render
accordion in integration readme (#223916)\n\n## Summary\n\n[Support
collapsible section in
Integration\nREADME](https://github.com/elastic/integration-experience/issues/82)\nThe
public Integrations docs page recently added support for
collapsible\nsections (e.g., for field tables and sample events). This
PR brings the\nsame functionality to Kibana to reduce scrolling and help
users focus on\nthe most relevant information.\n\nTo display an
accordion, the README should include the following
markup:\n```\n<details>\n <summary>Click to expand</summary>\n This
content is hidden by default.\n</details>\n```\nHowever, we do not want
to modify the integration READMEs directly.\nDoing so would cause these
tags to appear as raw HTML in older versions\nof Kibana\nBumping the
minimum supported Kibana version for each integration is\nalso not a
solution, as it would complicate backports and maintenance.\n\n####
Proposed solution\nDetect in Kibana parts that should be collapsible,
like `exported\nfields` and update the markdown with the necessary
markups. Similar to\nwhat the `integration-docs` does
in\nhttps://github.com/elastic/integration-docs/issues/342\n\n\n####
Dependencies added:\n- `rehype-raw`: Parse and render HTML inside
Markdown.\n- `rehype-sanitize`: Sanitize potentially unsafe
HTML.\n\n#### Version pinning for compatibility\n-
`rehype-sanitize@4.0.0`: Uses hast-util-sanitize@3+, which provides
a\nbuilt-in default schema and is compatible with CommonJS
environments.\n- `rehype-raw@5.1.0`: The latest version that supports
CommonJS. Later\nversions are
ESM-only.\n\n\n\nhttps://github.com/user-attachments/assets/15f0822b-9b36-45e6-a47e-c8fa0dedd4c3\n\n\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [ ] Any text
added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n###
Identify risks\n\nDoes this PR introduce any risks? For example,
consider risks like hard\nto test bugs, performance regression,
potential of data loss.\n\nDescribe the risk, its severity, and
mitigation for each identified\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"869e162812a449742aad9ddd99f1acf838c278f1"}},"sourceBranch":"main","suggestedTargetBranches":["8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/223916","number":223916,"mergeCommit":{"message":"Render
accordion in integration readme (#223916)\n\n## Summary\n\n[Support
collapsible section in
Integration\nREADME](https://github.com/elastic/integration-experience/issues/82)\nThe
public Integrations docs page recently added support for
collapsible\nsections (e.g., for field tables and sample events). This
PR brings the\nsame functionality to Kibana to reduce scrolling and help
users focus on\nthe most relevant information.\n\nTo display an
accordion, the README should include the following
markup:\n```\n<details>\n <summary>Click to expand</summary>\n This
content is hidden by default.\n</details>\n```\nHowever, we do not want
to modify the integration READMEs directly.\nDoing so would cause these
tags to appear as raw HTML in older versions\nof Kibana\nBumping the
minimum supported Kibana version for each integration is\nalso not a
solution, as it would complicate backports and maintenance.\n\n####
Proposed solution\nDetect in Kibana parts that should be collapsible,
like `exported\nfields` and update the markdown with the necessary
markups. Similar to\nwhat the `integration-docs` does
in\nhttps://github.com/elastic/integration-docs/issues/342\n\n\n####
Dependencies added:\n- `rehype-raw`: Parse and render HTML inside
Markdown.\n- `rehype-sanitize`: Sanitize potentially unsafe
HTML.\n\n#### Version pinning for compatibility\n-
`rehype-sanitize@4.0.0`: Uses hast-util-sanitize@3+, which provides
a\nbuilt-in default schema and is compatible with CommonJS
environments.\n- `rehype-raw@5.1.0`: The latest version that supports
CommonJS. Later\nversions are
ESM-only.\n\n\n\nhttps://github.com/user-attachments/assets/15f0822b-9b36-45e6-a47e-c8fa0dedd4c3\n\n\n\n###
Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers
should verify this PR satisfies this list as well.\n\n- [ ] Any text
added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [x] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n###
Identify risks\n\nDoes this PR introduce any risks? For example,
consider risks like hard\nto test bugs, performance regression,
potential of data loss.\n\nDescribe the risk, its severity, and
mitigation for each identified\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\n\n---------\n\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"869e162812a449742aad9ddd99f1acf838c278f1"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
@kibanamachine kibanamachine removed the backport missing Added to PRs automatically when the are determined to be missing a backport. label Jun 25, 2025
@andrewkroh andrewkroh mentioned this pull request Jul 1, 2025
Merged
4 tasks
@kgeller kgeller mentioned this pull request Jul 21, 2025
Merged
kgeller added a commit that referenced this pull request Jul 23, 2025
@kgeller
Integrations overview: render accordion for sample events (#228799)
6dfb185 
## Summary

Support for collapsible sections was [recently
added](#223916) with functionality
to collapse the exported fields table by default. This PR is a followup
to that and also collapses the sample events by default as well.

## Screen recording


https://github.com/user-attachments/assets/f51ea1f9-0b27-4ddb-a2ee-a994ae3bf380

Relates #223916
Addresses elastic/integration-experience#151
kertal pushed a commit to kertal/kibana that referenced this pull request Jul 25, 2025
@kgeller @kertal
Integrations overview: render accordion for sample events (elastic#22…
e7e96c9 
…8799)

## Summary

Support for collapsible sections was [recently
added](elastic#223916) with functionality
to collapse the exported fields table by default. This PR is a followup
to that and also collapses the sample events by default as well.

## Screen recording


https://github.com/user-attachments/assets/f51ea1f9-0b27-4ddb-a2ee-a994ae3bf380

Relates elastic#223916
Addresses elastic/integration-experience#151
eokoneyo pushed a commit to eokoneyo/kibana that referenced this pull request Jul 31, 2025
@kgeller @eokoneyo
Integrations overview: render accordion for sample events (elastic#22…
4aabdfa 
…8799)

## Summary

Support for collapsible sections was [recently
added](elastic#223916) with functionality
to collapse the exported fields table by default. This PR is a followup
to that and also collapses the sample events by default as well.

## Screen recording


https://github.com/user-attachments/assets/f51ea1f9-0b27-4ddb-a2ee-a994ae3bf380

Relates elastic#223916
Addresses elastic/integration-experience#151
@kgeller kgeller mentioned this pull request Aug 20, 2025
Merged
@mjwolf mjwolf mentioned this pull request Dec 5, 2025
Closed
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:version Backport to applied version labels enhancement New value added to drive a business result release_note:enhancement Team:Fleet Team label for Observability Data Collection Fleet team Team:Security-Scalability Security Integrations Scalability Team v8.19.0 v9.1.0

8 participants

@haetamoudi @kibanamachine @elasticmachine @juliaElastic @jsoriano @kgeller @elena-shostak @mykola-elastic