AIR Task Flow and Management
Last updated
Was this helpful?
Last updated
Was this helpful?
In today's dynamic digital environment, managing tasks efficiently within a software system is crucial for reliability, flexibility, and optimal performance. This guide delves into a sophisticated task management system designed to handle a wide array of operational scenarios, focusing on task retrieval, execution, prioritization, and system resilience against failures and network disruptions.
The AIR platform features an intuitive web-based console designed to orchestrate and dispatch tasks to designated remote AIR responders effectively. Serving as the nerve center for task allocation, this console guarantees that each task is accurately assigned for execution, optimizing operational efficiency. Within this ecosystem, the assignment of a specific task to a particular asset is termed a 'task assignment,' ensuring a clear, one-to-one correspondence between tasks and assets for precise management and tracking.
To accommodate diverse operational needs and customer network policies, the system employs two primary mechanisms for task checking:
Regular Interval Checks: Tasks are checked at predefined intervals, which can be dynamically adjusted based on the system's current configuration and operational demands.
The NATS Protocol: For immediate task fetching or near real time communications with assets, the system incorporates a specialized protocol named "NATS." This protocol is designed to bypass the standard checking intervals, allowing for urgent tasks to be retrieved and executed with minimal delay
Task Checking Intervals
Task-checking intervals are not static; they vary dynamically from seconds to hours, influenced by the system's configuration. This flexibility ensures the system can adapt to changing workloads and priorities efficiently.
Certain tasks, such as "cancel tasks," receive priority in the execution queue. This prioritization is crucial to prevent delays in the cancellation process, ensuring tasks are halted promptly when required.
The system adopts a first-in-first-out (FIFO) queue model for task execution. This model guarantees that tasks are processed in the order received, with special considerations for tasks that might block or delay subsequent operations unnecessarily.
If a Tasking Assignment has been collected by the Responder but is interrupted before the completion of collection, triage, or analysis, the task will not resume where it left off. Instead, this interruption will result in a task failure. Such failures are automatically recorded within the console's tasking details.
When this occurs, the status of the task in the AIR console will reflect the failure, and it will be necessary to manually restart or initiate a new task to ensure that the intended data collection and analysis are completed. This approach ensures clarity and accuracy in the management of tasking assignments, even in cases of unexpected interruptions.
For tasks that require file uploads, such as uploading to an evidence repository, the system includes built-in retry mechanisms. These mechanisms are activated to re-attempt uploads if network issues interrupt the process. The number of retries and the specific procedures for handling these retries vary depending on the task type and the destination of the file.
Additionally, if "direct collection" is enabled for an acquisition task and there is a failure, the user must restart the acquisition process from the beginning. This ensures that all necessary data is properly collected without partial or corrupt files.
A specialized "purge local" task type exists for the efficient cleanup of local data related to completed or failed tasks. This function is integral to maintaining optimal disk space usage and system resource allocation.
This guide underscores the necessity of a flexible system capable of adapting to varied customer policies, including specific network configurations and security requirements. The choice of protocols and mechanisms for task management is influenced by these diverse operational needs.
Continuous improvement is a cornerstone of system development. The commitment to updating documentation reflects ongoing efforts to refine task management processes and system functionalities based on operational insights and technical advancements.
The guide provides an in-depth look at the technical underpinnings of the system, including the use of the "NATS" protocol, dynamic adjustment of task-checking intervals, and the logic behind task prioritization and queue management. These details offer a comprehensive understanding of the system's operational logic and its capability to handle various scenarios efficiently.
Efficient task management is pivotal in ensuring the reliability and performance of software systems. Through innovative mechanisms like the air console and NATS protocol, alongside dynamic task-checking intervals and a robust FIFO queue model, the system outlined in this guide represents a state-of-the-art solution for managing tasks in complex software environments. The emphasis on flexibility, resilience, and continuous improvement underscores the system's readiness to meet the evolving demands of modern digital operations.
