Historical Queries & Metrics
The Historical Queries & Metrics page allows you to display system metrics and queries executed during a specified time period. Queries may also be filtered by database and/or user.
Set the time period to display by entering dates and times in the From and To date and time fields. You can enter dates by typing them into the date field or by choosing from the pop-up calendar. Enter 24-hour times in HH:MM format.
To restrict queries that display in the query table at the bottom of the page, enter a Greenplum database name in the Database field, a user name in the User field, or both. Filtering by database and user only affects the queries displayed in the table. The metrics displayed in charts include all activity during the selected time period.
Click Search to display results that match your criteria.
Charts of the following metrics are available. Show or hide them at any time with the checklist at the upper right of the view.
The number of queries running and the number of queries queued to run.
The percentage CPU used by system processes and the percentage CPU used by user processes.
Percentage of memory in use.
Disk read and write rates in megabytes per second.
Network I/O read and write rates in megabytes per second. Network metrics include traffic over all NICs (network interface cards), including internal interconnect and administrative traffic.
System load average for 1-minute, 5-minute, and 15-minute periods.
Percentage of swap space used.
The Query table displays queries that were active during the specified time period, including queries that started before or finished after the specified time. However, queries that are still active are not included in the table; these queries can be viewed on the Query Monitor page.
The query table has the following columns:
An identification string for the query. In the Console, this looks like “1295397846-56415-2”.
The final status of the query. This can be one of the following:
The Greenplum Database user who submitted the query.
The name of the database that was queried.
The time the query was submitted to the query planner.
The amount of time a query spent in the queue before it was executed.
The amount of time the query required to produce a result.
The time the query completed or was cancelled.
The amount of CPU skew. CPU skew occurs when query executor processes for one segment use a disproportionate amount of CPU compared to processes for other segments executing the query. This value is the coefficient of variation for the CPU used by processes running this query on each segment, multiplied by 100. For example, a value of .95 is shown as 95.
A measure of row skew in the system. Row skew occurs when one segment produces a disproportionate number of rows for a query. This value is the coefficient of variation for the Rows Out metric of all iterators across all segments for this query, multiplied by 100. For example, a value of .95 is shown as 95.
The name of the resource queue for the query.
Each query inherits the priority assigned to its resource queue.
For more information about Resource Queues and Query Plans, refer to the Greenplum Database Administrator Guide.