Our sysadmins recently upgraded to ES 1.0.1, which has deprecated field
as a filter type and now our custom kibana dashboards are non-functional. I
have seen a few posts about this topic, but I haven't found any guidance as
to what needs to be in the dashboard file to replace the below snippet:
: lucene
}
},
ids: [
0
]
},
filter: {
idQueue: [
0,
0,
1,
2
],
list: {},
ids: []
}
},
On Wednesday, March 12, 2014 1:34:14 AM UTC-7, Jay Wilson wrote:
Our sysadmins recently upgraded to ES 1.0.1
I am modifying the guided.json dashboard. Down in Events panel I would
like to tell kibana to statically filter out specific records. I tried
adding this to the file.
query: {
filtered: {
query: {
bool: {
not filter.
Here once you save that dashboard , you can always go back to the same
link to see the same static dashboard.
Thanks
Vineeth
On Thu, Jan 9, 2014 at 2:42 AM, Jay Wilson jawr...@gmail.comjavascript:
wrote:
I am modifying the guided.json dashboard. Down in Events
I have a default-mapping.json file working fine in Ubuntu by placing it in
/usr/local/elasticsearch/config/.
I also have Centos install of ES, but I can't figure out where to put the
default-mapping.json file. I have tried /usr/share/elasticsearch/config/
and /etc/elasticsearch/config/.
