Am using the standard ELK stack and am having an issue with kibana
currently.
I close one of my indices (e.g. logstash-2015.03.30). When i do a search in
kibana for data involving that index, i get a 403 (IndexClosedException).
I would have expected Kibana/Elasticsearch to know the index is closed and
not to use in in search.
Is there anyway to tell kibana to ignore that index in search? Would
deleting the index be an alternative?
This is dangerous as it can lead to you not knowing that data isn't
available.
If you have it closed and are considering deleting it to resolve this, then
why even bother closing it in the first place, just delete it.
On 2 April 2015 at 00:37, Derry O' Sullivan derryos@gmail.com wrote:
Hi all,
Am using the standard ELK stack and am having an issue with kibana
currently.
I close one of my indices (e.g. logstash-2015.03.30). When i do a search
in kibana for data involving that index, i get a 403
(IndexClosedException). I would have expected Kibana/Elasticsearch to know
the index is closed and not to use in in search.
Is there anyway to tell kibana to ignore that index in search? Would
deleting the index be an alternative?
The reason i asked was that i closed the index due to the fact that i
didn't want people to query that data temporarily (vs
deleting/permanently). I thought that Kibana would have handled the closed
index vs throwing a 403 exception. Without looking at the developer tools
though, you don't get any errors from kibana - just blank widgets.
This is dangerous as it can lead to you not knowing that data isn't
available.
If you have it closed and are considering deleting it to resolve this,
then why even bother closing it in the first place, just delete it.
On 2 April 2015 at 00:37, Derry O' Sullivan derryos@gmail.com wrote:
Hi all,
Am using the standard ELK stack and am having an issue with kibana
currently.
I close one of my indices (e.g. logstash-2015.03.30). When i do a search
in kibana for data involving that index, i get a 403
(IndexClosedException). I would have expected Kibana/Elasticsearch to know
the index is closed and not to use in in search.
Is there anyway to tell kibana to ignore that index in search? Would
deleting the index be an alternative?
You might want to raise an issue on Github for a feature request then as
it's possible to just ignore.
On 2 April 2015 at 09:15, Derry O' Sullivan derryos@gmail.com wrote:
Hi Mark,
The reason i asked was that i closed the index due to the fact that i
didn't want people to query that data temporarily (vs
deleting/permanently). I thought that Kibana would have handled the closed
index vs throwing a 403 exception. Without looking at the developer tools
though, you don't get any errors from kibana - just blank widgets.
This is dangerous as it can lead to you not knowing that data isn't
available.
If you have it closed and are considering deleting it to resolve this,
then why even bother closing it in the first place, just delete it.
On 2 April 2015 at 00:37, Derry O' Sullivan derryos@gmail.com wrote:
Hi all,
Am using the standard ELK stack and am having an issue with kibana
currently.
I close one of my indices (e.g. logstash-2015.03.30). When i do a search
in kibana for data involving that index, i get a 403
(IndexClosedException). I would have expected Kibana/Elasticsearch to know
the index is closed and not to use in in search.
Is there anyway to tell kibana to ignore that index in search? Would
deleting the index be an alternative?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.