Skip to content
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

Temporary kibana runtime fields #159182

Closed
nettnikl opened this issue Jun 7, 2023 · 8 comments
Closed

Temporary kibana runtime fields #159182

nettnikl opened this issue Jun 7, 2023 · 8 comments
Labels
enhancement New value added to drive a business result Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL.

Comments

@nettnikl
Copy link

nettnikl commented Jun 7, 2023

Describe the feature:
Allowing to specify runtime fields for a singular search query in the KQL search query bar or the fields list on the left side.

This can be done with the current language for runtime fields, or (preferably) in an easier syntax.

Describe a specific use case for the feature:

  • To expose already available functionality: https://www.elastic.co/guide/en/elasticsearch/reference/7.17/runtime-search-request.html#runtime-search-request
    As i understand, Runtime fields are not stored, because they are meant for cases which are exceptional/one-time use.
  • To make the transition easy for splunk users, who are used to not only specify the search term, but also the displayed fields in the search bar (also dynamically created - ie runtime - ones).
  • During analysis of exceptional events (like in a SIEM, but also RCAs of software errors), we do a lot of searches for patterns that normally would never occur. In such cases, the overhead of creating a persistent runtime field (which, in case it has an error, crashes all searches) seems unnecessary. Also, in many such cases these runtime fields are not reused often, or at all. If they are, they are usually modified again, which would be much more comfortable if available in the search bar.
  • To allow use cases like ([KQL] Allow comparing the values for different fields #110699 (comment)) to not act as filter, but also be displayed as a field, which helps in creating ad-hoc "dashboard" tables
@botelastic botelastic bot added the needs-team Issues missing a team label label Jun 7, 2023
@nreese nreese added the Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. label Jun 12, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Jun 12, 2023
@nreese nreese added enhancement New value added to drive a business result needs-team Issues missing a team label labels Jun 12, 2023
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jun 12, 2023
@kertal
Copy link
Member

kertal commented Jun 13, 2023

@nettnikl Did you have a chance to look at ESQL which is currently under development, I think this could cover your use case? https://www.elastic.co/de/blog/introduction-to-esql-new-query-language-flexible-iterative-analytics

@nettnikl
Copy link
Author

Hi! This indeed looks like it is we're looking for. But to say for sure, it has to be tested ofc - the blog doesnt explicitely mention in which version it would be included - is it available for the 7.x version, or only in some beta versions on 8.x branch?

@kertal
Copy link
Member

kertal commented Jun 13, 2023

Looping in @ninoslavmiskovic for those kind of questions

@ninoslavmiskovic
Copy link
Contributor

@nettnikl we are currently working on ESQL and I would to share the video from ElasticON with a demo of ESQL : https://youtu.be/JxisIO8q8UU

Stayed tuned on our blog and social media for public announcements on releases.

@kertal
Copy link
Member

kertal commented Jun 13, 2023

thx @ninoslavmiskovic closing since it's an enhancement in the works

@kertal kertal closed this as completed Jun 13, 2023
@nettnikl
Copy link
Author

Thanks for the information and the link. Looks very promising!
To summarize: there's no usable version right now, especially no production ready one, and there is no way of being notified about progress here dedicatedly, so the recommendation is to wait on the regular PR channels, right?

@kertal
Copy link
Member

kertal commented Jun 13, 2023

@nettnikl you can subscribe to this issue #137810 to see when it's resolved
And you're right, there's no usable version right now (not a public one)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL.
Projects
None yet
Development

No branches or pull requests

5 participants