@timestamp offset
Posted: Wed Jan 21, 2015 6:40 pm
Hello,
I have 3 hour offset, EST vs PST between @timestamp value and timestamp in the messages. How can I correct the time so it's in pacific time?
@timestamp message
2015-01-21T18:19:47.000-08:00 21 Jan 2015 21:19:45 DEBUG org.quartz.impl.jdbcjobstore.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' retuned by: DefaultQuartzScheduler_Worker-...
2015-01-21T18:19:47.000-08:00 21 Jan 2015 21:19:42 DEBUG org.quartz.impl.jdbcjobstore.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' is desired by: DefaultQuartzScheduler_Quar...
2015-01-21T18:19:47.000-08:00 21 Jan 2015 21:19:42 INFO org.quartz.plugins.history.LoggingTriggerHistoryPlugin - Trigger CORE_JOB_GROUP.coreJobRetrievalCronTrigger completed firing job
2015-01-21T18:19:47.000-08:00 21 Jan 2015 21:19:40 DEBUG org.quartz.impl.jdbcjobstore.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' is desired by: DefaultQuartzScheduler_Quar...
I have 3 hour offset, EST vs PST between @timestamp value and timestamp in the messages. How can I correct the time so it's in pacific time?
@timestamp message
2015-01-21T18:19:47.000-08:00 21 Jan 2015 21:19:45 DEBUG org.quartz.impl.jdbcjobstore.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' retuned by: DefaultQuartzScheduler_Worker-...
2015-01-21T18:19:47.000-08:00 21 Jan 2015 21:19:42 DEBUG org.quartz.impl.jdbcjobstore.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' is desired by: DefaultQuartzScheduler_Quar...
2015-01-21T18:19:47.000-08:00 21 Jan 2015 21:19:42 INFO org.quartz.plugins.history.LoggingTriggerHistoryPlugin - Trigger CORE_JOB_GROUP.coreJobRetrievalCronTrigger completed firing job
2015-01-21T18:19:47.000-08:00 21 Jan 2015 21:19:40 DEBUG org.quartz.impl.jdbcjobstore.StdRowLockSemaphore - Lock 'TRIGGER_ACCESS' is desired by: DefaultQuartzScheduler_Quar...