Combining sub-category filters with category filters
You can combine category filters with sub-category filters, to obtain alert messages for specific thresholds you set in MC. You can also use sub-category filters to obtain information about alerts on specific resource pools in your database.
Sub-category filters
You can use the following sub-category filters with the category filters. Sub-category filters are case sensitive and must be lowercase.
Sub-Category Filter | Alerts Related to Threshold Value Set For: |
---|---|
THRESHOLD_NODE_CPU |
Node CPU |
THRESHOLD_NODE_MEMORY |
Node Memory |
THRESHOLD_NODE_DISK_USAGE |
Node Disk Usage |
THRESHOLD_NODE_DISKIO |
Node Disk I/O |
THRESHOLD_NODE_CPUIO |
Node CPU I/O Wait |
THRESHOLD_NODE_REBOOTRATE |
Node Reboot Rate |
THRESHOLD_NETIO |
Network I/O Error |
THRESHOLD_QUERY_QUEUED |
Queued Query Number |
THRESHOLD_QUERY_FAILED |
Failed Query Number |
THRESHOLD_QUERY_SPILLED |
Spilled Query Number |
THRESHOLD_QUERY_RETRIED |
Retried Query Number |
THRESHOLD_QUERY_RUNTIME |
Query Running Time |
Resource pool-specific sub-category filters
To retrieve alerts for a specific resource pool, you can use sub-category filters in combination with the following category filters:
-
thresholds
-
rp_name
If you use these sub-category filters without the RP_NAME
filter, the query retrieves alerts for all resource pools in your database.
Sub-Category Filter | Alerts Related to Threshold Value Set For: |
---|---|
THRESHOLD_RP_QUERY_MAX_TIME |
Queries reaching the maximum allowed execution time. |
THRESHOLD_RP_QUERY_RESOURCE_REJECT |
The number of queries with resource rejections. |
THRESHOLD_RP_QUERY_QUEUE_TIME |
The number of queries that ended because of queue time exceeding a limit. |
THRESHOLD_RP_QUERY_RUN_TIME |
The number of queries that ended because of run time exceeding a limit. |
THRESHOLD_RP_MEMORY |
The minimum allowed resource pool size. |
THRESHOLD_RP_MAX_MEMORY |
The maximum allowed resource pool size. |
Authentication
Requires an MC-User-Apikey in the request header.
Example request
GET |
https://<MC_NODE>:5450/webui/api/alerts?category=thresholds&subcategory= <subcategory_filter> |
Combine the thresholds category filter with a sub-category filter
This example shows how you can request alerts using cURL with the thresholds category filter and a sub-category filter. You apply the following filters:
-
THRESHOLDS
-
THRESHOLD_NODE_CPU
curl -H "MC-User-ApiKey: ValidUserKey" https://<MC_NODE>:5450/webui/api/alerts?category=thresholds&subcategory=threshold_node_cpu
Response:
[
{
"alerts":[
{
"id":11749,
"markedRead":false,
"eventTypeCode":2,
"create_time":"2015-11-05 11:04:43.997",
"updated_time":"2015-11-05 11:04:43.997",
"severity":"warning",
"status":1,
"databaseName":"mydb",
"databaseId":105,
"clusterName":"1443122180317_cluster",
"description":" Database: mydb Lower than threshold Node CPU 10 % v_mydb_node0002 ;1.03% v_mydb_node0003 ;0.9% v_mydb_node0001 ;1.36% ",
"summary":"Threshold : Node CPU < 10 %",
"internal":false,
"count":1
},
{
"id":11744,
"markedRead":false,
"eventTypeCode":2,
"create_time":"2015-11-05 10:59:46.107",
"updated_time":"2015-11-05 10:59:46.107",
"severity":"warning",
"status":1,
"databaseName":"mydb2",
"databaseId":106,
"clusterName":"1443552354071_cluster",
"description":" Database: mydb2 Lower than threshold Node CPU 10 % v_mydb2_node0002 ;0.83% v_mydb2_node0001 ;1.14% ",
"summary":"Threshold : Node CPU < 10 %",
"internal":false,
"count":1
}
],
"total_alerts":2,
"request_query":"category=thresholds&subcategory=threshold_node_cpu",
"request_time":"2015-11-05 11:05:28.116"
}
]
Request an alert on a specific resource pool
This example shows how you can request alerts using cURL on a specific resource pool. The name of the resource pool is resourcepool1
. You apply the following filters:
-
THRESHOLDS
-
RP_NAME
-
THRESHOLD_RP_QUERY_RUN_TIME
curl -H "MC-User-ApiKey: ValidUserKey" https://<MC_NODE>:5450/webui/api/alerts?category=thresholds&subcategory=threshold_rp_query_run_time&rp_name=resourcepool1
Response:
[
{
"alerts":[
{
"id":6525,
"markedRead":false,
"eventTypeCode":2,
"create_time":"2015-11-05 14:25:36.797",
"updated_time":"2015-11-05 14:25:36.797",
"severity":"warning",
"status":1,
"databaseName":"mydb",
"databaseId":106,
"clusterName":"1443552354071_cluster",
"description":" Resource Pool: resourcepool1 Threshold Name: Ended Query with Run Time Exceeding Limit Time Interval: 14:20:36 to 14:25:36 Threshold Value: 0 min(s) Actual Value: 2186 query(s) ",
"summary":"Resource Pool: resourcepool1; Threshold : Ended Query with Run Time Exceeding Limit > 0 min(s)",
"internal":false,
"count":1
},
{
"id":6517,
"markedRead":false,
"eventTypeCode":2,
"create_time":"2015-11-05 14:20:39.541",
"updated_time":"2015-11-05 14:20:39.541",
"severity":"warning",
"status":1,
"databaseName":"mydb",
"databaseId":106,
"clusterName":"1443552354071_cluster",
"description":" Resource Pool: resourcepool1 Threshold Name: Ended Query with Run Time Exceeding Limit Time Interval: 14:15:39 to 14:20:39 Threshold Value: 0 min(s) Actual Value: 2259 query(s) ",
"summary":"Resource Pool: resourcepool1; Threshold : Ended Query with Run Time Exceeding Limit > 0 min(s)",
"internal":false,
"count":1
}
],
"total_alerts":14,
"request_query":"category=thresholds&subcategory=threshold_rp_query_run_time&rp_name=resourcepool1",
"request_time":"2015-11-05 11:07:43.988"
}
]