This topic gives you reference information about the Google Stackdriver Trace service (csb-google-stackdriver-trace). It details the plans, configuration parameters, and binding credentials.
Caution The Google Stackdriver Trace service offering is currently in beta and is intended for evaluation and test purposes only. Do not use this product in a production environment.
Plans
The table below lists the plans for Google Stackdriver Trace:
| Plan | Description |
|---|---|
| default | Default plan |
Plan Configuration Parameters
When configuring Cloud Service Broker for GCP you can add additional plans. For how to configure plans, see Configure Services with Cloud Service Broker for GCP.
The following table lists parameters that can only be configured for additional plans:
| Parameter Name | Values | Default |
|---|---|---|
name* | The plan name | n/a |
id* | A unique GUID | n/a |
description* | Description of the new plan | n/a |
display_name | Name to use when displaying plan in marketplace | n/a |
free | When false, Service Instances of this Service Plan have a cost | true |
bindable | Specifies whether Service Instances of the Service Plan can bind to applications | true |
plan_updateable | Whether the Plan supports upgrade/downgrade/sidegrade to another version | true |
* Required
Configuration Parameters
You can provision a service by running:
cf create-service csb-google-stackdriver-trace PLAN-NAME SERVICE-INSTANCE-NAME
There are no configuration parameters that you can configure when provisioning a service.
Binding Credentials
You can bind a service by running:
cf bind-service APP-NAME SERVICE-INSTANCE --binding-name BINDING-NAME
The format for binding credentials for Google Stackdriver Trace:
{
"Email" : "SERVICE-ACCOUNT-EMAIL",
"Name" : "SERVICE-ACCOUNT-NAME",
"PrivateKeyData" : "SERVICE-ACCOUNT-PRIVATE-KEY",
"Credentials" : "SERVICE-ACCOUNT-CREDENTIALS",
"ProjectId" : "GCP-PROJECT-ID",
"UniqueId" : "SERVICE-ACCOUNT-UNIQUE-ID"
}
Content feedback and comments