- CheckMates
- :
- Products
- :
- Quantum
- :
- Security Gateways
- :
- Re: Interpreting/Calculating debug timestamps
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×
Sign in with your Check Point UserCenter/PartnerMap account to access more great content and get a chance to win some Apple AirPods! If you don't have an account, create one now for free!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Interpreting/Calculating debug timestamps
Can someone explain, how to interpret the timestamps (if these are timestamps) of debug-messages. Seems not to be epoche-time or uptime counters.
For example:
@;1110845025;[cpu_4];[fw4_7];fw_log_drop_ex: Packet proto=6 x.x.x.x:56258 -> y.y.y.y:443 dropped by fw_first_packet_state_checks Reason: First packet isn't SYN;
Thanks in advance
Christian
Labels
- Labels:
-
DiagnosticsView
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I suppose it depends on how you interpret that number.
I don't know for certain, but it seems like "seconds since boot" or "seconds since kernel modules loaded" or even possibly "seconds since last policy install."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I faced the same problem and I must say that this is really a bad choice because logs without a timestamp are useless in most cases.
