Skip to end of metadata
Go to start of metadata

Overview of "Manage ION Processes (Deprecated)" Use Case

Monitor and control all system processes and environments DEPRECATED

Tip: Key Points
UC Priority= 4 or 5: Critical, is in R2
Only boldface steps are required
<#> before a step —> lower priority
(optional) —> run-time option


Refer to the Product Description and Product Description Release 2 pages for metadata definitions.

Actors Integrated Observatory Operator (Cyber Operator)
References UC.R2.40 Monitor ION Resources
Uses UC.R2.44 Define Service Type During Runtime
Is Used By UC.R2.46 Operate Integrated Observatory Network
Is Extended By  
In Acceptance Scenarios AS.R2.01C Operate Integrated Observatory Network
Technical Notes  
Lead Team CEI
Primary Service Process Management Services
Version 1.6.1
UC Priority 4
UC Status Deprecated
UX Exposure ONC


This information summarizes the Use Case functionality.

Monitor all processes in the ION system (services, agents, user processes) and their deployment execution environment. Control process scheduling policy, executing processes, and execution sites.


Initial State

Integrated Observatory Operator is logged in.

Scenario for "Manage ION Processes (Deprecated)" Use Case

  1. The Integrated Observatory Operator calls up a Process Collection view to review process environments on the system.
    1. See UC.R2.49 Deploy Distributed Processes for further details.
    2. Additional detail: The displays should be able to discriminate/filter based on process type (a service, an agent), owner class (system, user), and specific owner.
  2. <2> The Integrated Observatory Operator calls up detailed Process Resources page views to examine resource usage for a class of processes.
    1. The ability to drill down from the ION level, through site, availability zone, Execution Engine and examine resource usage at each level is important.
    2. The ability to filter on different types of resources (CPU, CCs, connections, message I/O, message queue length) is important.
    3. If this information is not available through the Integrated Observatory in R2, it can be viewed from outside the system.
  3. Upon identifying a runaway process (using too many resources of some type), the Integrated Observatory Operator can take appropriate action.
    1. Could pause data input, or kill it.
    2. Theoretically could put it into debug mode, or move it to an isolated machine, but moving a process to an isolated machine with current in-flight context is hard.
  4. The Integrated Observatory Operator examines the scheduling policy for a process, and modifies it.
    1. Could simply increase or decrease the frequency of execution, for those processes that are scheduled by time interval.
    2. Could increase or decrease the priority allocated to the process (e.g., unix process priority in the context of the operational unit).
    3. Could create a more advanced policy, that defines the scheduling based on other parameters (CPU time used by process or machine, for example).
  5. <2> The Integrated Observatory Operator examines the scheduling policy for a group of processes, and modifies them all.

Final State

Operations continue with the changes in effect.


These comments provide additional context (usually quite technical) for editors of the use case.

Integration of the CEI processes with the Integrated Observatory COI resources infrastructure is under analysis. The ability to manage these processes from the Integrated Observatory is therefore not yet determined.

The level of process inspection within the Integrated Observatory that's required in Release 2 may need further analysis. The scenario assumes that detailed process inspection will take place outside of the Integrated Observatory.

There is some duplication of steps with UC.R2.40 Monitor ION Resources, but the details under each step are somewhat different.

(click on # to go to R2 use case)
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20
21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
61     27B


usecase usecase Delete
productdescription productdescription Delete
r2-usecase-deprecated r2-usecase-deprecated Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.