We have an issue within our organization, with the timestamp in Kibana.
Our Orchestrator is connected to ElasticSearch and the whole view of our Robot’s run we have in Kibana.
The problem is that log messages from our Robot’s are not displaying in a correct order, as you can see on the attached screen 5 logs were performed in the same time, which of course it’s not a true. Sometimes it’s very annoying because firstly it’s saying ‘Complete get transaction data’ and after that ‘Started get transaction data’ - it should be the other way around
Do you guys have any advices, ideas what settings should we change?
Maybe it’s just a way of breaking seconds into smaller from this format HH:mm:ss.SSS ?
Ok, you've got @timestamp and timeStamp. The former is usually the default that Kibana will pick when it creates an index pattern, the latter would be something that your app is creating. But those are educated guesses at how the process works, not definite answers. If you head to Management > Settings > Index patterns, you should be able to see which is the default time field being used.
Back to your question though, you may find that there's a difference between the two timestamp fields I mentioned, and while Kibana is sorting on one, it should be using the other that you are expecting.
Checking which of those fields is the Kibana default will help clarify.
Sounds like this goes back to your software and how it's handling the data it creates and sends to Elasticsearch. As, ultimately, Kibana can only show what is provided to it.
Have you tried speaking to the software provider?
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.