Introduction
On installations with the MSS license, Logsign can assign incidents to analysts automatically. Only users marked as analysts and in the Check In state take part. This article explains who receives an incident, in which order waiting incidents are assigned, and how automatic assignment affects the First Reply Time (FRT) of the SLA.
For manual assignment, see Assigning User to an Incident. For SLA settings, see SLA Management in Logsign.
Analyst Settings
Automatic assignment uses three fields on the user form. They are shown only with the MSS license and are not available for Super Admin accounts (see Users).
- Is Analyst: the user can receive incidents automatically.
- Max Incident Count: the maximum number of open incidents the analyst can own at the same time. If no value is set, the limit is 100.
- Check In: the analyst is on duty. Users that are not checked in do not receive incidents.
The limit counts only incidents with the status Open that the analyst owns.
The Incident Pool
Incidents that wait for an analyst are owned by LogsignBot. This set of incidents is called the pool. Logsign checks the pool every 60 seconds and gives the waiting incidents to checked-in analysts that are below their limit.
How a New Incident Is Assigned
When a new incident arrives, Logsign decides as follows:
- If no analyst is checked in, the incident goes to the pool.
- If the pool already holds open incidents, the new incident also goes to the pool and waits for its turn. It does not take a free analyst slot ahead of older incidents. Emergency incidents are the exception (see below).
- If the pool is empty, the incident goes directly to the checked-in analyst with the fewest open incidents, as long as that analyst is below the limit.
- If every checked-in analyst is at the limit, the incident goes to the pool.
Because of step 2, a new incident can wait in the pool for up to one pool check (about 60 seconds) even when an analyst has free capacity.
Order of Pool Assignment
On each pool check, Logsign sorts the pool by risk score, highest first. When two incidents have the same risk score, the older incident (earlier generation time) is assigned first. Logsign then gives the incidents to the available analysts in turn, until each analyst reaches the limit or the pool is empty.
The order uses the risk score of the incident. It does not use the Priority value that an analyst can change on the incident.
Emergency Incidents
An incident with the risk level Emergency does not wait in the pool. It is assigned directly to the checked-in analyst with the fewest open incidents. For these incidents an analyst can go over the limit by 10% of the limit (at least 1). For example, an analyst with a limit of 10 can receive one more Emergency incident at 10 open incidents. If no analyst has room even with this extra slot, the incident goes to the pool.
When an Analyst Checks Out
When an analyst is no longer checked in, Logsign moves the analyst's open incidents to the checked-in analysts on the next pool check. If no analyst has free capacity, these incidents go back to the pool.
Effect on First Reply Time
Automatic assignment from the pool does not count as the first reply. The FRT of the incident stays open until a person takes the first action on the incident, the same as with a direct assignment. This way the SLA First Reply column and the Frt bar measure the analyst response, not the LogsignBot assignment.
Troubleshooting
| Symptom | Possible cause | What to do |
|---|---|---|
| Many incidents stay with LogsignBot. | All checked-in analysts are at their Max Incident Count, or no analyst is checked in. | Increase Max Incident Count or ask more analysts to check in. |
| Incidents stay with LogsignBot for more than a few minutes, even though checked-in analysts have free capacity. | The pool check does not run. | Contact Logsign Support. |
| An incident waits about one minute before it is assigned. | The pool held other incidents when it arrived, so it waits for the next pool check. | This is expected behavior. |