The Controller service provides the API for orchestrating a
collection of debugger agents to perform debugging tasks. These
agents are each attached to a process of an application which may
include one or more replicas.
The debugger agents register with the Controller to identify the
application being debugged, the Debuggee. All agents that register
with the same data, represent the same Debuggee, and are assigned
the same debuggee_id.
The debugger agents call the Controller to retrieve the list of
active Breakpoints. Agents with the same debuggee_id get the
same breakpoints list. An agent that can fulfill the breakpoint
request updates the Controller with the breakpoint result. The
controller selects the first result received and discards the rest
of the results. Agents that poll again for active breakpoints will
no longer have the completed breakpoint in the list and should
remove that breakpoint from their attached process.
The Controller service does not provide a way to retrieve the
results of a completed breakpoint. This functionality is available
using the Debugger service.
The Controller service provides the API for orchestrating a
collection of debugger agents to perform debugging tasks. These
agents are each attached to a process of an application which may
include one or more replicas.
The debugger agents register with the Controller to identify the
application being debugged, the Debuggee. All agents that register
with the same data, represent the same Debuggee, and are assigned
the same debuggee_id.
The debugger agents call the Controller to retrieve the list of
active Breakpoints. Agents with the same debuggee_id get the
same breakpoints list. An agent that can fulfill the breakpoint
request updates the Controller with the breakpoint result. The
controller selects the first result received and discards the rest
of the results. Agents that poll again for active breakpoints will
no longer have the completed breakpoint in the list and should
remove that breakpoint from their attached process.
The Controller service does not provide a way to retrieve the
results of a completed breakpoint. This functionality is available
using the Debugger service.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[],[],null,["# Package controller2 (1.7.0)\n\nVersion latestkeyboard_arrow_down\n\n- [1.7.0 (latest)](/python/docs/reference/clouddebugger/latest/google.cloud.debugger_v2.services.controller2)\n- [1.6.1](/python/docs/reference/clouddebugger/1.6.1/google.cloud.debugger_v2.services.controller2)\n- [1.5.0](/python/docs/reference/clouddebugger/1.5.0/google.cloud.debugger_v2.services.controller2)\n- [1.4.3](/python/docs/reference/clouddebugger/1.4.3/google.cloud.debugger_v2.services.controller2)\n- [1.3.2](/python/docs/reference/clouddebugger/1.3.2/google.cloud.debugger_v2.services.controller2)\n- [1.2.1](/python/docs/reference/clouddebugger/1.2.1/google.cloud.debugger_v2.services.controller2)\n- [1.1.0](/python/docs/reference/clouddebugger/1.1.0/google.cloud.debugger_v2.services.controller2)\n- [1.0.2](/python/docs/reference/clouddebugger/1.0.2/google.cloud.debugger_v2.services.controller2)\n- [0.1.5](/python/docs/reference/clouddebugger/0.1.5/google.cloud.debugger_v2.services.controller2) \nAPI documentation for `debugger_v2.services.controller2` package. \n\nClasses\n-------\n\n### [Controller2AsyncClient](/python/docs/reference/clouddebugger/latest/google.cloud.debugger_v2.services.controller2.Controller2AsyncClient)\n\nThe Controller service provides the API for orchestrating a\ncollection of debugger agents to perform debugging tasks. These\nagents are each attached to a process of an application which may\ninclude one or more replicas.\n\nThe debugger agents register with the Controller to identify the\napplication being debugged, the Debuggee. All agents that register\nwith the same data, represent the same Debuggee, and are assigned\nthe same `debuggee_id`.\n\nThe debugger agents call the Controller to retrieve the list of\nactive Breakpoints. Agents with the same `debuggee_id` get the\nsame breakpoints list. An agent that can fulfill the breakpoint\nrequest updates the Controller with the breakpoint result. The\ncontroller selects the first result received and discards the rest\nof the results. Agents that poll again for active breakpoints will\nno longer have the completed breakpoint in the list and should\nremove that breakpoint from their attached process.\n\nThe Controller service does not provide a way to retrieve the\nresults of a completed breakpoint. This functionality is available\nusing the Debugger service.\n\n### [Controller2Client](/python/docs/reference/clouddebugger/latest/google.cloud.debugger_v2.services.controller2.Controller2Client)\n\nThe Controller service provides the API for orchestrating a\ncollection of debugger agents to perform debugging tasks. These\nagents are each attached to a process of an application which may\ninclude one or more replicas.\n\nThe debugger agents register with the Controller to identify the\napplication being debugged, the Debuggee. All agents that register\nwith the same data, represent the same Debuggee, and are assigned\nthe same `debuggee_id`.\n\nThe debugger agents call the Controller to retrieve the list of\nactive Breakpoints. Agents with the same `debuggee_id` get the\nsame breakpoints list. An agent that can fulfill the breakpoint\nrequest updates the Controller with the breakpoint result. The\ncontroller selects the first result received and discards the rest\nof the results. Agents that poll again for active breakpoints will\nno longer have the completed breakpoint in the list and should\nremove that breakpoint from their attached process.\n\nThe Controller service does not provide a way to retrieve the\nresults of a completed breakpoint. This functionality is available\nusing the Debugger service."]]
