支持的查询过滤条件字段
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
如需参考过滤条件语法,请参阅查询过滤条件,并查看下文中的过滤条件示例。
alerts.list
支持的字段
过滤字段 |
alertId |
应用于根据提醒 ID 过滤提醒。
相应的值应为 string 类型。
|
type |
应用于按提醒类型过滤提醒。
对应的值应为 string 类型。Alert.type 字段说明中列出了此过滤条件的可能值。
|
source |
应用于根据提醒来源过滤提醒。
对应的值应为 string 类型。Alert.type 字段说明中列出了此过滤条件的可能值。
|
createTime |
应用于根据提醒创建时间过滤提醒。
相应值应为 string (Timestamp
format) 类型;更具体地说,应为 RFC 3339 日期时间字符串,例如 "2018-01-01T00:00:00Z"
|
startTime |
应用于按提醒开始时间过滤提醒。
相应值应为 string (Timestamp
format) 类型;更具体地说,应为 RFC 3339 日期时间字符串,例如 "2018-01-01T00:00:00Z"
|
endTime |
应用于根据提醒结束时间过滤提醒。
相应值应为 string (Timestamp
format) 类型;更具体地说,应为 RFC 3339 日期时间字符串,例如 "2018-01-01T00:00:00Z"
|
列表查询示例
- 如需查询 2018 年 4 月 5 日当天或之后创建的所有提醒,请执行以下操作:
createTime >= "2018-04-05T00:00:00Z"
- 如需查询来源为“Gmail 钓鱼式攻击”的所有提醒,请执行以下操作:
source:"Gmail phishing"
- 如需查询 2017 年开始的所有提醒,请执行以下操作:
startTime >= "2017-01-01T00:00:00Z&" AND startTime < "2018-01-01T00:00:00Z"
- 如需查询来源为“Gmail 钓鱼式攻击”的所有用户举报的钓鱼式攻击提醒,请执行以下操作:
type:"User reported phishing" source:"Gmail phishing"
alerts.feedback.list
支持的字段
过滤字段 |
alertId |
应用于根据提醒 ID 过滤提醒反馈。
相应值应为 string 类型。
当请求的 alertId 中使用“-”通配符时,可用于在一次调用中列出所选提醒的反馈。
|
feedbackId |
应用于根据反馈 ID 过滤提醒反馈。
相应值应为 string 类型。
|
反馈列表查询示例
- 如需查询 ID 为
alertId01
或 alertId02
的提醒的反馈,请执行以下操作:
alertId = alertId01 OR alertId = alertId02
- 如需查询反馈 ID 为
feedbackId01
的提醒 alertId01
的反馈,请执行以下操作:
alertId = alertId01 AND feedbackId = feedbackId01
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-03-25。
[null,null,["最后更新时间 (UTC):2025-03-25。"],[],[],null,["# Supported query filter fields\n\nSee [Query filters](/workspace/admin/alertcenter/guides/query-filters) for reference\non filter syntax, and review the filter examples below.\n\nFields supported by `alerts.list`\n---------------------------------\n\n| Filter fields ||\n|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `alertId` | Should be used to filter alerts based on alert id. Corresponding value should be of type: `string`. |\n| `type` | Should be used to filter alerts based on alert type. Corresponding value should be of type: `string`. Possible values for this filter are listed in the [`Alert.type` field description](/workspace/admin/alertcenter/reference/rest/v1beta1/alerts#alert-types). |\n| `source` | Should be used to filter alerts based on alert source. Corresponding value should be of type: `string`. Possible values for this filter are listed in the [`Alert.type` field description](/workspace/admin/alertcenter/reference/rest/v1beta1/alerts#alert-types). |\n| `createTime` | Should be used to filter alerts based on alert creation time. Corresponding value should be of type: `string (`[Timestamp](/protocol-buffers/docs/reference/google.protobuf#google.protobuf.Timestamp)` format)`; more specifically, an [RFC 3339](https://tools.ietf.org/html/rfc3339) date-time string, for example, `\"2018-01-01T00:00:00Z\"` |\n| `startTime` | Should be used to filter alerts based on alert start time. Corresponding value should be of type: `string (`[Timestamp](/protocol-buffers/docs/reference/google.protobuf#google.protobuf.Timestamp)` format)`; more specifically, an [RFC 3339](https://tools.ietf.org/html/rfc3339) date-time string, for example, `\"2018-01-01T00:00:00Z\"` |\n| `endTime` | Should be used to filter alerts based on alert end time. Corresponding value should be of type: `string (`[Timestamp](/protocol-buffers/docs/reference/google.protobuf#google.protobuf.Timestamp)` format)`; more specifically, an [RFC 3339](https://tools.ietf.org/html/rfc3339) date-time string, for example, `\"2018-01-01T00:00:00Z\"` |\n\n### List query examples\n\n- To query for all alerts created on or after April 5, 2018: \n `createTime \u003e= \"2018-04-05T00:00:00Z\"`\n- To query for all alerts from the source \"Gmail phishing\": \n `source:\"Gmail phishing\"`\n- To query for all alerts that started in 2017: \n `startTime \u003e= \"2017-01-01T00:00:00Z&\" AND startTime \u003c \"2018-01-01T00:00:00Z\"`\n- To query for all user-reported phishing alerts from the source \"Gmail phishing\": \n `type:\"User reported phishing\" source:\"Gmail phishing\"`\n\nFields supported by `alerts.feedback.list`\n------------------------------------------\n\n| Filter fields ||\n|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `alertId` | Should be used to filter alert feedback based on alert id. Corresponding value should be of type: `string`. Can be used to list feedback for selected alerts in one call when the '-' wildcard is used in request's `alertId`. |\n| `feedbackId` | Should be used to filter alert feedback based on feedback id. Corresponding value should be of type: `string`. |\n\n### Feedback list query examples\n\n- To query feedback of alerts with ids `alertId01` or `alertId02`: \n `alertId = alertId01 OR alertId = alertId02`\n- To query feedback of an alert `alertId01` with feedback id `feedbackId01`: \n `alertId = alertId01 AND feedbackId = feedbackId01`"]]