I don't know if this is a bug with Kibana or if my code caused this or if I am misinterpreting something. My issue is that whenever I try to manipulate my time axis to stretch beyond an hour using the buttons on Kibana, the total time displayed will be wrong. Also, something that stuck out was that the upper bound of the displayed time domain would change, even though I leave that button on Kibana set as "now" which doesn't make sense to me. I have checked my data in discover to make sure and it goes past 1 hour of data -- to about 3 hours.
{
$schema: "https://vega.github.io/schema/vega-lite/v2.json"
mark: point
data: {
url: {
%context%: true
%timefield%: log.@timestamp
index: log_datalake
body: {
size: 10000,
_source: ["log.@timestamp", "log.nbreLigne", "log.type"]
}
}
format: { property: "hits.hits" }
}
transform: [
{
calculate: "toDate(datum._source['log.@timestamp'])",
as: "time"
}
]
encoding: {
x: {
field: time
type: temporal
axis: { title: "Job" }
}
y: {
field: _source.log.nbreLigne
type: quantitative
axis: { title: "Nb line" }
}
color: {
field: _source.log.type
type: nominal
legend: { title: ' Step' }
}
shape: {
field: _source.log.type
type: nominal
}
}
}
When I use : JSON.stringify(VEGA_DEBUG.vegalite_spec) there are errors on my field log.type