[Filters] Confusing difference between formatted value of numbers and filters on that number

[cpajr]

When number formatters are used in Kibana, there is often a difference between what you see in Kibana and what you type to filter. For example, while searching based on event.duration in milliseconds, you need to understand that the data is displayed in milliseconds but collected in nanoseconds.

However, if a search is executed, you have to search based on the number in nanoseconds, or the value seen within the JSON. Kibana should be able to allow for a search based on how it is representing it within its interface.

Steps to reproduce:

1. Perform a search for a piece of data based on the Event Duration as shown in the entry table (i.e. event.duration > 20172)
2. When search is completed, the results will not reflect desired search.
3. Instead of providing a search based on the number shown in the table, issue a search based on the number shown within the JSON output (i.e. event.duration > 20172000000).

[wylieconlon]

@cpajr interesting feature request. I need to rewrite some of your issue to describe the part that is actually a new feature.

[elasticmachine]

Pinging @elastic/kibana-app-services (Team:AppServices)

[elasticmachine]

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