Inactivity period (threshold) setting
Threshold is basically the inactivity period of the users. The Threshold setting allows you to set how much after the last activity should a user be considered inactive (in seconds). The shorter the period, the more aggressive you are in saving licenses.
Example: Let's assume we have a single user license and two users: "A" and "B. User “A” logs in and starts to use Jira. User “B” will only be able to log in if user “A” was inactive for at least the time specified by threshold (ie. did not click on anything within Jira for that time). The license of user "A" will be revoked only after that amount of time.
| Note |
|---|
Value must be between 1 and 86400 seconds. |
Start License Optimizer automatically
Check this option if you want the License Optimizer to start automatically after app update or Jira restart.
Comprehensive License Count Check
License Optimizer checks the access for each user in every request and with this, creates a cluster lock for every event. (This option is enabled by default.) This can cause performance degradation in large instances where a large number of users are active at the same time.
You can uncheck this to prevent it, and in this case, LO will only lock the cluster when it is adding a user to the access group. However, if it is unchecked there is a possibility of user overflowing in the access group and users will be unable to use the application! To prevent this, when this option is disableb, configure the "Access limit" with a lower value as your possible seats in the license, thus providing a buffer size. We recommend to start with at least 5-10 user buffer value.
An example for this case:
There is a 100 user tier license applied.
There is a fixed admin group of 10 members.
In this case by default, LO can assign 90 places for other users.
The Access Limit should be configured to 95.
With 10 fixed admins, the LO sees 85 seats (95 limit - 10 fix user) as allocable and there will be 5 seats as a buffer.
Logging License Optimizer activity
Enable this to log optimizer activity and log info about the current and prevorious state of the user management by the app.