public class DescribeDBDiagEventResponse extends AbstractModel
header, skipSign| Constructor and Description |
|---|
DescribeDBDiagEventResponse() |
DescribeDBDiagEventResponse(DescribeDBDiagEventResponse source)
NOTE: Any ambiguous key set via .set("AnyKey", "value") will be a shallow copy,
and any explicit key, i.e Foo, set via .setFoo("value") will be a deep copy.
|
| Modifier and Type | Method and Description |
|---|---|
String |
getDiagItem()
Get 诊断项。
|
String |
getDiagType()
Get 诊断类型。支持值包括"高危账号","自增键耗尽","连接性检查","CPU利用率","死锁","全表扫描","高并发/压力请求","预编译语句过多","内存利用率","Metadata lock","磁盘超限","内存超限","只读锁","只读实例剔除","行锁","活跃会话","慢SQL","数据库快照","磁盘空间利用率","执行计划变化","主从切换","Table open cache命中率低","大表","事务未提交","事务导致复制延迟"等。
|
String |
getEndTime()
Get 结束时间。格式: "yyyy-MM-dd HH:mm:ss"
|
Long |
getEventId()
Get 事件 ID 。
|
String |
getExplanation()
Get 诊断事件详情,若无附加解释信息则输出为空。
|
String |
getMetric()
Get 保留字段。
|
String |
getOutline()
Get 诊断概要。
|
String |
getProblem()
Get 诊断出的问题。
|
String |
getRequestId()
Get 唯一请求 ID,由服务端生成,每次请求都会返回(若请求因其他原因未能抵达服务端,则该次请求不会获得 RequestId)。定位问题时需要提供该次请求的 RequestId。
|
Long |
getSeverity()
Get 严重程度。严重程度分为5级,按影响程度从高至低分别为:1:致命,2:严重,3:告警,4:提示,5:健康。
|
String |
getStartTime()
Get 开始时间。格式: "yyyy-MM-dd HH:mm:ss"
|
String |
getSuggestions()
Get 诊断建议,若无建议则输出为空。
|
void |
setDiagItem(String DiagItem)
Set 诊断项。
|
void |
setDiagType(String DiagType)
Set 诊断类型。支持值包括"高危账号","自增键耗尽","连接性检查","CPU利用率","死锁","全表扫描","高并发/压力请求","预编译语句过多","内存利用率","Metadata lock","磁盘超限","内存超限","只读锁","只读实例剔除","行锁","活跃会话","慢SQL","数据库快照","磁盘空间利用率","执行计划变化","主从切换","Table open cache命中率低","大表","事务未提交","事务导致复制延迟"等。
|
void |
setEndTime(String EndTime)
Set 结束时间。格式: "yyyy-MM-dd HH:mm:ss"
|
void |
setEventId(Long EventId)
Set 事件 ID 。
|
void |
setExplanation(String Explanation)
Set 诊断事件详情,若无附加解释信息则输出为空。
|
void |
setMetric(String Metric)
Set 保留字段。
|
void |
setOutline(String Outline)
Set 诊断概要。
|
void |
setProblem(String Problem)
Set 诊断出的问题。
|
void |
setRequestId(String RequestId)
Set 唯一请求 ID,由服务端生成,每次请求都会返回(若请求因其他原因未能抵达服务端,则该次请求不会获得 RequestId)。定位问题时需要提供该次请求的 RequestId。
|
void |
setSeverity(Long Severity)
Set 严重程度。严重程度分为5级,按影响程度从高至低分别为:1:致命,2:严重,3:告警,4:提示,5:健康。
|
void |
setStartTime(String StartTime)
Set 开始时间。格式: "yyyy-MM-dd HH:mm:ss"
|
void |
setSuggestions(String Suggestions)
Set 诊断建议,若无建议则输出为空。
|
void |
toMap(HashMap<String,String> map,
String prefix)
Internal implementation, normal users should not use it.
|
any, fromJsonString, getBinaryParams, GetHeader, getMultipartRequestParams, getSkipSign, isStream, set, SetHeader, setParamArrayObj, setParamArraySimple, setParamObj, setParamSimple, setSkipSign, toJsonStringpublic DescribeDBDiagEventResponse()
public DescribeDBDiagEventResponse(DescribeDBDiagEventResponse source)
public String getDiagItem()
public void setDiagItem(String DiagItem)
DiagItem - 诊断项。public String getDiagType()
public void setDiagType(String DiagType)
DiagType - 诊断类型。支持值包括"高危账号","自增键耗尽","连接性检查","CPU利用率","死锁","全表扫描","高并发/压力请求","预编译语句过多","内存利用率","Metadata lock","磁盘超限","内存超限","只读锁","只读实例剔除","行锁","活跃会话","慢SQL","数据库快照","磁盘空间利用率","执行计划变化","主从切换","Table open cache命中率低","大表","事务未提交","事务导致复制延迟"等。public Long getEventId()
public void setEventId(Long EventId)
EventId - 事件 ID 。public String getExplanation()
public void setExplanation(String Explanation)
Explanation - 诊断事件详情,若无附加解释信息则输出为空。public String getOutline()
public void setOutline(String Outline)
Outline - 诊断概要。public String getProblem()
public void setProblem(String Problem)
Problem - 诊断出的问题。public Long getSeverity()
public void setSeverity(Long Severity)
Severity - 严重程度。严重程度分为5级,按影响程度从高至低分别为:1:致命,2:严重,3:告警,4:提示,5:健康。public String getStartTime()
public void setStartTime(String StartTime)
StartTime - 开始时间。格式: "yyyy-MM-dd HH:mm:ss"public String getSuggestions()
public void setSuggestions(String Suggestions)
Suggestions - 诊断建议,若无建议则输出为空。public String getMetric()
public void setMetric(String Metric)
Metric - 保留字段。public String getEndTime()
public void setEndTime(String EndTime)
EndTime - 结束时间。格式: "yyyy-MM-dd HH:mm:ss"public String getRequestId()
public void setRequestId(String RequestId)
RequestId - 唯一请求 ID,由服务端生成,每次请求都会返回(若请求因其他原因未能抵达服务端,则该次请求不会获得 RequestId)。定位问题时需要提供该次请求的 RequestId。Copyright © 2025. All rights reserved.