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
How do I round a floating point number to 2 or 3 decimal places in the Metric visualization in Kibana4?
Also, how do I add "filter" criteria to the Metric Visualization, e.g., exclude certain documents from a sum/max metric or only sum up values from certain documents?
I was able to enter search text in the visualization which ended up being saved as:
{
"index": "index-prefix-*",
"query": {
"query_string": {
"query": "FieldName: "Some Field Text"",
"analyze_wildcard": true
}
},
"filter": []
}
Is there is a better way?
Thanks
Nabheet
The text was updated successfully, but these errors were encountered:
rashidkpc
changed the title
Metrics visualization round a floating point number
Apply field formatter to metric vis
Jan 13, 2015
rashidkpc
added
the
bug
Fixes for quality problems that affect the customer experience
label
Jan 13, 2015
It looks like the metric vis is not applying the number field formatter. Tagging as bug
Really we should probably be applying the field formatter anywhere we display a number that represents the value of a field. Eg, we should apply it on things like sum/min/max, but not on say, count, or unique count.
I've reduced this ticket to only address the one bug, if you have usage questions feel free to join us in #kibana on freenode for interactive troubleshooting.
How do I round a floating point number to 2 or 3 decimal places in the Metric visualization in Kibana4?
Also, how do I add "filter" criteria to the Metric Visualization, e.g., exclude certain documents from a sum/max metric or only sum up values from certain documents?
I was able to enter search text in the visualization which ended up being saved as:
{
"index": "index-prefix-*",
"query": {
"query_string": {
"query": "FieldName: "Some Field Text"",
"analyze_wildcard": true
}
},
"filter": []
}
Is there is a better way?
Thanks
Nabheet
The text was updated successfully, but these errors were encountered: