# Team Monitor View

A special view exists for monitoring which team instances have been created and whether each of them is currently active or not. When debugging callin bindings which do not trigger while they are intended to do so, the team monitor should provide first help to find out whether there is any active instance of the team being considered. If no active instance exists, callins can not trigger.

The team monitor view is a variant of the variables view with the following features:

- Display all instances of all teams in the system.
- Display the activation state of each team instance as one of
  a team instance in not active (for the current thread, if one is selected)
  a team instance is active, either globally or for the thread selected in the debug view
  a team instance is implicitly active due to executing a team or role method.
- Change the activation state of a team using the context menu (Activate Team or Deactivate Team).
  This operation affects the currently selected thread. If global (de)activation should be achieved, select the debug target () instead of any individual thread.
- Inspect fields of a team instance or perform any operation inherited from the variables view.
  Note, that filtering of OT/J Internal Variables is also supported (and enabled by default).

Note that teams may only appear if a thread is currently suspended. If teams are visible while all threads are running, the Activate Team or Deactivate Team options cannot be performed.

Technical note: When debugging an Eclipse application or OSGi fragment with OT/Equinox enabled, the team monitor can only work if an open Object Teams Plug-in Project can be found in the workspace. If this requirement is not met a corresponding warning will be logged.