This chapter provides a description of each monitoring view and its columns. It contains the following sections:
For examples of how to use views, see Examples.
MGMT$ALERT_CURRENT displays current information for any alerts that are logged in the Management Repository that are in a non-clear state. Only the most recent open alert in a non-clear status for a given metric is displayed through this view.
Table 14-1 MGMT$ALERT_CURRENT
Column | Description |
---|---|
TARGET_NAME |
Name of the target where the metric was collected. The target name uniquely identifies a managed target within the Management Repository. The target name typically contains the name of the managed entity that was provided by the system or database administrator. |
TARGET_TYPE |
The target type defines the set of metrics that are applicable for the target |
TARGET_GUID |
The unique global identifier for the target |
VIOLATION_GUID |
Unique identifier for the alert |
METRIC_NAME |
Name of the metric being defined |
METRIC_COLUMN |
For table metrics, the metric column contains the name of the column in the table that is being defined. If the metric that is being defined is not a table metric, the value in this column is a single space.For example, if this table describing the MGMT$TARGET_TYPE view was being defined as a table metric, Column Name, Data Type, and Description would be metric columns. |
METRIC_LABEL |
An intuitive display name for the metric that is being defined |
COLUMN_LABEL |
For table metrics, the column label contains an intuitive display name for the metric column |
KEY_VALUE |
The key value for which the alert has been recorded. For composite keys, this is the first part of the key |
KEY_VALUE2 |
For composite keys, this is the second part of the key for which the alert has been recorded |
KEY_VALUE3 |
For composite keys, this is the third part of the key for which the alert has been recorded |
KEY_VALUE4 |
For composite keys, this is the fourth part of the key for which the alert has been recorded |
KEY_VALUE5 |
For composite keys, this is the fifth part of the key for which the alert has been recorded |
COLLECTION_ TIMESTAMP |
The date-time when the alert condition was detected by the Management Agent |
ALERT_STATE |
A user readable description of the internal alert code that is sent from the Management Agent to identify the state of the alert condition. A alert record is transferred to the repository from the Management Agent each time the metric threshold is crossed in either direction, or if the Management Agent is restarted. The value of this column will contain one of the following strings:
If the metric's alert condition goes into a clear state, it will no longer be visible from this view. |
VIOLATION_TYPE |
A user readable description of the type of violation. Possible values are:
|
MESSAGE |
An optional message that is generated when the alert is created that provides additional information about the alert condition |
MESSAGE_NLSID |
The NLSID of the alert message |
MESSAGE_PARAMS |
Contains the URL encoded parameters separated by "&" to be used to format the alert message |
ACTION_MESSAGE |
Suggested action message in English for this alert |
ACTION_MESSAGE_NLSID |
The NLS ID of the action message |
ACTION_MESSAGE_PARAMS |
Contains the URL encoded parameters for translating action message |
TYPE_DISPLAY_NAME |
The display name of the target type |
Usage Notes
List the current alerts that are in a non-clear state for a metric, set of metrics, or for a managed target. If the user is only interested in non-clear alerts, counts or selects, using this view provide better performance than using the MGMT$ALERT_DETAILS view.
Access to this view will use an index if the query references the member target name, target type, metric name, and metric column or a subset of these columns if they are included as listed above from left to right.
The MGMT$TARGET_METRIC_COLLECTIONS view displays information about the metric collections.
Table 14-2 MGMT$TARGET_METRIC_COLLECTIONS
Column | Description |
---|---|
TARGET_NAME |
Name of the target where the metric was collected. The target name uniquely identifies a managed target within the Management Repository. The target name typically contains the name of the managed entity that was provided by the system or database administrator. |
TARGET_TYPE |
The target type defines the set of metrics that are applicable for the target |
TARGET_GUID |
Unique global identifier (GUID) for the target |
METRIC_NAME |
Name of the metric being defined |
METRIC_COLUMN |
For table metrics, the metric column contains the name of the column in the table that is being defined. If the metric that is being defined is not a table metric, the value in this column is a single space. For example, if the table describing the MGMT$TARGET_TYPE view is defined as a table metric, then Column Name, Data Type, and Description would be metric columns. |
METRIC_GUID |
Unique global identifier (GUID) for the metric. This ID can be used to associate metric information with metric data information during reporting. |
COLLECTION_NAME |
The name of the collection |
IS_ENABLED |
Indicates whether the collection is currently enabled
|
IS_REPOSITORY |
Indicates whether this is a repository-side collection. A repository-side collection has a PL/SQL evaluation procedure that is responsible for calculating the metric values. |
FREQUENCY_CODE |
The metric collection frequency type. Possible values are:
|
COLLECTION_FREQUENCY |
Frequency of the metric collection. Value displayed is dependent on the frequency code:
|
UPLOAD_POLICY |
The frequency with which the metric data is uploaded or stored |
Usage Notes
List the metric collections for a given target.
The MGMT$TARGET_METRIC_SETTINGS view displays information about the current metric setting stored for all targets in the Management Repository. This view provides information for both Management Agent-side and Management Repository-side metrics.
Table 14-3 MGMT$TARGET_METRIC_SETTINGS
Column | Description |
---|---|
TARGET_NAME |
Name of the target where the metric was collected. The target name uniquely identifies a managed target within the Management Repository. The target name typically contains the name of the managed entity that was provided by the system or database administrator. |
TARGET_TYPE |
The target type defines the set of metrics that are applicable for the target |
TARGET_GUID |
The unique global identifier (GUID) for the target |
METRIC_NAME |
Name of the metric being defined |
METRIC_COLUMN |
For table metrics, the metric column contains the name of the column in the table that is being defined. If the metric that is being defined is not a table metric, the value in this column is a single space.For example, if the table describing the MGMT$TARGET_TYPE view is defined as a table metric, then Column Name, Data Type, and Description would be metric columns. |
METRIC_GUID |
The unique global identifier for the metric. This ID can be used to associate metric information with metric data information during reporting. |
COLLECTION_NAME |
The name of the collection |
CATEGORY |
The name of the category the metricRefer to MGMT$METRIC_CATEGORIES for the list of all metric categories. |
KEY_VALUE |
The key value of the metric setting. For composite keys, this is the first part of the key.If the thresholds are not for a table metric, or the thresholds apply for all rows in the metric column, then the value in this column will contain a single space. |
KEY_VALUE2 |
For composite keys, this is the second part of the key |
KEY_VALUE3 |
For composite keys, this is the third part of the key |
KEY_VALUE4 |
For composite keys, this is the fourth part of the key |
KEY_VALUE5 |
For composite keys, this is the fifth part of the key |
KEY_OPERATOR |
Specifies whether the key_value columns have any SQL wildcards.For single key column metrics, the value is 1 if the key_value has wildcard characters, 0 otherwise.For metrics with multiple keys, a list of operators for all key columns will be stored here. For example, a metric with 3 keys (k1, k2, k3) where K1 and K2 use wildcards and K3 uses exact match, then 011 is stored in this column. |
HAS_ACTIVE_BASELINE |
The is a flag that specifies that the metric rows with this key_value has an active baseline and any user updates to thresholds or parameter values should be ignored. |
PREVENT_OVERRIDE |
The is a flag that specifies that the metric rows with this key_value has a template override flag. Once the template override flag is ON, any template application will not update the threshold or parameter values. |
WARNING_OPERATOR |
Defines the warning threshold condition to be applied
|
WARNING_THRESHOLD |
The warning threshold value |
CRITICAL_OPERATOR |
Defines the critical threshold condition to be applied
|
CRITICAL_THRESHOLD |
The critical threshold value |
OCCURRENCE_COUNT |
The number of times the test has to trigger to raise a violation |
WARNING_ACTION_TYPE |
Specifies the job type of the warning corrective action when WARNING_ACTION_TYPE is “Corrective-Action" |
WARNING_ACTION_JOB_OWNER |
Specifies the job owner of the warning corrective action when WARNING_ACTION_TYPE is “Corrective-Action" |
WARNING_ACTION_JOB_NAME |
Specifies the job name of the warning corrective action when WARNING_ACTION_TYPE is “Corrective-Action" |
CRITICAL_ACTION_TYPE |
The critical corrective action type configured. Possible values are:
|
CRITICAL_ACTION_JOB_TYPE |
Specifies the job type of the critical corrective action when WARNING_ACTION_TYPE is “Corrective-Action" |
CRITICAL_ACTION_JOB_OWNER |
Specifies the job owner of the critical corrective action when WARNING_ACTION_TYPE is “Corrective-Action" |
CRITICAL_ACTION_JOB_NAME |
Specifies the job name of the critical corrective action when WARNING_ACTION_TYPE is “Corrective-Action" |
Usage Notes
List all the metric setting for a given target.
List the metric settings for a given target and metric.
List the corrective actions assigned for a given target-metric.
The MGMT$AVAILABILITY_CURRENT view displays information about the most recent target availability information stored in the Management Repository.
Table 14-4 MGMT$AVAILABILITY_CURRENT
Column | Description |
---|---|
TARGET_NAME |
Name of the target where the metric was collected. The target name uniquely identifies a managed target within the Management Repository. The target name typically contains the name of the managed entity that was provided by the system or database administrator. |
TARGET_TYPE |
The target type defines the set of metrics that are applicable for the target |
TARGET_GUID |
The unique global identifier for the target |
START_TIMESTAMP |
The time when the target availability status change was first detected |
AVAILABILITY_STATUS |
Current target availability status. This column contains one of the following values:
|
AVAILABILITY_STATUS_CODE |
Status code corresponding to the availability status.
|
TYPE_DISPLAY_NAME |
The name of the target type as shown in the UI. |
Usage Notes
Get the current availability status of a given target.
The MGMT$AVAILABILITY_HISTORY view displays detailed historical information about changes in the availability status for a target over time.
Table 14-5 MGMT$AVAILABILITY_HISTORY
Column | Description |
---|---|
TARGET_NAME |
Name of the target where the metric was collected. The target name uniquely identifies a managed target within the Management Repository. The target name typically contains the name of the managed entity that was provided by the system or database administrator. |
TARGET_TYPE |
The target type defines the set of metrics that are applicable for the target |
TARGET_GUID |
The unique global identifier for the target |
START_TIMESTAMP |
The time when the target availability status change was first detected |
END_TIMESTAMP |
The time when the target availability status change was last detected |
AVAILABILITY_STATUS |
Target availability status. This column will contain one of the following values:
|
Usage Notes
Access to this view will use an index if the query references the member TARGET_ NAME, TARGET_TYPE and the START_TIMESTAMP.
The MGMT$ALERT_HISTORY view displays historical information for any alerts that are logged in the Management Repository.
Table 14-6 MGMT$ALERT_HISTORY
Column | Description |
---|---|
TARGET_NAME |
Name of the target where the metric was collected. The target name uniquely identifies a managed target within the Management Repository. The target name typically contains the name of the managed entity that was provided by the system or database administrator. |
TARGET_TYPE |
The target type defines the set of metrics that are applicable for the target |
TARGET_GUID |
The unique global identifier for the target |
VIOLATION_GUID |
Unique identifier for the alert |
METRIC_NAME |
Name of the metric being defined |
METRIC_COLUMN |
For table metrics, the metric column contains the name of the column in the table that is being defined. If the metric that is being defined is not a table metric, the value in this column is a single space. For example, if this table describing the MGMT$TARGET_TYPE view was being defined as a table metric, Column Name, Data Type, and Description would be metric columns. |
METRIC_LABEL |
An intuitive display name for the metric that is being defined |
COLUMN_LABEL |
For table metrics, the column label contains an intuitive display name for the metric column |
KEY_VALUE |
The key value for which the alert has been recorded. For composite keys, this is the first part of the key. |
KEY_VALUE2 |
For composite keys, this is the second part of the key for which the alert has been recorded |
KEY_VALUE3 |
For composite keys, this is the third part of the key for which the alert has been recorded |
KEY_VALUE4 |
For composite keys, this is the fourth part of the key for which the alert has been recorded |
KEY_VALUE5 |
For composite keys, this is the fifth part of the key for which the alert has been recorded |
COLLECTION_ TIMESTAMP |
The date-time when the alert condition was detected by the Management Agent |
ALERT_STATE |
A user readable description of the internal alert code that is sent from the Management Agent to identify the state of the alert condition. A alert record is transferred to the repository from the Management Agent each time the metric threshold is crossed in either direction, or if the Management Agent is restarted. The value of this column will contain one of the following strings:
If the metric's alert condition goes into a clear state, it will no longer be visible from this view. |
ALERT_DURATION |
The time, in hours, from when the alert condition was first detected until it was cleared |
MESSAGE |
An optional message that is generated when the alert is created that provides additional information about the alert condition |
MESSAGE_NLSID |
The NLSID of the alert message |
MESSAGE_PARAMS |
Contains the URL encoded parameters separated by "&" to be used to format the alert message |
ACTION_MESSAGE |
Suggested action message in English for this alert |
ACTION_MESSAGE_NLSID |
The NLS ID of the action message |
ACTION_MESSAGE_PARAMS |
Contains the URL encoded parameters for translating action message |
VIOLATION_TYPE |
An intuitive description of the type of violation. Possible values are:
|
TYPE_DISPLAY_NAME |
The display name of the target type |
The MGMT$AVAIL_ALERT_HISTORY view displays historical information for response alerts that are logged in the Management Repository.
Table 14-7 MGMT$AVAIL_ALERT_HISTORY
Column | Description |
---|---|
TARGET_NAME |
Name of the target where the metric was collected. The target name uniquely identifies a managed target within the Management Repository. The target name typically contains the name of the managed entity that was provided by the system or database administrator. |
TARGET_TYPE |
The target type defines the set of metrics that are applicable for the target |
TARGET_GUID |
The unique global identifier of the target |
VIOLATION_GUID |
The unique identifier of the violation. |
VIOLATION_LEVEL |
The priority level of the violation, such as:
|
CYCLE_GUID |
Violation GUID of the first violation in the severity life cycle. |
METRIC_NAME |
An intuitive display name for the metric that is being defined |
METRIC_COLUMN |
For table metrics, the metric column contains the name of the column in the table that is being defined. If the metric that is being defined is not a table metric, then the value in this column is a single space. |
METRIC_GUID |
The unique global identifier for the metric column |
METRIC_LABEL |
User display name of the metric |
COLUMN_LABEL |
For table metrics, the column label contains an intuitive displayname for the metric column |
COLLECTION_TIMESTAMP |
The date-time when the alert condition was detected by the Management Agent |
ALERT_STATE |
A user readable description of the internal alert code that is sent from the Management Agent to identify the state of the alert condition. A alert record is transferred to the repository from the Management Agent each time the metric threshold is crossed in either direction, or if the Management Agent is restarted. The value of this column will contain one of the following strings:
|
ALERT_DURATION |
The time, in hours, from when the alert condition was first detected until it was cleared |
MESSAGE |
An optional message that is generated when the alert is created that provides additional information about the alert condition |
MESSAGE_NLSID |
The NLSID of the alert message |
MESSAGE_PARAMS |
Contains the URL encoded parameters separated by "&" to be used to format the alert message |
ACTION_MESSAGE |
Suggested action message in English for this alert |
ACTION_MESSAGE_NLSID |
The NLS ID of the action message |
ACTION_MESSAGE_PARAMS |
Contains the URL encoded parameters for translating action message |
VIOLATION_TYPE |
An intuitive description of the type of violation. Possible values are:
|
TYPE_DISPLAY_NAME |
The display name of the target type |
The MGMT$METRIC_DETAILS view displays a rolling 7 day window of individual metric samples. These are the metric values for the most recent sample that has been loaded into the Management Repository plus any earlier samples that have not been aggregated into hourly statistics.
Table 14-8 MGMT$METRIC_DETAILS
Column | Description |
---|---|
TARGET_NAME |
Name of the target where the metric was collected. The target name uniquely identifies a managed target within the Management Repository. The target name typically contains the name of the managed entity that was provided by the system or database administrator. |
TARGET_TYPE |
The target type defines the set of metrics that are applicable for the target |
TARGET_GUID |
The unique global identifier for the target |
METRIC_NAME |
Name of the metric being defined |
METRIC_TYPE |
A DECODE of the internal numeric type of the metric that is being defined. This column will contain one of the following values:
|
METRIC_COLUMN |
For table metrics, the metric column contains the name of the column in the table that is being defined. If the metric that is being defined is not a table metric, the value in this column is a single space.For example, if this table describing the MGMT$TARGET_TYPE view was being defined as a table metric, Column Name, Data Type, and Description would be metric columns. |
METRIC_LABEL |
An intuitive display name for the metric that is being defined |
COLUMN_LABEL |
For table metrics, the column label contains an intuitive display name for the metric column |
COLLECTION_ TIMESTAMP |
The date-time when the alert condition was detected by the Management Agent |
VALUE |
Since current metric values can be a numeric or a string type, this column returns the value of the metric as a string. If the user of the view is restricting the query to numeric metric values, they can use the TO_NUMBER SQL function to return the values in numeric form. |
KEY_VALUE |
The key value for which the alert has been recorded. For composite keys, this is the first part of the key. |
KEY_VALUE2 |
For composite keys, this is the second part of the key for which the alert has been recorded |
KEY_VALUE3 |
For composite keys, this is the third part of the key for which the alert has been recorded |
KEY_VALUE4 |
For composite keys, this is the fourth part of the key for which the alert has been recorded |
KEY_VALUE5 |
For composite keys, this is the fifth part of the key for which the alert has been recorded |
Usage Notes
Show the individual values for a metric over time.
Identify time periods when abnormal samples for metric were collected.
Calculate the correlation coefficient between two or more metrics.
Provide metric values that are associated with an alert.
Queries using this view will use an index if the queries use the target name, the target type, metric name. metric column, and key value, or if they are based upon the collection_timestamp.
The MGMT$METRIC_CURRENT view displays information on the most recent metric values that have been loaded into the Management Repository.
Table 14-9 MGMT$METRIC_CURRENT
Column | Description |
---|---|
TARGET_NAME |
Name of the target where the metric was collected. The target name uniquely identifies a managed target within the Management Repository. The target name typically contains the name of the managed entity that was provided by the system or database administrator. |
TARGET_TYPE |
The target type defines the set of metrics that are applicable for the target |
TARGET_GUID |
The unique global identifier for the target |
METRIC_NAME |
Name of the metric being defined |
METRIC_TYPE |
A DECODE of the internal numeric type of the metric that is being defined. This column will contain one of the following values:
|
METRIC_COLUMN |
For table metrics, the metric column contains the name of the column in the table that is being defined. If the metric that is being defined is not a table metric, the value in this column is a single space.For example, if this table describing the MGMT$TARGET_TYPE view was being defined as a table metric, Column Name, Data Type, and Description would be metric columns. |
METRIC_LABEL |
An intuitive display name for the metric that is being defined |
COLUMN_LABEL |
For table metrics, the column label contains an intuitive display name for the metric column |
COLLECTION_ TIMESTAMP |
The date-time when the alert condition was detected by the Management Agent |
VALUE |
Since current metric values can be a numeric or a string type, this column returns the value of the metric as a string. If the user of the view is restricting the query to numeric metric values, they can use the TO_NUMBER SQL function to return the values in numeric form. |
KEY_VALUE |
The key value for which the alert has been recorded. For composite keys, this is the first part of the key. |
KEY_VALUE2 |
For composite keys, this is the second part of the key for which the alert has been recorded |
KEY_VALUE3 |
For composite keys, this is the third part of the key for which the alert has been recorded |
KEY_VALUE4 |
For composite keys, this is the fourth part of the key for which the alert has been recorded |
KEY_VALUE5 |
For composite keys, this is the fifth part of the key for which the alert has been recorded |
Usage Notes
Retrieve the most recent value for a metric that is stored in the Management Repository.
Retrieve the latest metrics for a target or metric for a specific time period.
Queries using this view will use an index if the queries use target name, the target type, metric name. metric column, and key value, or if they are based upon the collection_timestamp.
The MGMT$METRIC_HOURLY view displays metric statistics information that have been aggregated from the individual metric samples into hourly time periods. For example, if a metric is collected every 15 minutes, the 1 hour rollup would aggregate the 4 samples into a single hourly value by averaging the 4 individual samples together. The current hour of statistics may not be immediately available from this view. The timeliness of the information provided from this view is dependent on when the query against the view was executed and when the hourly rollup table was last refreshed.
Table 14-10 MGMT$METRIC_HOURLY
Column | Description |
---|---|
TARGET_NAME |
Name of the target where the metric was collected. The target name uniquely identifies a managed target within the Management Repository. The target name typically contains the name of the managed entity that was provided by the system or database administrator. |
TARGET_TYPE |
The target type defines the set of metrics that are applicable for the target |
TARGET_GUID |
The unique global identifier for the target |
METRIC_NAME |
Name of the metric being defined |
METRIC_COLUMN |
For table metrics, the metric column contains the name of the column in the table that is being defined. If the metric that is being defined is not a table metric, the value in this column is a single space.For example, if this table describing the MGMT$TARGET_TYPE view was being defined as a table metric, Column Name, Data Type, and Description would be metric columns. |
METRIC_LABEL |
An intuitive display name for the metric that is being defined |
COLUMN_LABEL |
For table metrics, the column label contains an intuitive display name for the metric column |
KEY_VALUE |
The key value for which the alert has been recorded. For composite keys, this is the first part of the key |
KEY_VALUE2 |
For composite keys, this is the second part of the key for which the alert has been recorded |
KEY_VALUE3 |
For composite keys, this is the third part of the key for which the alert has been recorded |
KEY_VALUE4 |
For composite keys, this is the fourth part of the key for which the alert has been recorded |
KEY_VALUE5 |
For composite keys, this is the fifth part of the key for which the alert has been recorded |
ROLLUP_TIMESTAMP |
The rollup timestamp identifies the start of the rollup period. For the one-hour rollups, samples that fall within the hourly boundaries from minute 00 through minute 59 inclusive will be combined. For example, samples from 12:00 AM through 12:59 AM would be combined into a single aggregated record with a rollup timestamp of "date" 12:00 AM. |
SAMPLE_COUNT |
The number of non NULL samples for the metric that were aggregated |
AVERAGE |
The average of the metric values for the samples that have been included in the rollup period |
MINIMUM |
The minimum value for the metric for the samples that have been included in the rollup period |
MAXIMUM |
The maximum value for the metric for samples that have been included in the rollup period |
STANDARD_DEVIATION |
The standard deviation for the metric values that have been included in the rollup period |
Usage Notes
This view provides the best level of granularity to show changes in a metric's value over the course of a day.
Identify hourly time periods when a metric or sets of metrics are maximized.
Understand how the variability of a metric over a one hour time period.
Identify the values of the collected metrics for a target when a particular hour has been identified as problematic.
Queries using this view will use an index if the queries use the target_name, the metric_name, or if they are based upon the rollup_timestamp.
The MGMT$METRIC_DAILY view displays metric statistics that have been aggregated from the samples collected over the previous twenty-four hour time period. The timeliness of the information provided from this view is dependent on when the query against the view was executed and when the hourly rollup table was last refreshed.
Table 14-11 MGMT$METRIC_DAILY
Column | Description |
---|---|
TARGET_NAME |
Name of the target where the metric was collected. The target name uniquely identifies a managed target within the Management Repository. The target name typically contains the name of the managed entity that was provided by the system or database administrator. |
TARGET_TYPE |
The target type defines the set of metrics that are applicable for the target |
TARGET_GUID |
The unique global identifier for the target |
METRIC_NAME |
Name of the metric being defined |
METRIC_COLUMN |
For table metrics, the metric column contains the name of the column in the table that is being defined. If the metric that is being defined is not a table metric, the value in this column is a single space.For example, if this table describing the MGMT$TARGET_TYPE view was being defined as a table metric, Column Name, Data Type, and Description would be metric columns. |
METRIC_LABEL |
An intuitive display name for the metric that is being defined |
COLUMN_LABEL |
For table metrics, the column label contains an intuitive display name for the metric column |
KEY_VALUE |
The key value for which the alert has been recorded. For composite keys, this is the first part of the key |
KEY_VALUE2 |
For composite keys, this is the second part of the key for which the alert has been recorded |
KEY_VALUE3 |
For composite keys, this is the third part of the key for which the alert has been recorded |
KEY_VALUE4 |
For composite keys, this is the fourth part of the key for which the alert has been recorded |
KEY_VALUE5 |
For composite keys, this is the fifth part of the key for which the alert has been recorded |
ROLLUP_TIMESTAMP |
The rollup timestamp identifies the start of the rollup period. For the one-hour rollups, samples that fall within the hourly boundaries from minute 00 through minute 59 inclusive will be combined. For example, samples from 12:00 AM through 12:59 AM would be combined into a single aggregated record with a rollup timestamp of "date" 12:00 AM. |
SAMPLE_COUNT |
The number of non-NULL samples for the metric that were aggregated |
AVERAGE |
The average of the metric values for the samples that have been included in the rollup period |
MINIMUM |
The minimum value for the metric for the samples that have been included in the rollup period |
MAXIMUM |
The maximum value for the metric for samples that have been included in the rollup period |
STANDARD_DEVIATION |
The standard deviation for the metric values that have been included in the rollup period |
Usage Notes
This view provides the best granularity to show changes in a metric's value over the course of a week or month.
Understand trends in metric values.
Queries using this view will use an index if the queries use the target_name, the metric_name, or if they are based upon the rollup_timestamp.