Full license usage log and extend type
One of my client want to measure duration time of login for each user from full license log
However, we noticed there is no extend type between checkout and checkin.
If there is extend type, then expiration date of checkin has different time, so we can calculate difference between. but without extend type time for checkout and checkin are exactly same.
What we want to know is how extend operation is initiated?
Is there time interval or some action to be recorded as extend type?
License usage reporting
https://jazz.net/wiki/bin/view/Main/LicenseReporting
Note: Description - The type of operation being performed, possibly a checkin, extend, or release.
However, we noticed there is no extend type between checkout and checkin.
If there is extend type, then expiration date of checkin has different time, so we can calculate difference between. but without extend type time for checkout and checkin are exactly same.
What we want to know is how extend operation is initiated?
Is there time interval or some action to be recorded as extend type?
License usage reporting
https://jazz.net/wiki/bin/view/Main/LicenseReporting
Note: Description - The type of operation being performed, possibly a checkin, extend, or release.
Accepted answer
user login starts a license lease marked by a checkout and bounded by an expiration time. Any action by that user thereafter will extend his lease time and show up in the log with a new(extended) expiration time. So, as long as the user is active performing further operations, his lease expiration time keeps extending. In the logs you will see these entries with the type marked as extend.
The lease finally comes to an end when either he logs out (checkin) or goes inactive and the expiration time is reached (expired).
typical entries in the log would look like:
checkout
extend(s) [provided user performed some action after login]
checkin / expire
This lease session will be identified by a lease id and the start time for all these entries will match. The expiration times are incremental (mostly) when an extend (user action) is seen. The final checkin / expire will show the expiration time to be same as the latest extend.
hope it helps
The lease finally comes to an end when either he logs out (checkin) or goes inactive and the expiration time is reached (expired).
typical entries in the log would look like:
checkout
extend(s) [provided user performed some action after login]
checkin / expire
This lease session will be identified by a lease id and the start time for all these entries will match. The expiration times are incremental (mostly) when an extend (user action) is seen. The final checkin / expire will show the expiration time to be same as the latest extend.
hope it helps
One other answer
Comments
Yes, I have seen these but this dose not help our customer.
If This Enhancement (#60402) is implemented, then we probably could satisfy their need. At this stage, extend type dose not always there and can not figure out the rule or the condition of recording it.
It does not seems to be every X minutes or something rather based on some actions, which is related license usage.