Use the Server Settings Performance Warehouse pane to set up connection details to use an external database. Use the external database to store Performance Warehouse data, manage System Profiles, and set the maximum duration for how data is kept. See Performance Warehouse Administration for more information.
Cyclic measurement data persists in the embedded Derby database or in a SQL DBMS (DB2, Oracle, PostgreSQL and Microsoft SQL Server / SQL Azure). The embedded database is for testing only and its usage is limited to certain licenses. See Embedded Performance Warehouse Usage Restrictions for more information. See System Requirements for SQL DBMS minimum supported versions.
Changing the AppMon Performance Warehouse database
You can only change the database when a database is not connected. Follow these steps to change the Performance Warehouse database.
- Choose Settings > Dynatrace Server, Performance Warehouse > Connection Details and click Disconnect to disconnect the current database.
- Provide a database type, host, port, user, and password to specify the new database. The Java Cryptographic Extension encrypts the password.
- Click Test Connection to verify that the Performance Warehouse database is available.
- Click Connect to connect to the database and create the tables.
The AppMon Performance Warehouse is now set up to the configured database. Click the Rebuild Schema to rebuild the whole database schema.
When you rebuild the schema, all Performance Warehouse data is lost.
See Performance Warehouse Administration for more database connection information.
Manage System Profiles
The System Profiles Management tab of the Performance Warehouse pane shows the System Profiles available in the Performance Warehouse. To remove unnecessary measurements or incidents from a System Profile’s Performance Warehouse storage, select a System Profile and click Delete Measurements/Incidents. Click Remove to delete a System Profile and all its data from the Performance Warehouse.
Use the Storage Management tab to set the length of time data are kept in high, medium, and low resolutions and when they are consolidated into the next lower level. The data point interval is ten seconds for data in memory and one minute, hour, or day for high, medium, or low resolutions in the database respectively. See Resolution for more information.
Performance Warehouse database versus session store files
The Performance Warehouse database continuously stores data from both system monitoring such as CPU and memory usage, and PurePath timings. Data is stored at 10-seconds granularity at the highest resolution. Granularity is diminished at the medium (hour) and low (day) resolutions.
To explicitly store parts of such live sessions, click Cockpit > Session Storage > Start / Stop Recording or > Store Session in the AppMon Client and right-click a System Profile. Click Cockpit > Session Storage to see them. You access them in the AppMon Server. The Export Session option zips up the stored session files (
.dts). The Import Session option from the file system makes it available in Cockpit > Offline > Local Sessions.
Stored session files can contain a memory dump, thread dump, sampling, or full PurePath information. Stored PurePath Sessions include time series data also.