Repository navigation
System integration references non existent tags in dashboard and searches #173755
Description
Activity
- addedbugFixes for quality problems that affect the customer experienceFixes for quality problems that affect the customer experience
on Dec 20, 2023 - addedTeam:Cloud SecurityCloud Security team relatedCloud Security team related
on Dec 27, 2023 Pinging @elastic/kibana-cloud-security-posture (Team:Cloud Security)
- addedneeds-teamIssues missing a team labelIssues missing a team labeland removedTeam:Cloud SecurityCloud Security team relatedCloud Security team related
on Feb 22, 2024 Removing the Cloud Security team tag as the issue can be reproduced with any integration as far as I can tell. I guess that it should be tagged with the Fleet team tag, but I will leave tagging to those who are better aware of which team it should belong to
Pinging @elastic/fleet (Team:Fleet)
Adding
Team: Fleetas the problem is concerning the System integration. Hope that makes senseHi @maxcold I believe this should rather be created in the https://github.com/elastic/integrations repository and looks like this could have been added by @marc-gr - https://github.com/elastic/integrations/blame/da6480c09e86a288c5c811f139f3b9f8a4f69b61/packages/system/kibana/tags.yml#L12
Hi @jlind23 , thanks for bringing this up! As the issue was coming from
globalSearchBarin Kibana, I wasn't sure where to open the issue. Kibana repo seemed like a good starting point.
As for the fix you mentioned, I still see the warning in the logs in version 8.13.0 of the stack (systemintegration v1.54.0).
One thing that I noticed is that I see this issue in logs only in us-west2 (LA) which is our cloud-first testing env, and not in other envs (I looked into Iowa as well). I guess due to the differences in the logging levels between these envs. I'm not sure how big of a problem the issue is taking into account that it's only a warning in our testing env, but who knows what it can lead to
The tag reference added in the integration should be automatically created by the Security Solution (more context #164582). IIRC for this to be the case user should have entered the Security Solution UI at least once, but I might be wrong on this.
- addedstaleUsed to mark issues that were closed for being staleUsed to mark issues that were closed for being staleand removedstaleUsed to mark issues that were closed for being staleUsed to mark issues that were closed for being stale
on Mar 18, 2025 We haven't revisited this issue in a while, so we're closing it due to inactivity. Please reopen with a comment if you think this is a mistake. Thanks!
Kibana version:
8.11
Elasticsearch version:
8.11
Server OS version:
Mac OS
Browser version:
Chrome
Browser OS version:
Original install method (e.g. download page, yum, from source, etc.):
Describe the bug:
When installing a
systemintegration, eg. by choosingCollect system logs and metricsin the New Hosts tab on the Add Integration page, and then searching fordashboardin the search bar, there is a warningSearchBar: Tag with id "security-solution-default" not found. Tag "security-solution-default" is referenced by the search result "dashboard:system-Logs-syslog-dashboard". Skipping displaying the missing tag.in the browser console.It's not clear where these tags are coming from as they are not referenced explicitly on the
system-Logs-syslog-dashboarddashboard which is an asset ofsystemintegration.While it's only a console warning, I'm not sure what else referencing non existent tags can affect. It used to crash Kibana's search but was fixed in
Steps to reproduce:
Collect system logs and metricsoption is selecteddashboardin the Kibana search barExpected behavior:
no warnings
Screenshots (if relevant):
Screen.Recording.2023-12-20.at.15.41.04.mov
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):
Any additional context: