[Logs Explorer] Field statistics don't return any data #178970
Comments
ablnk
added
bug
|
Pinging @elastic/obs-ux-logs-team (Team:obs-ux-logs) |
|
I'm taking a look at this issue, as this behaviour seems to occur since the fields added to the grid are Smart Fields (a combination of many fields), which are so not mapped directly to any field and listed in the Field statistics. |
|
@tonyghiani do you know if this only happen on serverless, or is it a general issue? |
Hi @paulb-elastic, we know the cause of this issue, which came as a consequence of adding support for the smart fields columns in Logs Explorer. The issue only affects Logs Explorer in both stateful/serverless deployment and only when using the default smart fields. |
|
Many thanks @tonyghiani for the detailed analysis |
davismcphee
added
Project:OneDiscover
|
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery) |
…tab when using Smart Fields (#184172) ## Summary This addresses the bugs listed in #181674 (#181621 and #178970). Smart Fields are compound fields, as such there is no "real" backing field for them. In these scenarios where we can't use them directly we fall back to the `fallbackFields` configured for them. [@amyjtechwriter please could you check the copy](#181621 (comment)). I think `derived from...` would have sounded better, but it felt at odds with the scenario where you might specifically pick a field that is also a fallback field for a smart field. ## Reviewer notes - There were quite a lot of cross cutting concerns here between the `unified-field-list`, `unified-data-table`, core Discover code, `discover-utils`, and the `data_vizualizer` plugin for the field statistics table. Where I'd have liked to potentially put more things in the discover-utils it wasn't possible due to circular project references. - I've not added any functional tests for now as we'd be adding them to the Observability Logs Explorer which is going to be deprecated in due course. This ties in with part three of #181674. - A `renderFieldName` prop has been added to the field statistics table, this seemed to be the least intrusive way forward rather than a new / comprehensive cell rendering change (similar to the external cell renderers). - I've used the original [`fallbackFields`](https://github.com/elastic/kibana/blob/main/src/plugins/discover/common/data_types/logs/constants.ts#L35) configurations but the [virtual column components actually render a bit extra](https://github.com/elastic/kibana/blob/main/packages/kbn-discover-utils/src/utils/get_message_field_with_fallbacks.ts#L13). Am I missing anything with regards to potentially extending the `fallbackFields` definitions? ## Screenshots <img width="1253" alt="Screenshot 2024-05-23 at 20 25 57" src="https://github.com/elastic/kibana/assets/471693/c2982f45-c8fa-4caa-935d-7007745ae2ce"> <img width="1477" alt="Screenshot 2024-05-23 at 20 26 21" src="https://github.com/elastic/kibana/assets/471693/3145fbd1-071e-42fd-a94d-beb15c29c739"> --------- Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Davis McPhee <davis.mcphee@elastic.co>
|
Fixed by #184172 |
Version:
Serverless project v 8.14.0
Description:
Field statistics in Logs Explorer don't return any data regardless of the set time interval (e.g. for 1 minute or for 7 days of log data).
Steps to reproduce:
Expected behavior:
Field statistics must be returned.
Screenshots:
The text was updated successfully, but these errors were encountered: