All these object types are inserted into the same index bits. The data is
inserted at regular intervals of say 30 mins, Meaning I add a set of JSON
document every 30 mins to each of the above five types. However only on of
my object type's have timestamp as a part of JSON data. I am using
elasticsearch 1.4 and Kibana 3. I can't seem to sepcify the index for the
Kibana dashboard. It does expect a timestamp value.
Because of this I suspect I am limited in the kinds of graphs that I can
plot.I would like to plot dual axis graphs and some time series data.Is
this correct assumption?
Is the index that Kibana is looking for the same as the index in
elasticsearch. In other words Should I rather use the timestamp value (of
when I load the data into elasticsearch) as the elasticsearch rather than
some constant value like bits used in the above example.
As my data does not have the timestamp inherently, What format should my
timestamp (that I am supposed to use as the index have, If I should)
All these object types are inserted into the same index bits. The data
is inserted at regular intervals of say 30 mins, Meaning I add a set of
JSON document every 30 mins to each of the above five types. However only
on of my object type's have timestamp as a part of JSON data. I am using
elasticsearch 1.4 and Kibana 3. I can't seem to sepcify the index for the
Kibana dashboard. It does expect a timestamp value.
Because of this I suspect I am limited in the kinds of graphs that I can
plot.I would like to plot dual axis graphs and some time series data.Is
this correct assumption?
Is the index that Kibana is looking for the same as the index in
elasticsearch. In other words Should I rather use the timestamp value (of
when I load the data into elasticsearch) as the elasticsearch rather than
some constant value like bits used in the above example.
As my data does not have the timestamp inherently, What format should my
timestamp (that I am supposed to use as the index have, If I should)
All these object types are inserted into the same index bits. The data
is inserted at regular intervals of say 30 mins, Meaning I add a set of
JSON document every 30 mins to each of the above five types. However only
on of my object type's have timestamp as a part of JSON data. I am using
elasticsearch 1.4 and Kibana 3. I can't seem to sepcify the index for the
Kibana dashboard. It does expect a timestamp value.
Because of this I suspect I am limited in the kinds of graphs that I can
plot.I would like to plot dual axis graphs and some time series data.Is
this correct assumption?
Is the index that Kibana is looking for the same as the index in
elasticsearch. In other words Should I rather use the timestamp value (of
when I load the data into elasticsearch) as the elasticsearch rather than
some constant value like bits used in the above example.
As my data does not have the timestamp inherently, What format should my
timestamp (that I am supposed to use as the index have, If I should)
All these object types are inserted into the same index bits. The data
is inserted at regular intervals of say 30 mins, Meaning I add a set of
JSON document every 30 mins to each of the above five types. However only
on of my object type's have timestamp as a part of JSON data. I am using
elasticsearch 1.4 and Kibana 3. I can't seem to sepcify the index for the
Kibana dashboard. It does expect a timestamp value.
Because of this I suspect I am limited in the kinds of graphs that I can
plot.I would like to plot dual axis graphs and some time series data.Is
this correct assumption?
Is the index that Kibana is looking for the same as the index in
elasticsearch. In other words Should I rather use the timestamp value (of
when I load the data into elasticsearch) as the elasticsearch rather than
some constant value like bits used in the above example.
As my data does not have the timestamp inherently, What format should my
timestamp (that I am supposed to use as the index have, If I should)
When you mention timestamp in my docs, Do you mean that I actually replace
the Elasticsearch 'index' with timestamp. If yes is there a python library
perhaps that does that for me?
Regards,
Karthik.
On Friday, 20 March 2015 05:52:46 UTC+13, Mark Walkom wrote:
KB reads data from Elasticsearch, so yeah an index is the same thing for
both.
Basically you either need a timestamp in your docs to use KB3, or move to
KB4.
On 18 March 2015 at 19:10, Karthik Sharma <karthik...@gmail.com
<javascript:>> wrote:
I have inserted some data into Elasticsearch using REST interface.An
example is shown below.
All these object types are inserted into the same index bits. The data
is inserted at regular intervals of say 30 mins, Meaning I add a set of
JSON document every 30 mins to each of the above five types. However only
on of my object type's have timestamp as a part of JSON data. I am using
elasticsearch 1.4 and Kibana 3. I can't seem to sepcify the index for the
Kibana dashboard. It does expect a timestamp value.
Because of this I suspect I am limited in the kinds of graphs that I can
plot.I would like to plot dual axis graphs and some time series data.Is
this correct assumption?
Is the index that Kibana is looking for the same as the index in
elasticsearch. In other words Should I rather use the timestamp value (of
when I load the data into elasticsearch) as the elasticsearch rather than
some constant value like bits used in the above example.
As my data does not have the timestamp inherently, What format should my
timestamp (that I am supposed to use as the index have, If I should)
When you mention timestamp in my docs, Do you mean that I actually replace
the Elasticsearch 'index' with timestamp. If yes is there a python library
perhaps that does that for me?
Regards,
Karthik.
On Friday, 20 March 2015 05:52:46 UTC+13, Mark Walkom wrote:
KB reads data from Elasticsearch, so yeah an index is the same thing for
both.
Basically you either need a timestamp in your docs to use KB3, or move to
KB4.
All these object types are inserted into the same index bits. The data
is inserted at regular intervals of say 30 mins, Meaning I add a set of
JSON document every 30 mins to each of the above five types. However only
on of my object type's have timestamp as a part of JSON data. I am using
elasticsearch 1.4 and Kibana 3. I can't seem to sepcify the index for the
Kibana dashboard. It does expect a timestamp value.
Because of this I suspect I am limited in the kinds of graphs that I can
plot.I would like to plot dual axis graphs and some time series data.Is
this correct assumption?
Is the index that Kibana is looking for the same as the index in
elasticsearch. In other words Should I rather use the timestamp value (of
when I load the data into elasticsearch) as the elasticsearch rather than
some constant value like bits used in the above example.
As my data does not have the timestamp inherently, What format should my
timestamp (that I am supposed to use as the index have, If I should)
I use the following script to enable timestamps for all of my document
types inside my id 'bits'. when I visualize it using Kibana3, I can't seem
to find timestamp field come up there. Am I doing somethign wrong? Do I
need to do something more?
On Thursday, 26 March 2015 09:49:19 UTC+13, Mark Walkom wrote:
I mean you need a field in your document containing a timestamp.
On 26 March 2015 at 07:15, Karthik Sharma <karthik...@gmail.com
<javascript:>> wrote:
When you mention timestamp in my docs, Do you mean that I actually
replace the Elasticsearch 'index' with timestamp. If yes is there a python
library perhaps that does that for me?
Regards,
Karthik.
On Friday, 20 March 2015 05:52:46 UTC+13, Mark Walkom wrote:
KB reads data from Elasticsearch, so yeah an index is the same thing for
both.
Basically you either need a timestamp in your docs to use KB3, or move
to KB4.
All these object types are inserted into the same index bits. The
data is inserted at regular intervals of say 30 mins, Meaning I add a set
of JSON document every 30 mins to each of the above five types. However
only on of my object type's have timestamp as a part of JSON data. I am
using elasticsearch 1.4 and Kibana 3. I can't seem to sepcify the index
for the Kibana dashboard. It does expect a timestamp value.
Because of this I suspect I am limited in the kinds of graphs that I
can plot.I would like to plot dual axis graphs and some time series data.Is
this correct assumption?
Is the index that Kibana is looking for the same as the index in
elasticsearch. In other words Should I rather use the timestamp value (of
when I load the data into elasticsearch) as the elasticsearch rather than
some constant value like bits used in the above example.
As my data does not have the timestamp inherently, What format should
my timestamp (that I am supposed to use as the index have, If I should)
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.