IBM Support

QRadar: Impact of a 'leap second' on QRadar

Question & Answer


How does QRadar account for leap year seconds?


The next leap year second is scheduled for June 30, 2020 at 23 hours 59 minutes 60 seconds UTC. Leap Seconds are added to account for the difference in UTC and International Atomic Time. A leap second causes an extra second to be injected into the day. QRadar accounts for this by changing the clock at 23:59:59 to 23:59:60 instead of 00:00:00. The time then runs as expected.

Leap year seconds do not affect UNIX time, so they do not affect QRadar. As an administrator, you can see this occurrence happen if you are doing a search, investigating an offense, or generating a report. This is a normal occurrence.

Where do you find more information?

[{"Product":{"code":"SSBQAC","label":"IBM Security QRadar SIEM"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"General Information","Platform":[{"code":"PF016","label":"Linux"}],"Version":"Version Independent","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

Modified date:
16 June 2018