Reference documentation and code samples for the Stackdriver Debugger V2 Client class Controller2Client.
Service Description: 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.
This class provides the ability to make remote calls to the backing service through method calls that map to API methods.
This class is currently experimental and may be subject to changes. See Google\Cloud\Debugger\V2\Controller2Client for the stable implementation
Namespace
Google \ Cloud \ Debugger \ V2 \ ClientMethods
__construct
Constructor.
Parameters | |
---|---|
Name | Description |
options |
array
Optional. Options for configuring the service API wrapper. |
↳ apiEndpoint |
string
The address of the API remote host. May optionally include the port, formatted as "
|
↳ credentials |
string|array|FetchAuthTokenInterface|CredentialsWrapper
The credentials to be used by the client to authorize API calls. This option accepts either a path to a credentials file, or a decoded credentials file as a PHP array. Advanced usage: In addition, this option can also accept a pre-constructed Google\Auth\FetchAuthTokenInterface object or Google\ApiCore\CredentialsWrapper object. Note that when one of these objects are provided, any settings in $credentialsConfig will be ignored. |
↳ credentialsConfig |
array
Options used to configure credentials, including auth token caching, for the client. For a full list of supporting configuration options, see Google\ApiCore\CredentialsWrapper::build() . |
↳ disableRetries |
bool
Determines whether or not retries defined by the client configuration should be disabled. Defaults to |
↳ clientConfig |
string|array
Client method configuration, including retry settings. This option can be either a path to a JSON file, or a PHP array containing the decoded JSON data. By default this settings points to the default client config file, which is provided in the resources folder. |
↳ transport |
string|TransportInterface
The transport used for executing network requests. May be either the string |
↳ transportConfig |
array
Configuration options that will be used to construct the transport. Options for each supported transport type should be passed in a key for that transport. For example: $transportConfig = [ 'grpc' => [...], 'rest' => [...], ]; See the Google\ApiCore\Transport\GrpcTransport::build() and Google\ApiCore\Transport\RestTransport::build() methods for the supported options. |
↳ clientCertSource |
callable
A callable which returns the client cert as a string. This can be used to provide a certificate and private key to the transport layer for mTLS. |
listActiveBreakpoints
Returns the list of all active breakpoints for the debuggee.
The breakpoint specification (location
, condition
, and expressions
fields) is semantically immutable, although the field values may
change. For example, an agent may update the location line number
to reflect the actual line where the breakpoint was set, but this
doesn't change the breakpoint semantics.
This means that an agent does not need to check if a breakpoint has changed when it encounters the same breakpoint on a successive call. Moreover, an agent should remember the breakpoints that are completed until the controller removes them from the active list to avoid setting those breakpoints again.
The async variant is Google\Cloud\Debugger\V2\Client\Controller2Client::listActiveBreakpointsAsync() .
Parameters | |
---|---|
Name | Description |
request |
Google\Cloud\Debugger\V2\ListActiveBreakpointsRequest
A request to house fields associated with the call. |
callOptions |
array
Optional. |
↳ retrySettings |
RetrySettings|array
Retry settings to use for this call. Can be a Google\ApiCore\RetrySettings object, or an associative array of retry settings parameters. See the documentation on Google\ApiCore\RetrySettings for example usage. |
Returns | |
---|---|
Type | Description |
Google\Cloud\Debugger\V2\ListActiveBreakpointsResponse |
registerDebuggee
Registers the debuggee with the controller service.
All agents attached to the same application must call this method with
exactly the same request content to get back the same stable debuggee_id
.
Agents should call this method again whenever google.rpc.Code.NOT_FOUND
is returned from any controller method.
This protocol allows the controller service to disable debuggees, recover
from data loss, or change the debuggee_id
format. Agents must handle
debuggee_id
value changing upon re-registration.
The async variant is Google\Cloud\Debugger\V2\Client\Controller2Client::registerDebuggeeAsync() .
Parameters | |
---|---|
Name | Description |
request |
Google\Cloud\Debugger\V2\RegisterDebuggeeRequest
A request to house fields associated with the call. |
callOptions |
array
Optional. |
↳ retrySettings |
RetrySettings|array
Retry settings to use for this call. Can be a Google\ApiCore\RetrySettings object, or an associative array of retry settings parameters. See the documentation on Google\ApiCore\RetrySettings for example usage. |
Returns | |
---|---|
Type | Description |
Google\Cloud\Debugger\V2\RegisterDebuggeeResponse |
updateActiveBreakpoint
Updates the breakpoint state or mutable fields.
The entire Breakpoint message must be sent back to the controller service.
Updates to active breakpoint fields are only allowed if the new value
does not change the breakpoint specification. Updates to the location
,
condition
and expressions
fields should not alter the breakpoint
semantics. These may only make changes such as canonicalizing a value
or snapping the location to the correct line of code.
The async variant is Google\Cloud\Debugger\V2\Client\Controller2Client::updateActiveBreakpointAsync() .
Parameters | |
---|---|
Name | Description |
request |
Google\Cloud\Debugger\V2\UpdateActiveBreakpointRequest
A request to house fields associated with the call. |
callOptions |
array
Optional. |
↳ retrySettings |
RetrySettings|array
Retry settings to use for this call. Can be a Google\ApiCore\RetrySettings object, or an associative array of retry settings parameters. See the documentation on Google\ApiCore\RetrySettings for example usage. |
Returns | |
---|---|
Type | Description |
Google\Cloud\Debugger\V2\UpdateActiveBreakpointResponse |
listActiveBreakpointsAsync
Parameters | |
---|---|
Name | Description |
request |
Google\Cloud\Debugger\V2\ListActiveBreakpointsRequest
|
optionalArgs = [] |
array
|
Returns | |
---|---|
Type | Description |
GuzzleHttp\Promise\PromiseInterface |
registerDebuggeeAsync
Parameters | |
---|---|
Name | Description |
request |
Google\Cloud\Debugger\V2\RegisterDebuggeeRequest
|
optionalArgs = [] |
array
|
Returns | |
---|---|
Type | Description |
GuzzleHttp\Promise\PromiseInterface |
updateActiveBreakpointAsync
Parameters | |
---|---|
Name | Description |
request |
Google\Cloud\Debugger\V2\UpdateActiveBreakpointRequest
|
optionalArgs = [] |
array
|
Returns | |
---|---|
Type | Description |
GuzzleHttp\Promise\PromiseInterface |