Create a sub account
POST/v1/account-management/time-based-accounts
Creates a new logging sub account. Must be run with an API token from the main account. Please ensure to change the region in the URL to match your account's region.
Request
- application/json
Body
-
If
isFlexible=false
, don't send this field or send it null. -
If
isFlexible=true
, this parameter is required. It determines the volume that is reserved for the account. -
If
isFlexible=false
this is the only capacity reserved for use by the account. Cannot be null. -
If
isFlexible=true
this is used to limit the account's access to shared volume. Once the data shipped to the account exceeds the account's reserved capacity, the account can continue to index data up to itsmaxDailyGB
, as long as shared volume is available. -
If null (and
isFlexible=true
), the account is uncapped and can continue to index data as long as shared volume is available.
Possible values: Value must match regular expression ^[_A-Za-z0-9-\+]+(\.[_A-Za-z0-9-]+)*@[A-Za-z0-9-]+(\.[A-Za-z0-9-]+)*(\.[A-Za-z]{2,})$
Account administrator's email address
Name of the account
Default value: false
The maximum volume of data that an account can index per calendar day.
Possible values: >= 1
How long log data is stored and searchable in Kibana, in days.
Default value: false
If other accounts can search this account's logs, true
. Otherwise, false
.
Default value: false
If users of the main account can access this account, true
. Otherwise, false
.
IDs of accounts that can access this account's data. The array is required, but can be empty.
Default value: false
Adds a LogSize field to each log to record the size in bytes, to better manage the account utilization.
utilizationSettings object
Settings for logging metrics on your account utilization, such as used and expected data volume at current indexing rate.
How often utilization metrics are written to logs, in minutes
If utilization metrics are written to logs, true
. Otherwise, false
.
Responses
- 200
successful operation
- application/json
- Schema
- Example (from schema)
Schema
ID of the account
{
"accountId": 99999
}