The task types are CLI, SNMP, API. Each task type has its own task queue.
•CLI Task: Execute CLI commands. Example: show run.
•SNMP Task: Execute SNMP, Ping and Trace commands. Example: ping 172.168.28.100
•API Task: Execute API task. Example: retrieve data from SDN devices.
Priorities vary from different tasks, and each type of task queue is divided into 5 different priority levels. Queues of different priority levels have different thread configurations.
The current system divides tasks into 6 different priority levels, and when the task thread is low on resources, tasks with higher priority are executed first.
Priority Queue |
Priority |
Task Type Description |
Change Management Queue |
5 |
Queue used by change management tasks. It has the highest priority. |
Direct Live Access Queue |
4 |
Queue used by Direct Live Access tasks, including: •Discover •Benchmark •On-demand map related tasks, such as running Qapp/Data View Template, or retrieving live data for the map •On-demand NI running tasks |
Interactive Queue |
3 |
Queue used by interactive tasks, which only include parser variable retrieval when editing the NIC in the current version. |
Adaptive Monitoring Primary Probe Queue |
2 |
Queue used by the primary probe in Adaptive Monitoring, includes: Adaptive Monitoring Primary Probe tasks. |
Drill-down Automation Queue |
1 |
Queue used by Adaptive Monitoring Triggered task, includes: •Triggered NI •Triggered CLI •Triggered secondary probe |
Schedule Task Queue |
0 |
Queue used by scheduled task, includes: •Scheduled Data View Template •Scheduled Parser •Scheduled Qapp |
•Reserved Thread Count: the number of threads reserved for this priority, which cannot be seized by other priorities.
•Expected Thread Count: the number of threads expected to be acquired in the priority queue. The system prioritizes the allocation of threads for each priority level according to the expected thread count. If the number of tasks in the priority queue is less than the expected thread count, i.e., not full, the remaining threads may be taken by other high-priority tasks.
•Max Thread Count: The maximum number of threads that can be used in the priority queue. The higher priority will preempt threads that are not applicable to the lower priority, but the total number of threads used cannot exceed the Max Thread Count.
Threads per queue are not fixed and are always dynamically allocated.
▪CLI Thread Configuration
Priority Queue |
Priority |
Reserved Thread Count |
Expected Thread Count |
Max Thread Count |
Schedule Queue |
0 |
0 |
30 |
180 |
Interactive Queue |
3 |
0 |
20 |
180 |
Drill-Down Queue |
1 |
0 |
40 |
180 |
Direct Live Access Queue |
4 |
0 |
40 |
180 |
Change Management Queue |
5 |
0 |
40 |
180 |
Adaptive Monitoring Primary Probe Queue |
2 |
50 |
50 |
50 |
▪SNMP Thread Configuration
Priority Queue |
Priority |
Reserved Thread Count |
Expected Thread Count |
Max Thread Count |
Change Management Queue |
5 |
0 |
50 |
200 |
Direct Live Access Queue |
4 |
0 |
50 |
200 |
Interactive Queue |
3 |
0 |
40 |
200 |
Adaptive Monitoring Primary Probe Queue |
2 |
100 |
100 |
100 |
Drill-Down Queue |
1 |
0 |
60 |
200 |
Schedule Queue |
0 |
0 |
30 |
200 |
▪API Thread Configuration
Priority Queue |
Priority |
Reserved Thread Count |
Expected Thread Count |
Max Thread Count |
Change Management Queue |
5 |
0 |
4 |
32 |
Direct Live Access Queue |
4 |
0 |
4 |
32 |
Interactive Queue |
3 |
0 |
4 |
32 |
Adaptive Monitoring Primary Probe Queue |
2 |
0 |
4 |
32 |
Drill-Down Queue |
1 |
0 |
4 |
32 |
Schedule Queue |
0 |
0 |
4 |
32 |