You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug:
While creating Transforms via the Kibana UI, we cannot select terms aggregations for long fields. The only option available for long fields is histogram, which results in different output than terms.
Using the Elasticsearch API, we can create transforms on long fields in either terms or histogram. The expected behavior is that Kibana also offers both aggregation methods.
Steps to reproduce:
Deploy the Kibana weblogs sample data
Go to Stack Management -> Transforms and create a new transform
For Groupy by select terms(clientip) and another one histogram(machine.ram)
Notice how no terms(machine.ram) are available. Also, notice how the field cannot be changed via the Edit button
Expected behavior:
Kibana should offer other aggregations, too, e.g., terms.
Screenshots (if relevant):
Workaround:
The currently confirmed workaround is to use the Kibana UI with the histogram aggregation until the end of the transforms configuration page. There, it offers to Copy to clipboard, which copies the current API call. Paste this to the Kibana dev console and replace the histogramaggregation with aterms. aggregation. Note that the aggregation name must not contain a period (.). This allows for the setup of transforms with termsonlong` fields.
The text was updated successfully, but these errors were encountered:
peteharverson
changed the title
Transforms UI only allows "histogram" on long fields - should also allow "terms"
[ML] Transforms UI only allows "histogram" on long fields - should also allow "terms"
Dec 16, 2022
Part of #123459
Kibana version: 7.17 - 8.5.3
Describe the bug:
While creating Transforms via the Kibana UI, we cannot select
terms
aggregations forlong
fields. The only option available forlong
fields ishistogram
, which results in different output thanterms
.Using the Elasticsearch API, we can create transforms on
long
fields in eitherterms
orhistogram
. The expected behavior is that Kibana also offers both aggregation methods.Steps to reproduce:
Groupy by
selectterms(clientip)
and another onehistogram(machine.ram)
terms(machine.ram)
are available. Also, notice how the field cannot be changed via theEdit
buttonExpected behavior:
Kibana should offer other aggregations, too, e.g.,
terms
.Screenshots (if relevant):
Workaround:
The currently confirmed workaround is to use the Kibana UI with the
histogram
aggregation until the end of the transforms configuration page. There, it offers toCopy to clipboard, which copies the current API call. Paste this to the Kibana dev console and replace the
histogramaggregation with a
terms. aggregation. Note that the aggregation name must not contain a period (
.). This allows for the setup of transforms with
termson
long` fields.The text was updated successfully, but these errors were encountered: