The Grail data model consists of buckets, tables, and views.
dt.entity
, are not stored in buckets and cannot be fetched directly.There is a set of predefined built-in buckets that cannot be modified, including:
default_
dt_
Name
Table
Retention
default_events
events
35 days
default_security_events
events
3 years
default_security_custom_events
events
1 year
default_bizevents
bizevents
35 days
default_logs
logs
35 days
default_metrics
metrics
15 months
default_spans
spans
10 days
dt_system_events
dt.system.events
1 year
You can create a bucket tailored to your needs. Grail buckets behave like folders in a file system and are designed for records that should be handled together. For example, you might need to store together:
Defining buckets can improve query performance by reducing query execution time and the scope of data read. Finally, having your data stored in a bucket streamlines your permission management because you can easily provide a user group or single users with access to needed data.
A maximum of 80 custom buckets can be created per environment.
For custom buckets, the possible retention periods range from 1 day to 10 years, with an additional week.
Shortening the retention period on update requests will delete the data that is over the new period.
To manage your buckets, ensure that you have configured the following permissions:
storage:bucket-definitions:read
storage:bucket-definitions:write
storage:bucket-definitions:delete
storage:bucket-definitions:truncate
With Storage Management you can:
To create a new custom Grail bucket with Storage Management you need to specify:
Latest Dynatrace
To manage your custom Grail buckets via REST API
Search for and select Dynatrace API.
In the Select a definition field, select Grail Storage Management.
Authenticate with your API token.
For details, see Authentication.
Perform one of the following actions.