You can use the information_schema.engine_history view to return information about each engine’s history in an account. The view shows operations performed on each engine, including creation, deletion, starts, stops, resizing, and logical operations like renames. It is often useful to filter this view to a particular engine. In the example below, a filter is applied to look at the history of engines starting with capacity_test_. By default, shows the events from the last 30 days.

SELECT
  *
FROM
  information_schema.engine_history
WHERE
  engine_name LIKE 'capacity_test_%'

Columns in information_schema.engines_history

Each row has the following columns with information about each engine.

Column NameData TypeDescription
engine_nameTEXTThe last known name of the engine. Either reflects the current name or the name at time of deletion.
engine_ownerTEXTThe name of the user who owns the engine.
cluster_idINTOrdinal numbers to identify engine clusters.
typeTEXT(5)The node type used in a given engine (S, M, L, or XL).
familyTEXTThe family of a given engine. Choose from STORAGE_OPTIMIZED or COMPUTE_OPTIMIZED.
nodesINTThe number of nodes in each of the cluster of the engine.
clustersINTThe number of clusters used in the engine.
auto_startBOOLEANIf TRUE, automatically start the engine if it is in a stopped state when a query comes in.
auto_stopINTAutomatically stop the engine after specified number of minutes.
auto_vacuumBOOLEANIndicates whether VACUUM is enabled or disabled by the user. Could also be NULL to indicate that VACUUM is automatically enabled by default.
initially_stoppedBOOLEANIf TRUE, the engine will not be automatically started after creation.
urlTEXTThe engine URL used by the users to issue queries to the engine.
default_databaseTEXTDefault database for the engine as specified by the user.
versionTEXTThe engine version.
event_typeTEXTThe name of the event.
event_reasonTEXTThe reason that the engine event was triggered.
event_statusTEXTThe status of the event, indicating whether the action corresponding to the event has succeeded, failed or is in process. Can have one of the following values: SUCCEEDED, FAILED or IN_PROGRESS.
event_start_timeTIMESTAMPTZThe time when the event was initiated.
event_finish_timeTIMESTAMPTZThe time when the event was completed.
user_nameTEXTThe user who triggered the event.
descriptionTEXTThe description of the engine as specified by the user.
query_idTEXTThe unique identifier for the SQL query used for engine operations.