Create a tracing account
POST/v1/account-management/consumption/tracing-accounts
Creates a tracing sub-account under a Consumption owner account.
maxDailyGB is the account's soft limit, and is required.
Available for Consumption accounts only. If the account is not a Consumption account, the request returns 400.
Please ensure to change the region in the URL to match your account's region.
Request
- application/json
Body
required
Email address of an active user of the owner account.
Name of the tracing account.
IDs of accounts that can access the tracing account's data. Can be empty.
The maximum volume of data, in GB, that the tracing account can index per calendar day. This is the account's soft limit. The account is suspended once its daily usage exceeds this value, so 0 suspends it as soon as it receives any data.
Responses
- 200
- 400
- 403
OK
- application/json
- Schema
- Example (from schema)
Schema
- Array [
- ]
ID of the tracing account.
Name of the tracing account.
The maximum volume of data, in GB, that the tracing account can index per calendar day. This is the account's soft limit - the same value the soft limit endpoints read and write. Null if not set.
Number of days that trace data is retained.
Account creation time, in epoch seconds.
authorizedAccounts object[]
Accounts that can access the tracing account's data.
Possible values: [MONTHLY_SPANS_QUOTA_EXCEEDED, DAILY_INDEXING_THRESHOLD_EXCEEDED, DAILY_CONSUMPTION_USAGE_EXCEEDED, NOT_SUSPENDED]
Whether the account is suspended, and why.
{
"accountId": 0,
"accountName": "string",
"maxDailyGB": 0,
"retention": 0,
"createdAt": 0,
"authorizedAccounts": [
{
"accountId": 0,
"accountName": "string"
}
],
"suspensionState": "MONTHLY_SPANS_QUOTA_EXCEEDED"
}
The account is not a Consumption account, email does not belong to an active user of the account, or the request exceeds the account's tracing budget or number of tracing accounts.
Only the owner account can manage tracing accounts.