Storage

data.h2.db
Response time tab data is collected continuously and stored at 1 minute intervals. This setting defines how long to retain this 1 minute interval data.
Response time tab data is rolled up at 5 minute intervals. This setting defines how long to retain this 5 minute rollup data.
Response time tab data is rolled up again at 30 minute intervals. This setting defines how long to retain this 30 minute rollup data.
Response time tab data is rolled up again at 4 hour intervals. This setting defines how long to retain this 4 hour rollup data.
This setting defines how long to retain the trace tab data.
This setting defines how long to retain the full query text on the queries tab data. The truncated query text and query stats are retained according to *.capped.db settings below.
*.capped.db
Queries, service calls and continuous profiling tab data is collected and stored at 1 minute intervals. This setting defines the size of the capped data file used to store this 1 minute interval data.
Queries, service calls and continuous profiling tab data is rolled up at 5 minute intervals. This setting defines the size of the capped data file used to store this 5 minute interval data.
Queries, service calls and continuous profiling tab data is rolled up at 30 minute intervals. This setting defines the size of the capped data file used to store this 30 minute interval data.
Queries, service calls and continuous profiling tab data is rolled up at 4 hour intervals. This setting defines the size of the capped data file used to store this 4 hour interval data.
This setting defines the size of the capped data file used to store the trace detail data (trace entries and trace profiles).
This setting defines how long to retain all 1 minute interval data. This includes response time data, query data, service call data, profile data, gauge data and error summary data. (this setting also applies to 5 second gauge data)
This setting defines how long to retain all 5 minute interval data. This includes response time data, query data, service call data, profile data, gauge data and error summary data.
This setting defines how long to retain all 30 minute interval data. This includes response time data, query data, service call data, profile data, gauge data and error summary data.
This setting defines how long to retain all 4 hour interval data. This includes response time data, query data, service call data, profile data, gauge data and error summary data.
This setting defines how long to retain all trace data. This includes individual traces and error message data.
This setting defines how long to retain the full query text on the queries tab data. The truncated query text and query stats are retained according to 1 min, 5 min, 30 min, 4 hour interval data settings above.
Updated expiration settings only apply to data collected from this point forward. Existing data is still tagged with the expiration settings in effect at the time the data was captured since using Cassandra TTL to implement expiration.
H2 data file size: {{h2DataFileSize | gtBytes}}
Table name Total bytes Row count
{{analyzedH2Table.name}} {{analyzedH2Table.bytes | number}} {{analyzedH2Table.rows | number}}
By transaction type
Transaction type Traces captured Traces captured because they were flagged as errors
{{analyzedTraceOverallCount.transactionType}} {{analyzedTraceOverallCount.count | number}} {{analyzedTraceOverallCount.errorCount | number}}
By transaction name
Transaction type Transaction name Traces captured Traces captured because they were flagged as errors
{{analyzedTraceCount.transactionType}} {{analyzedTraceCount.transactionName}} {{analyzedTraceCount.count | number}} {{analyzedTraceCount.errorCount | number}}