You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, I am having some odd issue with timestamps that I am just not understanding.
For a test I am sending a batch of 250 updates, I increment the value by 1 each time and I add a second to each one.
As an example I am sending an update using a timestamp of 1432822235859 which should be:
Date in your timezone*: 5/28/2015, 10:10:36 AM
but in zabbix I am seeing it as: 2015.May.27 06:25:21
also, as part of my test I add some time to the time stamp for each iteration. What is odd is that the value should be MS, but if I add "1000" I see a 16 minute difference in zabbix (like it was treating MS as seconds).
Very confused...
The text was updated successfully, but these errors were encountered:
I wanted some batching behavior so I added an add method where the DataObject gets added to a list until it reaches a threshold and then they are all sent together. But my basic code looks like:
long time = System.currentTimeMillis();
System.out.println("Time in MS = " + Long.toString(time));
for (long i = 0; i < 300; i++)
{
long tmp = time + i;
System.out.println("Posting Time in MS = " + Long.toString(tmp));
sender.add(new DataObject(tmp,"LogstashTest","TestItem",String.valueOf(i)));
}
So, I am having some odd issue with timestamps that I am just not understanding.
For a test I am sending a batch of 250 updates, I increment the value by 1 each time and I add a second to each one.
As an example I am sending an update using a timestamp of 1432822235859 which should be:
Date in your timezone*: 5/28/2015, 10:10:36 AM
but in zabbix I am seeing it as: 2015.May.27 06:25:21
also, as part of my test I add some time to the time stamp for each iteration. What is odd is that the value should be MS, but if I add "1000" I see a 16 minute difference in zabbix (like it was treating MS as seconds).
Very confused...
The text was updated successfully, but these errors were encountered: