-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Security Solutions][Timeline] Non indexed fields are not showing up in the table view #91424
Comments
Pinging @elastic/security-threat-hunting (Team:Threat Hunting) |
Pinging @elastic/security-solution (Team: SecuritySolution) |
@karanbirsingh-qasource can you please validate the fix of this issue on 7.11.2BC2 and 7.12BC3? thanks :) |
Hi @karanbirsingh-qasource I'm not familiar with tat field but I can guide you to create an alert with a non-index field.
PUT /index/ POST /index/_doc/
Once the alert is generated from the alert details view, you should be able to search for the @FrankHassanabad can you please point us if this way is correct for testing this scenario? Thanks :) |
thanks for sharing the details to create the test-data for issue regress . we have validated this issue on 7.12.0 BC4 and found that issue is still occuring . mydestination field value is comming as "-" under the alert list table . However this field value is present under alert detail fly-out. Build Details:
Artifact Page: https://staging.elastic.co/7.12.0-336ff10d/summary-7.12.0.html @FrankHassanabad please provide your input if we are missing something for this issue regress. thanks !! |
thanks for looking into our observation. we have followed the steps shared by glo in order to create sample data for detection alert having non-index field and we have re-validated the step even there is no newer build than BC4 , but the issue is still occuring on 7.12.0 BC4 at our side even we have dragged that signal to timeline to see there issue occurrence too. Additionally below is the details of the mapping of index being used to create custom rule. Mapping
Steps Followed:
Additional Observation:
Please let us known if we are missing something in steps followed. thanks !! |
I reproduced it!! I was just looking at timeline, I needed the rule. Now to debug, I'll update soon. Thanks for your patience 🙏 |
Ok! The issue is that we have the custom mapping on the index, but not on the
Now each new |
Thanks for looking into our observation and providing updated steps to validate this Issue. we have followed the steps on 7.12.0 BC4 and Found that issue is Fixed 🟢 . Now Non-Index field ( in our case it is Build Details:
Snap-Shoot:Additional Details:Custom Rule Exported Zip: rules_export.zip Hence, we are closing this issue and adding "QA:Validated" label to it. thanks!! |
Bug conversion: Created 01 new Test-Case for this Ticket under Bug Conversion task: |
We are seeing this same behavior in v7.16.0. Should it have been resolved in this version? |
Describe the bug:
In timeline when you have an unindexed field after creating an alert and you select it in the details view it looks like the values are not showing up in the table. Tested 7.11.1-BC-1
Steps to reproduce:
Expected behavior:
The table shows the unindexed values in the columns.
Kibana version:
7.11.1-BC-1
Elasticsearch version:
7.11.1-BC-1
Server OS version:
any
Browser version:
any
Browser OS version:
any
Original install method (e.g. download page, yum, from source, etc.):
cloud
The text was updated successfully, but these errors were encountered: