Skip to content

[Fleet] fix icon loading with default icon#242406

Merged
teresaromero merged 2 commits intoelastic:mainfrom
teresaromero:111088-fix-icons
Nov 11, 2025
Merged

[Fleet] fix icon loading with default icon#242406
teresaromero merged 2 commits intoelastic:mainfrom
teresaromero:111088-fix-icons

Conversation

@teresaromero
Copy link
Contributor

@teresaromero teresaromero commented Nov 10, 2025

Summary

Fix #111088

When loading the fleet data streams table, some icons are not loaded correctly and appear with the default 'package' icon.

Updated the deprecated sendGetPackageInfoByKey function and use sendGetPackageInfoByKeyForRq instead. This alone did not solve the problem.
When fetching for the icon list of a given package, only set the default 'package' icon type if the item list is undefined.

Attached capture of the new behavior.

Screen.Recording.2025-11-10.at.13.57.26.mov

Testing

Running locally kibana with fleet and an agent enrolled via docker.
Installed different integrations, specially system and system audit, this last one uses the default package icon. I found one of my solutions to not show the default icon so kept this one to check they worked ok too.

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
  • Review the backport guidelines and apply applicable backport:* labels.

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.

Release note

Fix package icons loading

@teresaromero teresaromero marked this pull request as ready for review November 10, 2025 13:16
@teresaromero teresaromero requested a review from a team as a code owner November 10, 2025 13:16
@teresaromero teresaromero changed the title [DRAFT][Fleet] fix icon loading with default icon Nov 10, 2025
@teresaromero teresaromero added release_note:fix backport:skip This PR does not require backporting v9.3.0 labels Nov 10, 2025
@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
fleet 176.6KB 176.7KB +20.0B
@nchaulet nchaulet self-requested a review November 10, 2025 15:22
Copy link
Member

@nchaulet nchaulet left a comment

Choose a reason for hiding this comment

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

Tested locally and works as expected 🚀

@botelastic botelastic bot added the Team:Fleet Team label for Observability Data Collection Fleet team label Nov 10, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@teresaromero teresaromero merged commit a8f82fc into elastic:main Nov 11, 2025
25 checks passed
eokoneyo pushed a commit to eokoneyo/kibana that referenced this pull request Dec 2, 2025
## Summary

Fix elastic#111088 

When loading the fleet data streams table, some icons are not loaded
correctly and appear with the default 'package' icon.

Updated the deprecated `sendGetPackageInfoByKey` function and use
`sendGetPackageInfoByKeyForRq` instead. This alone did not solve the
problem.
When fetching for the icon list of a given package, only set the default
'package' icon type if the item list is undefined.

Attached capture of the new behavior.


https://github.com/user-attachments/assets/aeb28ae6-cb46-42d5-a6a9-a82f9edee168


### Testing

Running locally kibana with fleet and an agent enrolled via docker. 
Installed different integrations, specially system and system audit,
this last one uses the default package icon. I found one of my solutions
to not show the default icon so kept this one to check they worked ok
too.

### 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
- [ ] [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)
- [ ] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

### 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.

- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
- [ ] ...

## Release note

Fix package icons loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:skip This PR does not require backporting release_note:fix Team:Fleet Team label for Observability Data Collection Fleet team v9.3.0

3 participants