对于 AI 代理：可在 https://www.mongodb.com/zh-cn/docs/llms.txt 获取文档索引—通过在任何 URL 路径后添加 .md 可获取所有页面的 Markdown 版本。
Docs 菜单

API 变更日志

(2.0~ea98120e205)

2026 年 7 月 14 日发布

GET /api/atlas/v2/groups/{groupId}/aiModelApiClouds/{云}/geographies/{geography}/modelGroupNames/{modelGroupName}/rateLimits
已交
  • 已添加端点
PATCH /api/atlas/v2/groups/{groupId}/aiModelApiClouds/{云}/geographies/{geography}/modelGroupNames/{modelGroupName}/rateLimits
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/aiModelApiClouds/{云}/geographies/{geography}/modelGroupNames/{modelGroupName}/rateLimits:reset
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/aiModelApiKeys
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/aiModelApiKeys
已交
  • 已添加端点
删除 /api/atlas/v2/groups/{groupId}/aiModelApiKeys/{apiKeyId}
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/aiModelApiKeys/{apiKeyId}
已交
  • 已添加端点
PATCH /api/atlas/v2/groups/{groupId}/aiModelApiKeys/{apiKeyId}
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/aiModelApiRateLimits
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/aiModelApiRateLimits:reset
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性中添加了新的“WEBHOOK_TEMPLATE_RENDER_FAILED”枚举值
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性中添加了新的“WEBHOOK_TEMPLATE_RENDER_FAILED”枚举值
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/' 中添加了新的 'WEBHOOK_TEMPLATE_RENDER_FAILED'枚举值
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性中添加了新的“WEBHOOK_TEMPLATE_RENDER_FAILED”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性中添加了新的“WEBHOOK_TEMPLATE_RENDER_FAILED”枚举值
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性中添加了新的“WEBHOOK_TEMPLATE_RENDER_FAILED”枚举值
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/' 中添加了新的 'WEBHOOK_TEMPLATE_RENDER_FAILED'枚举值
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 在“results/items/oneOf[subschema #8: Any other Alerts]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性中添加了新的“WEBHOOK_TEMPLATE_RENDER_FAILED”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 在“results/items/oneOf[subschema #8: Any other Alerts]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性中添加了新的“WEBHOOK_TEMPLATE_RENDER_FAILED”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 在“/oneOf[subschema #8: Any other Alerts]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性中添加了新的“WEBHOOK_TEMPLATE_RENDER_FAILED”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 在“/oneOf[subschema #8: Any other Alerts]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性中添加了新的“WEBHOOK_TEMPLATE_RENDER_FAILED”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 在“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性中添加了新的“WEBHOOK_TEMPLATE_RENDER_FAILED”枚举值
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 在“results/items/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #12: Group Event Types]/”响应属性中添加了新的“WEBHOOK_TEMPLATE_RENDER_FAILED”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 在“/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #12: Group Event Types]/”响应属性中添加了新的“WEBHOOK_TEMPLATE_RENDER_FAILED”枚举值
PATCH /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections/{connectionId}
已交
  • 已添加端点
GET /api/atlas/v2/orgs/{orgId}/aiModelApiClouds/{云}/geographies/{geography}/modelGroupNames/{modelGroupName}/rateLimits
已交
  • 已添加端点
GET /api/atlas/v2/orgs/{orgId}/aiModelApiKeys
已交
  • 已添加端点
GET /api/atlas/v2/orgs/{orgId}/aiModelApiKeys/{apiKeyId}
已交
  • 已添加端点
GET /api/atlas/v2/orgs/{orgId}/aiModelApiRateLimits
已交
  • 已添加端点

2026 年 7 月 08 日发布

GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs
Updated
  • 在响应中添加了可选属性“results/items/instantUserProvisioningDisabled”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
Updated
  • 在响应中添加了可选属性 'instantUserProvisioningDisabled'
PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
Updated
  • 请求属性“identityProviderId”变为可空
  • 请求属性 'postAuthRoleGrants/items/' 变为可为空
  • 在响应中添加了可选属性 'instantUserProvisioningDisabled'
  • 添加了新的可选请求属性 'instantUserProvisioningDisabled'
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders
Updated
  • 向响应添加了可选属性 'results/items/associatedOrgs/items/instantUserProvisioningDisabled, results/items/oneOf[subschema #1: SAML]/associatedOrgs/items/instantUserProvisioningDisabled, results/items/oneOf[subschema #2: OIDC WORKFORCE]/associatedOrgs/items/instantUserProvisioningDisabled, results/items/oneOf[subschema #3: OIDC WORKLOAD]/associatedOrgs/items/instantUserProvisioningDisabled'
POST /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders
Updated
  • 请求属性“/oneOf[subschema #1: OIDC WORKFORCE]/说明”变为可为空
  • 请求属性“/oneOf[subschema #2: OIDC 工作负载]/说明”变为可为 null
  • 请求属性 '说明' 变为可空
  • 向响应添加了可选属性 '/oneOf[subschema #1: OIDC WORKFORCE]/associatedOrgs/items/instantUserProvisioningDisabled, /oneOf[subschema #2: OIDC 工作负载]/associatedOrgs/items/instantUserProvisioningDisabled, associatedOrgs/items/instantUserProvisioningDisabled'
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 将可选属性 '/oneOf[subschema #1: SAML]/associatedOrgs/items/instantUserProvisioningDisabled, /oneOf[subschema #2: OIDC WORKFORCE]/associatedOrgs/items/instantUserProvisioningDisabled, /oneOf[subschema #3: OIDC 工作负载]/associatedOrgs/items/instantUserProvisioningDisabled, associatedOrgs/items/instantUserProvisioningDisabled' 添加到响应中
PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 请求属性“/oneOf[subschema #1: SAML]/说明”变为可为空
  • 请求属性“/oneOf[subschema #1: SAML]/status”变为可为 null
  • 请求属性“/oneOf[subschema #2: OIDC WORKFORCE]/说明”变为可为空
  • 请求属性“/oneOf[subschema #3: OIDC 工作负载]/说明”变为可为 null
  • 请求属性 '说明' 变为可空
  • 将可选属性 '/oneOf[subschema #1: SAML]/associatedOrgs/items/instantUserProvisioningDisabled, /oneOf[subschema #2: OIDC WORKFORCE]/associatedOrgs/items/instantUserProvisioningDisabled, /oneOf[subschema #3: OIDC 工作负载]/associatedOrgs/items/instantUserProvisioningDisabled, associatedOrgs/items/instantUserProvisioningDisabled' 添加到响应中
GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 向响应添加了可选属性 'results/items/oneOf[subschema #10: Intelligent 工作负载 管理 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #10: Intelligent 工作负载 管理 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #11: NDS 自动伸缩 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #11: NDS 自动伸缩 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #12: X509 User 身份验证 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #12: X509 User 身份验证 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #13: 副本集 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #13: 副本集 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #14: 副本集 Threshold 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #14: 副本集 Threshold 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #15: 无服务器 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #15: 无服务器 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #16: Flex 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #16: Flex 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #17: Stream Processor 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #17: Stream Processor 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #18: Stream Processor 指标 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #18: Stream Processor 指标 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #1: Any Other 警报 Configurations]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #1: Any Other 警报 Configurations]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #2: 应用 Services 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #2: 应用 Services 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #3: 应用 Services 指标 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #3: 应用 Services 指标 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #4: 计费 Threshold 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #4: 计费 Threshold 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #5: 集群 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #5: 集群 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #6: Cps 备份 Threshold 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #6: Cps 备份 Threshold 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #7: 加密密钥 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #7: 加密密钥 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #8: 托管 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #8: 托管 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #9: 托管 指标 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #9: 托管 指标 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate。
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 已将可选属性“/oneOf[subschema #10: Intelligent Workload Management Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #10: Intelligent Workload Management Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #12: X509 User Authentication Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #12: X509 User Authentication Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #13: Replica Set Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #13: Replica Set Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #14: Replica Set Threshold Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #14: Replica Set Threshold Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #15: Serverless Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #15: Serverless Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #16: Flex Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #16: Flex Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #17: Stream Processor Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #17: Stream Processor Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #18: Stream Processor Metric Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #18: Stream Processor Metric Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #1: Any Other Alert Configurations]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #1: Any Other Alert Configurations]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #2: App Services Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #2: App Services Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #3: App Services Metric Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #3: App Services Metric Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #4: Billing Threshold Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #4: Billing Threshold Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #5: Cluster Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #5: Cluster Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #7: Encryption Key Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #7: Encryption Key Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #8: Host Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #8: Host Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #9: Host Metric Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #9: Host Metric Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate”添加到响应中
  • 已添加新的可选请求属性 '/oneOf[subschema #10: Intelligent 工作负载 管理 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #10: Intelligent 工作负载 管理 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #11: NDS 自动伸缩 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #11: NDS 自动伸缩 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #12: X509 User 身份验证 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #12: X509 User 身份验证 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #13: 副本集 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #13: 副本集 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #14: 副本集 Threshold 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #14: 副本集 Threshold 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #15: 无服务器 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #15: 无服务器 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #16: Flex 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #16: Flex 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #17: Stream Processor 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #17: Stream Processor 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #18: Stream Processor 指标 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #18: Stream Processor 指标 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #1: Any Other 警报 Configurations]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #1: Any Other 警报 Configurations]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #2: 应用 Services 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #2: 应用 Services 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #3: 应用 Services 指标 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #3: 应用 Services 指标 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #4: 计费 Threshold 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #4: 计费 Threshold 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #5: 集群 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #5: 集群 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #6: Cps 备份 Threshold 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #6: Cps 备份 Threshold 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #7: 加密密钥 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #7: 加密密钥 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #8: 托管 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #8: 托管 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #9: 托管 指标 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #9: 托管 指标 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate'
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 已将可选属性“/oneOf[subschema #10: Intelligent Workload Management Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #10: Intelligent Workload Management Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #12: X509 User Authentication Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #12: X509 User Authentication Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #13: Replica Set Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #13: Replica Set Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #14: Replica Set Threshold Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #14: Replica Set Threshold Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #15: Serverless Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #15: Serverless Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #16: Flex Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #16: Flex Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #17: Stream Processor Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #17: Stream Processor Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #18: Stream Processor Metric Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #18: Stream Processor Metric Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #1: Any Other Alert Configurations]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #1: Any Other Alert Configurations]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #2: App Services Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #2: App Services Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #3: App Services Metric Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #3: App Services Metric Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #4: Billing Threshold Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #4: Billing Threshold Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #5: Cluster Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #5: Cluster Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #7: Encryption Key Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #7: Encryption Key Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #8: Host Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #8: Host Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #9: Host Metric Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #9: Host Metric Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate”添加到响应中
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 已将可选属性“/oneOf[subschema #10: Intelligent Workload Management Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #10: Intelligent Workload Management Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #12: X509 User Authentication Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #12: X509 User Authentication Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #13: Replica Set Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #13: Replica Set Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #14: Replica Set Threshold Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #14: Replica Set Threshold Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #15: Serverless Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #15: Serverless Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #16: Flex Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #16: Flex Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #17: Stream Processor Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #17: Stream Processor Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #18: Stream Processor Metric Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #18: Stream Processor Metric Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #1: Any Other Alert Configurations]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #1: Any Other Alert Configurations]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #2: App Services Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #2: App Services Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #3: App Services Metric Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #3: App Services Metric Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #4: Billing Threshold Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #4: Billing Threshold Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #5: Cluster Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #5: Cluster Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #7: Encryption Key Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #7: Encryption Key Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #8: Host Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #8: Host Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #9: Host Metric Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #9: Host Metric Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate”添加到响应中
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 已将可选属性“/oneOf[subschema #10: Intelligent Workload Management Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #10: Intelligent Workload Management Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #12: X509 User Authentication Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #12: X509 User Authentication Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #13: Replica Set Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #13: Replica Set Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #14: Replica Set Threshold Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #14: Replica Set Threshold Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #15: Serverless Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #15: Serverless Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #16: Flex Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #16: Flex Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #17: Stream Processor Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #17: Stream Processor Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #18: Stream Processor Metric Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #18: Stream Processor Metric Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #1: Any Other Alert Configurations]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #1: Any Other Alert Configurations]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #2: App Services Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #2: App Services Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #3: App Services Metric Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #3: App Services Metric Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #4: Billing Threshold Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #4: Billing Threshold Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #5: Cluster Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #5: Cluster Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #7: Encryption Key Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #7: Encryption Key Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #8: Host Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #8: Host Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、/oneOf[subschema #9: Host Metric Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、/oneOf[subschema #9: Host Metric Alert Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate”添加到响应中
  • 已添加新的可选请求属性 '/oneOf[subschema #10: Intelligent 工作负载 管理 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #10: Intelligent 工作负载 管理 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #11: NDS 自动伸缩 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #11: NDS 自动伸缩 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #12: X509 User 身份验证 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #12: X509 User 身份验证 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #13: 副本集 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #13: 副本集 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #14: 副本集 Threshold 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #14: 副本集 Threshold 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #15: 无服务器 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #15: 无服务器 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #16: Flex 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #16: Flex 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #17: Stream Processor 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #17: Stream Processor 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #18: Stream Processor 指标 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #18: Stream Processor 指标 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #1: Any Other 警报 Configurations]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #1: Any Other 警报 Configurations]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #2: 应用 Services 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #2: 应用 Services 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #3: 应用 Services 指标 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #3: 应用 Services 指标 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #4: 计费 Threshold 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #4: 计费 Threshold 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #5: 集群 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #5: 集群 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #6: Cps 备份 Threshold 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #6: Cps 备份 Threshold 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #7: 加密密钥 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #7: 加密密钥 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #8: 托管 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #8: 托管 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #9: 托管 指标 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #9: 托管 指标 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate'
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 向响应添加了可选属性 'results/items/oneOf[subschema #10: Intelligent 工作负载 管理 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #10: Intelligent 工作负载 管理 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #11: NDS 自动伸缩 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #11: NDS 自动伸缩 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #12: X509 User 身份验证 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #12: X509 User 身份验证 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #13: 副本集 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #13: 副本集 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #14: 副本集 Threshold 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #14: 副本集 Threshold 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #15: 无服务器 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #15: 无服务器 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #16: Flex 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #16: Flex 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #17: Stream Processor 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #17: Stream Processor 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #18: Stream Processor 指标 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #18: Stream Processor 指标 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #1: Any Other 警报 Configurations]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #1: Any Other 警报 Configurations]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #2: 应用 Services 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #2: 应用 Services 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #3: 应用 Services 指标 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #3: 应用 Services 指标 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #4: 计费 Threshold 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #4: 计费 Threshold 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #5: 集群 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #5: 集群 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #6: Cps 备份 Threshold 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #6: Cps 备份 Threshold 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #7: 加密密钥 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #7: 加密密钥 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #8: 托管 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #8: 托管 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate、results/items/oneOf[subschema #9: 托管 指标 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate、results/items/oneOf[subschema #9: 托管 指标 警报 Configuration]/通知/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate。
POST /api/atlas/v2/groups/{groupId}/backup/exportBuckets
Updated
  • 请求主体变为可空
POST /api/atlas/v2/groups/{groupId}/clusterConfigurations:validate
Updated
  • 在请求属性“clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize”中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 向请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • 将新的 'M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 区域复制规格]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP 实例大小]/'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'
  • 在请求属性“clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize”中添加了新的“M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2”枚举值
  • 向请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值添加到请求属性“clusterDescription/effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/electableSpecs/instanceSize”
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • 在请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 在请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/effectiveElectableSpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/effectiveReadOnlySpecs/instanceSize'
  • 向请求属性“clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize”添加了新的“M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2”枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/autoScaling/compute/max实例Size/oneOf[subschema #3: GCP 实例 Sizes]/'
  • 在请求属性“clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/autoScaling/compute/min实例Size/oneOf[subschema #3: GCP 实例 Sizes]/”中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[子模式 #3: GCP 区域复制规格]/effectiveAnalyticsSpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize'
  • 在请求属性“clusterDescription/replicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize”中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 已将新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值添加到请求属性“clusterDescription/复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/”中
  • 将新的 'M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 区域复制规格]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP 实例大小]/'
  • 在请求属性 'clusterDescription/复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/analyticsSpecs/instanceSize' 中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 中
  • 已添加新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值到请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveReadOnlySpecs/instanceSize'
  • 在请求属性“clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize”中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 向请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已添加新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值到请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M30_GEN_2”、“M40_GEN_2”、“M50_GEN_2”、“M 60_GEN_2、M80_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'枚举值添加到请求属性'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3： GCP实例大小]/'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP 实例大小]/'
  • 在请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize' 中。
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/复制/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #3: GCP 实例 Sizes]/'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M30_GEN_2”、“M40_GEN_2”、“M50_GEN_2”、“M 60_GEN_2、M80_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'枚举值添加到请求属性'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP实例大小]/'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M30_GEN_2”、“M40_GEN_2”、“M50_GEN_2”、“M 60_GEN_2、M80_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'枚举值添加到请求属性'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/analyticsSpecs/instanceSize'
  • 已将新的 'M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 已将新的‘M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2’枚举值添加到请求属性‘clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/’
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/effectiveAnalyticsSpecs/instanceSize'
  • 在请求属性 'clusterDescription/复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/effectiveElectableSpecs/instanceSize' 中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规格]/readOnlySpecs/instanceSize' 中。
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize'
  • 已将新的“S10_HIGHCPU”枚举值添加到请求属性“searchDeploymentSpec/instanceSize”
GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 在“results/items/effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize”响应属性中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 将新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值添加到“results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/”响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/analyticsAutoScaling/compute/min实例Size/oneOf[subschema #3: GCP 实例 Sizes]/' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/analyticsSpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 在“results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/”响应属性中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 响应属性。
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 响应属性
  • 在“results/items/effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/electableSpecs/instanceSize”响应属性中添加了新的“M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2”枚举值
  • 将新的 'M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[子模式 #1：Amazon Web Services 区域复制规格]/readOnlySpecs/instanceSize' 响应属性
  • 在 'results/items/effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #3: GCP 实例 Sizes]/' 响应属性中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/分析自动扩展/计算/最小实例大小/oneOf[subschema #3: GCP 实例大小]/' 响应属性。
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/analyticsSpecs/instanceSize' 响应属性
  • 在“results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/”响应属性中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[子模式 #2: Azure 区域复制规范]/autoScaling/compute/minInstanceSize/oneOf[子模式 #3: GCP 实例大小]/' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/effectiveElectableSpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/effectiveReadOnlySpecs/instanceSize' 响应属性。
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M30_GEN_2”、“M40_GEN_2”、“M50_GEN_2”、“M 60_GEN_2、M80_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R80_GEN_2'枚举值添加到 'results/items/ectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/electableSpecs/instanceSize 的响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #3: GCP 实例 Sizes]/' 响应属性
  • 在 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规格]/analyticsSpecs/instanceSize' 响应属性
  • 向 'results/items/effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/autoScaling/compute/max实例Size/oneOf[subschema #3: GCP 实例 Sizes]/' 响应属性添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性。
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规格]/effectiveElectableSpecs/instanceSize' 响应属性
  • 向 'results/items/effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/effectiveReadOnlySpecs/instanceSize' 响应属性添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性
  • 向 'results/items/replicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize' 响应属性添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性。
  • 在“results/items/复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/analyticsSpecs/instanceSize”响应属性中添加了新的“M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2”枚举值
  • 在 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/autoScaling/compute/min实例Size/oneOf[subschema #3: GCP 实例 Sizes]/' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 区域复制规格]/effectiveAnalyticsSpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/effectiveElectableSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/复制规格/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/effectiveReadOnlySpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规格]/electableSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[子模式 #1：Amazon Web Services 区域复制规格]/readOnlySpecs/instanceSize' 响应属性
  • 已添加新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值到 'results/items/复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #3: GCP 实例 Sizes]/' 属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/autoScaling/compute/max实例Size/oneOf[subschema #3: GCP 实例 Sizes]/' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 向 'results/items/复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/effectiveAnalyticsSpecs/instanceSize' 响应属性添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/effectiveElectableSpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性。
  • 在响应属性 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize' 中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #3: GCP 实例 Sizes]/' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/analyticsAutoScaling/compute/min实例Size/oneOf[subschema #3: GCP 实例 Sizes]/' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize' 响应属性
  • 向 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规格]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP 实例大小]/' 响应属性
  • 在“results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize”响应属性中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 向 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 响应属性添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 响应属性
  • 在 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'results/items/复制Specs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize' 响应属性
  • 向“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/”响应属性添加了新的“M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2”枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 区域复制规格]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP 实例大小]/' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 将新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值添加到“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/”响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性
  • 向 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize' 响应属性添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[子模式 #2: Azure 区域复制规范]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[子模式 #3: GCP 实例大小]/' 响应属性
  • 在 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 向 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/effectiveElectableSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/readOnlySpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 在 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize' 响应属性中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/max实例Size/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/effectiveElectableSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 响应属性
  • 向 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize' 响应属性
  • 在响应属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize' 响应属性中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 向 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举添加到 '复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性。
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M30_GEN_2”、“M40_GEN_2”、“M50_GEN_2”、“M 60_GEN_2、M80_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R80_GEN_2'枚举值添加到 '复制规格/items/regionConfigs/items/oneOf[subschema #2 : Azure Regional ReplicationSpecifications]/autoScaling/compute/最小实例大小/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 响应属性中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性
  • 将新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize”响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M30_GEN_2”、“M40_GEN_2”、“M50_GEN_2”、“M 60_GEN_2、M80_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R80_GEN_2'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3 ： GCP区域复制规范]/analyticsSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 响应属性中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 响应属性
  • 向 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 响应属性添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 向 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize' 响应属性中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性
  • 向请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize' 添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 在请求属性“effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #3: GCP 实例 Sizes]/”中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 在请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • 在请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 在请求属性“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize”中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 向请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值添加到请求属性“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize”中
  • 已将新的 'M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2' 枚举值添加到请求属性 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/electableSpecs/instanceSize'
  • 向请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/readOnlySpecs/instanceSize' 添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 在请求属性“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/”中添加了新的“M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2”枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/analyticsAutoScaling/compute/min实例Size/oneOf[subschema #3: GCP 实例 Sizes]/'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • 向请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'。
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/有效分析规范/实例大小'。
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • 已将新的 'M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/effectiveReadOnlySpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • 在请求属性“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/”中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • 向请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 在请求属性“effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/electableSpecs/instanceSize”中添加了新的“M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2”枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • 已将新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值添加到请求属性“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize”
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 在请求属性“复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/analyticsAutoScaling/compute/min实例Size/oneOf[subschema #3: GCP Instance Sizes]/”中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • 在请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 将新的 'M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 区域复制规格]/effectiveAnalyticsSpecs/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M30_GEN_2”、“M40_GEN_2”、“M50_GEN_2”、“M 60_GEN_2、M80_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1：AWS 区域复制规范]/有效ElectableSpecs/instanceSize'
  • 已将新的‘M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2’枚举值添加到请求属性‘replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize’
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[子模式 #2: Azure 区域复制规格]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[子模式 #3: GCP 实例大小]/'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP 实例大小]/'。
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'。
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/electableSpecs/instanceSize'
  • 已添加新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • 将新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/”
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP 实例 Sizes]/'
  • 在请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize”中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 已将新的‘M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2’枚举值添加到请求属性‘复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/autoScaling/compute/min实例Size/oneOf[subschema #3: GCP 实例 Sizes]/’
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M30_GEN_2”、“M40_GEN_2”、“M50_GEN_2”、“M 60_GEN_2、M80_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/forcedAnalyticsSpecs/instanceSize'
  • 在请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize”中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize'
  • 在请求属性“复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/readOnlySpecs/instanceSize”中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize' 中
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'providerSettings/oneOf[subschema #3: 集群的云服务提供商设置]/autoScaling/compute/maxInstanceSize' 响应属性。
  • 在“providerSettings/oneOf[subschema #3: Cloud Service Provider Settings for a Cluster]/autoScaling/compute/minInstanceSize”响应属性中添加了新的“M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2”枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'providerSettings/oneOf[subschema #3: Cloud Service Provider Settings for a Cluster]/instanceSizeName' 响应属性
  • 已将新的 'M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2' 枚举值添加到请求属性 'providerSettings/oneOf[subschema #3: 集群的云服务提供商设置]/autoScaling/compute/maxInstanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'providerSettings/oneOf[subschema #3: Cloud Service Provider Settings for a Cluster]/autoScaling/compute/minInstanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'providerSettings/oneOf[subschema #3: Cloud Service Provider Settings for a Cluster]/instanceSizeName'
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgradeToServerless
Updated
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'providerSettings/effectiveInstanceSizeName/oneOf[subschema #3: GCP 实例 Sizes]/' 响应属性
  • 在请求属性 'providerSettings/effectiveInstanceSizeName/oneOf[subschema #3: GCP Instance Sizes]/' 中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize' 响应属性
  • 向“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/”响应属性添加了新的“M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2”枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 区域复制规格]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP 实例大小]/' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 将新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值添加到“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/”响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性
  • 向 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize' 响应属性添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[子模式 #2: Azure 区域复制规范]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[子模式 #3: GCP 实例大小]/' 响应属性
  • 在 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 向 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/effectiveElectableSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/readOnlySpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 在 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize' 响应属性中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/max实例Size/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/effectiveElectableSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 响应属性
  • 向 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize' 响应属性
  • 在响应属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize' 响应属性中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 向 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举添加到 '复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性。
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M30_GEN_2”、“M40_GEN_2”、“M50_GEN_2”、“M 60_GEN_2、M80_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R80_GEN_2'枚举值添加到 '复制规格/items/regionConfigs/items/oneOf[subschema #2 : Azure Regional ReplicationSpecifications]/autoScaling/compute/最小实例大小/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 响应属性中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性
  • 将新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize”响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M30_GEN_2”、“M40_GEN_2”、“M50_GEN_2”、“M 60_GEN_2、M80_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R80_GEN_2'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3 ： GCP区域复制规范]/analyticsSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 响应属性中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 响应属性
  • 向 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 响应属性添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 向 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize' 响应属性中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize' 响应属性
  • 向“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/”响应属性添加了新的“M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2”枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 区域复制规格]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP 实例大小]/' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 将新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值添加到“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/”响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性
  • 向 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize' 响应属性添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[子模式 #2: Azure 区域复制规范]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[子模式 #3: GCP 实例大小]/' 响应属性
  • 在 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 向 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/effectiveElectableSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/readOnlySpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 在 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize' 响应属性中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/max实例Size/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/effectiveElectableSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 响应属性
  • 向 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize' 响应属性
  • 在响应属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize' 响应属性中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 向 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举添加到 '复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性。
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M30_GEN_2”、“M40_GEN_2”、“M50_GEN_2”、“M 60_GEN_2、M80_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R80_GEN_2'枚举值添加到 '复制规格/items/regionConfigs/items/oneOf[subschema #2 : Azure Regional ReplicationSpecifications]/autoScaling/compute/最小实例大小/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 响应属性中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性
  • 将新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize”响应属性
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M30_GEN_2”、“M40_GEN_2”、“M50_GEN_2”、“M 60_GEN_2、M80_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R80_GEN_2'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3 ： GCP区域复制规范]/analyticsSpecs/instanceSize' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 响应属性中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 响应属性
  • 向 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 响应属性添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 向 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize' 响应属性中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize' 响应属性
  • 向请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize' 添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 在请求属性“effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #3: GCP 实例 Sizes]/”中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 在请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • 在请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 在请求属性“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize”中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 向请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值添加到请求属性“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize”中
  • 已将新的 'M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2' 枚举值添加到请求属性 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/electableSpecs/instanceSize'
  • 向请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/readOnlySpecs/instanceSize' 添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 在请求属性“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/”中添加了新的“M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2”枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/analyticsAutoScaling/compute/min实例Size/oneOf[subschema #3: GCP 实例 Sizes]/'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • 向请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'。
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/有效分析规范/实例大小'。
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • 已将新的 'M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/effectiveReadOnlySpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • 在请求属性“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/”中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • 向请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 在请求属性“effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/electableSpecs/instanceSize”中添加了新的“M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2”枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • 已将新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值添加到请求属性“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize”
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 在请求属性“复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/analyticsAutoScaling/compute/min实例Size/oneOf[subschema #3: GCP Instance Sizes]/”中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • 在请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 将新的 'M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 区域复制规格]/effectiveAnalyticsSpecs/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M30_GEN_2”、“M40_GEN_2”、“M50_GEN_2”、“M 60_GEN_2、M80_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1：AWS 区域复制规范]/有效ElectableSpecs/instanceSize'
  • 已将新的‘M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2’枚举值添加到请求属性‘replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize’
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[子模式 #2: Azure 区域复制规格]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[子模式 #3: GCP 实例大小]/'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP 实例大小]/'。
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'。
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/electableSpecs/instanceSize'
  • 已添加新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • 将新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/”
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP 实例 Sizes]/'
  • 在请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize”中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 已将新的‘M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2’枚举值添加到请求属性‘复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/autoScaling/compute/min实例Size/oneOf[subschema #3: GCP 实例 Sizes]/’
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M30_GEN_2”、“M40_GEN_2”、“M50_GEN_2”、“M 60_GEN_2、M80_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/forcedAnalyticsSpecs/instanceSize'
  • 在请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize”中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize'
  • 在请求属性“复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/readOnlySpecs/instanceSize”中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize' 中
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports
Updated
  • 请求主体变为可空
GET /api/Atlas/v2/groups/{groupId}/集群/{clusterName}/备份/快照/{snapshotId}/数据库
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}/databases/{databaseName}
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}/databases/{databaseName}/collections
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}/databases/{databaseName}/collections/{collectionName}
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collectionRestoreJobs
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collectionRestoreJobs
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collectionRestoreJobs/{jobId}
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collectionRestoreJobs/{jobId}/collections
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collectionRestoreJobs/{jobId}/collections/{sourceNamespace}
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 向 'effectiveSpecs/items/instanceSize' 响应属性添加了新的 'S10_HIGHCPU' 枚举值
  • 在“specs/items/instanceSize”响应属性中添加了新的“S10_HIGHCPU”枚举值
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 请求属性 'defaultNodeCount' 变为可为空
  • 请求属性 'specs/items/cloudProvider' 变为可空
  • 请求属性 'specs/items/nodeCount' 变为可为空
  • 请求属性“specs/items/regionName”变为可空
  • 向 'effectiveSpecs/items/instanceSize' 响应属性添加了新的 'S10_HIGHCPU' 枚举值
  • 在“specs/items/instanceSize”响应属性中添加了新的“S10_HIGHCPU”枚举值
  • 已将新的 'S10_HIGHCPU' 枚举值添加到请求属性 'specs/items/instanceSize'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 请求属性 'defaultNodeCount' 变为可为空
  • 请求属性 'specs/items/cloudProvider' 变为可空
  • 请求属性 'specs/items/nodeCount' 变为可为空
  • 请求属性“specs/items/regionName”变为可空
  • 向 'effectiveSpecs/items/instanceSize' 响应属性添加了新的 'S10_HIGHCPU' 枚举值
  • 在“specs/items/instanceSize”响应属性中添加了新的“S10_HIGHCPU”枚举值
  • 已将新的 'S10_HIGHCPU' 枚举值添加到请求属性 'specs/items/instanceSize'
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots/{snapshotId}
Updated
  • 请求属性“clusterName”变为可为 null
GET /api/atlas/v2/groups/{groupId}/containers
Updated
  • “results/items/oneOf[subschema #1: Azure]/vnetName”响应的属性模式已从“^([-\w._()])+$ 更改为“^([-\w._()])+$ 。 _()])$'
POST /api/atlas/v2/groups/{groupId}/containers
Updated
  • 将请求属性 '/oneOf[subschema #1: AZURE]/vnetName' 的模式从 '^([-\w._()])$' 更改为 '^([-\w._()])+$'
  • '/oneOf[subschema #1: AZURE]/vnetName' 响应的属性模式已从 '^([-\w._()])$' 更改为 '^([-\w._()])+$'
GET /api/atlas/v2/groups/{groupId}/containers/all
Updated
  • “results/items/oneOf[subschema #1: Azure]/vnetName”响应的属性模式已从“^([-\w._()])+$ 更改为“^([-\w._()])+$ 。 _()])$'
GET /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • '/oneOf[subschema #1: AZURE]/vnetName' 响应的属性模式已从 '^([-\w._()])$' 更改为 '^([-\w._()])+$'
PATCH /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 将请求属性 '/oneOf[subschema #1: AZURE]/vnetName' 的模式从 '^([-\w._()])$' 更改为 '^([-\w._()])+$'
  • '/oneOf[subschema #1: AZURE]/vnetName' 响应的属性模式已从 '^([-\w._()])$' 更改为 '^([-\w._()])+$'
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 将新的 'ANALYZE' 枚举值添加到 '/items/actions/items/action' 响应属性中
POST /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 在“actions/items/操作”响应属性中添加了新的“分析”枚举值
  • 在请求属性 'actions/items/操作' 中添加了新的 '分析' 枚举值
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 在“actions/items/操作”响应属性中添加了新的“分析”枚举值
PATCH /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 在“actions/items/操作”响应属性中添加了新的“分析”枚举值
  • 在请求属性 'actions/items/操作' 中添加了新的 '分析' 枚举值
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 在“results/items/oneOf[subschema #15: Atlas 项目审核]/eventTypeName”响应属性中添加了新的“AGENT_FORCE_RESTART_REQUESTED”枚举值
  • 将新的 'CPS_RESTORE_AUTH_AUDIT' 枚举值添加到 'results/items/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #7: Disk Backup Event Types]/' 响应属性中
  • 在 'results/items/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #30: Stream Processor Event Types]/' 响应属性中添加了新的 'STREAM_PROCESSOR_STARTED' 枚举值
  • 在“results/items/oneOf[subschema #25: Stream Processor Events]/eventTypeName”响应属性中添加了新的“STREAM_PROCESSOR_STARTED”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 在 '/oneOf[subschema #15: Atlas 项目 审核]/eventTypeName' 响应属性中添加了新的 'AGENT_FORCE_RESTART_REQUESTED' 枚举值
  • 在“/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #7: Disk Backup Event Types]/”响应属性中添加了新的“CPS_RESTORE_AUTH_AUDIT”枚举值
  • 在“/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #30: Stream Processor Event Types]/”响应属性中添加了新的“STREAM_PROCESSOR_STARTED”枚举值
  • 在 '/oneOf[subschema #25: Stream Processor Events]/eventTypeName' 响应属性中添加了新的 'STREAM_PROCESSOR_STARTED' 枚举值
POST /api/atlas/v2/groups/{groupId}/flexClusters:tenantUpgrade
Updated
  • 向请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize' 添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 在请求属性“effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #3: GCP 实例 Sizes]/”中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 在请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • 在请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 在请求属性“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize”中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 向请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值添加到请求属性“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize”中
  • 已将新的 'M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2' 枚举值添加到请求属性 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/electableSpecs/instanceSize'
  • 向请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/readOnlySpecs/instanceSize' 添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 在请求属性“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/”中添加了新的“M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2”枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/analyticsAutoScaling/compute/min实例Size/oneOf[subschema #3: GCP 实例 Sizes]/'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • 向请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'。
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/有效分析规范/实例大小'。
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • 已将新的 'M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/effectiveReadOnlySpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • 在请求属性“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/”中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • 向请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 在请求属性“effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/electableSpecs/instanceSize”中添加了新的“M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2”枚举值
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • 已将新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值添加到请求属性“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize”
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 在请求属性“复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/analyticsAutoScaling/compute/min实例Size/oneOf[subschema #3: GCP Instance Sizes]/”中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • 在请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 中添加了新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 将新的 'M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 区域复制规格]/effectiveAnalyticsSpecs/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M30_GEN_2”、“M40_GEN_2”、“M50_GEN_2”、“M 60_GEN_2、M80_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1：AWS 区域复制规范]/有效ElectableSpecs/instanceSize'
  • 已将新的‘M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2’枚举值添加到请求属性‘replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize’
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[子模式 #2: Azure 区域复制规格]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[子模式 #3: GCP 实例大小]/'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP 实例大小]/'。
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'。
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/electableSpecs/instanceSize'
  • 已添加新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • 将新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/”
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP 实例 Sizes]/'
  • 在请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize”中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • 已将新的‘M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2’枚举值添加到请求属性‘复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/autoScaling/compute/min实例Size/oneOf[subschema #3: GCP 实例 Sizes]/’
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M30_GEN_2”、“M40_GEN_2”、“M50_GEN_2”、“M 60_GEN_2、M80_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/forcedAnalyticsSpecs/instanceSize'
  • 在请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize”中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize'
  • 在请求属性“复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/readOnlySpecs/instanceSize”中添加了新的“M140_GEN_2、M200_GEN_2、M30_GEN_2、M40_GEN_2、M50_GEN_2、M60_GEN_2、M80_GEN_2、R200_GEN_2、R300_GEN_2、R400_GEN_2、R40_GEN_2、R50_GEN_2、R60_GEN_2、R80_GEN_2”枚举值
  • 将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize' 中
GET /api/atlas/v2/groups/{groupId}/integrations
Updated
  • 将可选属性 'results/items/oneOf[subschema #7: WEBHOOK]/bodyTemplate, results/items/oneOf[subschema #7: WEBHOOK]/headersTemplate' 添加到响应
GET /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 将可选属性 '/oneOf[subschema #7: WEBHOOK]/bodyTemplate, /oneOf[subschema #7: WEBHOOK]/headersTemplate' 添加到响应中
POST /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 将可选属性 'results/items/oneOf[subschema #7: WEBHOOK]/bodyTemplate, results/items/oneOf[subschema #7: WEBHOOK]/headersTemplate' 添加到响应
  • 已添加新的可选请求属性 '/oneOf[subschema #7: WEBHOOK]/bodyTemplate, /oneOf[subschema #7: WEBHOOK]/headersTemplate'
PUT /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 将可选属性 'results/items/oneOf[subschema #7: WEBHOOK]/bodyTemplate, results/items/oneOf[subschema #7: WEBHOOK]/headersTemplate' 添加到响应
  • 已添加新的可选请求属性 '/oneOf[subschema #7: WEBHOOK]/bodyTemplate, /oneOf[subschema #7: WEBHOOK]/headersTemplate'
POST /api/atlas/v2/groups/{groupId}/liveMigrations
Updated
  • 请求属性 'destination/privateLinkId' 变为可空
  • 请求属性 '分片' 变为可空
  • 请求属性 'source/caCertificatePath' 变为可为空
  • 请求属性 'source/password' 变为可空
  • 请求属性“source/username”变为可为空
POST /api/atlas/v2/groups/{groupId}/liveMigrations/validate
Updated
  • 请求属性 'destination/privateLinkId' 变为可空
  • 请求属性 '分片' 变为可空
  • 请求属性 'source/caCertificatePath' 变为可为空
  • 请求属性 'source/password' 变为可空
  • 请求属性“source/username”变为可为空
GET /api/atlas/v2/groups/{groupId}/mongoDBVersions
Updated
  • 已将新的‘M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2’枚举值添加到‘results/items/instanceSize/oneOf[subschema #3: GCP Instance Sizes]/’ 响应属性
GET /api/atlas/v2/groups/{groupId}/peers
Updated
  • “results/items/oneOf[subschema #2: Azure]/vnetName”响应的属性模式已从“^([-\w._()])+$ 更改为“^([-\w._()])+$ 。 _()])$'
POST /api/atlas/v2/groups/{groupId}/peers
Updated
  • 将请求属性 '/oneOf[subschema #2: AZURE]/vnetName' 的模式从 '^([-\w._()])$' 更改为 '^([-\w._()])+$'
  • '/oneOf[subschema #2: AZURE]/vnetName' 响应的属性模式已从 '^([-\w._()])$' 更改为 '^([-\w._()])+$'
GET /api/atlas/v2/groups/{groupId}/peers/{peerId}
Updated
  • '/oneOf[subschema #2: AZURE]/vnetName' 响应的属性模式已从 '^([-\w._()])$' 更改为 '^([-\w._()])+$'
PATCH /api/atlas/v2/groups/{groupId}/peers/{peerId}
Updated
  • 将请求属性 '/oneOf[subschema #2: AZURE]/vnetName' 的模式从 '^([-\w._()])$' 更改为 '^([-\w._()])+$'
  • '/oneOf[subschema #2: AZURE]/vnetName' 响应的属性模式已从 '^([-\w._()])$' 更改为 '^([-\w._()])+$'
GET /api/atlas/v2/groups/{groupId}/serverless
Updated
  • 已添加新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值到 'results/items/providerSettings/effectiveInstanceSizeName/oneOf[subschema #3: GCP 实例大小]/' 响应属性
GET /api/atlas/v2/groups/{groupId}/serverless/{name}
Updated
  • 已将新的 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 枚举值添加到 'providerSettings/effectiveInstanceSizeName/oneOf[subschema #3: GCP 实例 Sizes]/' 响应属性
GET /api/atlas/v2/groups/{groupId}/serviceAccounts
Updated
  • 添加了新的可选“查询”请求参数“includeSystemManaged”
PATCH /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
Updated
  • 请求属性 '说明' 变为可空
  • 请求属性“名称”变为可为 null
POST /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/accessList
Updated
  • 请求属性 '/items/cidrBlock' 变为可为空
  • 请求属性 '/items/ipAddress' 变为可为空
  • 请求属性 '/items/lastUsedAddress' 变为可为空
  • 请求属性“/items/lastUsedAt”变为可为 null
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 请求属性“connections/items/clusterGroupId”变为可为空
  • 请求属性 'connections/items/dbRoleToExecute' 变为可为空
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 请求属性“processorStatus/mode”变为可为 null
  • 请求属性 'processorStatus/region' 变为可空
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 请求属性 '/clusterGroupId' 变为可为空
  • 请求属性 '/dbRoleToExecute' 变为可为空
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 请求属性 '/clusterGroupId' 变为可为空
  • 请求属性 '/dbRoleToExecute' 变为可为空
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}/failoverConnections
Updated
  • 请求属性 '/clusterGroupId' 变为可为空
  • 请求属性 '/dbRoleToExecute' 变为可为空
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}/failoverConnections/{failoverConnectionId}
Updated
  • 请求属性 '/clusterGroupId' 变为可为空
  • 请求属性 '/dbRoleToExecute' 变为可为空
POST /api/atlas/v2/orgs
Updated
  • 请求属性 'apiKey/roles/items/' 变为可为空
  • 请求属性 'serviceAccount' 变为可为空
POST /api/atlas/v2/orgs/{orgId}/apiKeys
Updated
  • 请求属性 'roles/items/' 变为可为空。
PATCH /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}
Updated
  • 请求属性 'roles/items/' 变为可为空。
POST /api/atlas/v2/orgs/{orgId}/billing/costExplorer/usage
Updated
  • 已将新的 'AI 模型 API' 枚举值添加到请求属性 'services/items/'
  • 已删除请求属性 'services/items/' 的枚举值 'AI 模型'
GET /api/atlas/v2/orgs/{orgId}/delegationSettings
已交
  • 已添加端点
PATCH /api/atlas/v2/组织/{orgId}/委托设置
已交
  • 已添加端点
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 将新的 'ATLAS_MAINTENANCE_FLEET_ACTIVE_WAVE_CLOSED_BY_ADMIN' 枚举值添加到 'results/items/oneOf[subschema #7: Atlas 组织 Atlas 审核]/eventTypeName' 响应属性中
  • 在 'results/items/oneOf[subschema #8: Organization Events]/eventTypeName' 响应属性中添加了新的 'OPERATIONS_CONTACT_MODIFIED' 枚举值
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 已添加新的 'ATLAS_MAINTENANCE_FLEET_ACTIVE_WAVE_CLOSED_BY_ADMIN' 枚举值到 '/oneOf[subschema #7: Atlas 组织 Atlas 审核]/eventTypeName' 响应属性
  • 已将新的 'OPERATIONS_CONTACT_MODIFIED' 枚举值添加到 '/oneOf[subschema #8: 组织 事件]/eventTypeName' 响应属性
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}/lineItems:search
Updated
  • 在请求属性“filters/skuServices/items/”中添加了新的“AI Model APIs”枚举值
  • 删除了请求属性 'filters/skuServices/items/' 的枚举值 'AI Models'
POST /api/atlas/v2/orgs/{orgId}/resourcePolicies
Updated
  • 请求属性 '说明' 变为可空
PATCH /api/atlas/v2/orgs/{orgId}/resourcePolicies/{resourcePolicyId}
Updated
  • 请求属性 '说明' 变为可空
  • 请求属性“名称”变为可为 null
POST /api/atlas/v2/orgs/{orgId}/resourcePolicies:validate
Updated
  • 请求属性 '说明' 变为可空
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts
Updated
  • 添加了新的可选“查询”请求参数“includeSystemManaged”
POST /api/atlas/v2/orgs/{orgId}/serviceAccounts
Updated
  • 请求主体变为可空
PATCH /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}
Updated
  • 请求属性 '说明' 变为可空
  • 请求属性“名称”变为可为 null
POST /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/accessList
Updated
  • 请求属性 '/items/cidrBlock' 变为可为空
  • 请求属性 '/items/ipAddress' 变为可为空
  • 请求属性 '/items/lastUsedAddress' 变为可为空
  • 请求属性“/items/lastUsedAt”变为可为 null
GET /api/atlas/v2/orgs/{orgId}/settings
Updated
  • 已将可选属性 'operationsContact' 添加到响应
PATCH /api/atlas/v2/orgs/{orgId}/settings
Updated
  • 已将可选属性 'operationsContact' 添加到响应
  • 添加了新的可选请求属性 'operationsContact'

2026 年 6 月 25 日发布

GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 将“subschema #7: OAuth Atlas 审核类型”添加到响应的“results/items/oneOf[subschema #1: 任何其他事件]/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 将“subschema #7: OAuth Atlas 审核类型”添加到响应的“/oneOf[subschema #1: 任何其他事件]/eventTypeName”响应属性“oneOf”列表中

2026 年 6 月 22 日发布

GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 已将新的 'SEOUL_KOR' 枚举值添加到 'results/items/dataProcessRegion/region/' 响应属性
  • 在响应中添加了可选属性“results/items/failoverRegions”
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在 'dataProcessRegion/区域/' 响应属性中添加了新的 'SEOUL_KOR' 枚举值
  • 已将新的 'SEOUL_KOR' 枚举值添加到请求属性 'dataProcessRegion/区域/'
  • 在响应中添加了可选属性 'failoverRegions'
  • 添加了新的可选请求属性 'failoverRegions'
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在 'dataProcessRegion/区域/' 响应属性中添加了新的 'SEOUL_KOR' 枚举值
  • 在响应中添加了可选属性 'failoverRegions'
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在 'dataProcessRegion/区域/' 响应属性中添加了新的 'SEOUL_KOR' 枚举值
  • 已将新的 'SEOUL_KOR' 枚举值添加到请求属性 '区域/'
  • 在响应中添加了可选属性 'failoverRegions'
  • 添加了新的可选请求属性 'failoverRegions'
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}/failoverConnections/{failoverConnectionId}
已交
  • 已添加端点
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}/failoverConnections/{failoverConnectionId}
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor
Updated
  • 在响应中添加了可选属性“failoverEnabled”
  • 添加了新的可选请求属性 'failoverEnabled'
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}
Updated
  • 在响应中添加了可选属性“eligibleForFailover、failoverEnabled”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}
Updated
  • 在响应中添加了可选属性“eligibleForFailover、failoverEnabled”
  • 添加了新的可选请求属性 'failoverEnabled'
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processors
Updated
  • 在响应中添加了可选属性“results/items/eligibleForFailover、results/items/failoverEnabled”
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
Updated
  • 在 'dataProcessRegion/区域/' 响应属性中添加了新的 'SEOUL_KOR' 枚举值
  • 在响应中添加了可选属性 'failoverRegions'

2026 年 6 月 17 日发布

GET /api/atlas/v2/groups/{groupId}/ 备份/{cloudProvider}/privateEndpoints
Updated
  • 在响应中添加了可选属性 'results/items/vpcRegionName'
帖子 /api/atlas/v2/groups/{groupId}/备份/{cloudProvider}/privateEndpoints
Updated
  • 在响应中添加了可选属性 'vpcRegionName'
  • 添加了新的可选请求属性 'vpcRegionName'
GET /api/atlas/v2/groups/{groupId}/ 备份/{cloudProvider}/privateEndpoints/{endpointId}
Updated
  • 在响应中添加了可选属性 'vpcRegionName'
POST /api/atlas/v2/groups/{groupId}/clusterConfigurations:validate
Updated
  • 已将新的 'ENHANCED_FULLY_WARMED' 枚举值添加到请求属性 'clusterDescription/diskWarmingMode'
GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 将新的 'ENHANCED_FULLY_WARMED' 枚举值添加到 'results/items/diskWarmingMode' 响应属性
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 已将新的 'ENHANCED_FULLY_WARMED' 枚举值添加到 'diskWarmingMode' 响应属性
  • 将新的 'ENHANCED_FULLY_WARMED' 枚举值添加到请求属性 'diskWarmingMode'
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 已将新的 'ENHANCED_FULLY_WARMED' 枚举值添加到 'diskWarmingMode' 响应属性
  • 将新的 'ENHANCED_FULLY_WARMED' 枚举值添加到请求属性 'diskWarmingMode'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 已将新的 'ENHANCED_FULLY_WARMED' 枚举值添加到 'diskWarmingMode' 响应属性
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 已将新的 'ENHANCED_FULLY_WARMED' 枚举值添加到 'diskWarmingMode' 响应属性
  • 将新的 'ENHANCED_FULLY_WARMED' 枚举值添加到请求属性 'diskWarmingMode'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 在响应中添加了可选属性“effectiveSpecs”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 在响应中添加了可选属性“effectiveSpecs”
  • 添加了新的可选请求属性 'defaultNodeCount, specs/items/cloudProvider, specs/items/regionName'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 在响应中添加了可选属性“effectiveSpecs”
  • 添加了新的可选请求属性 'defaultNodeCount, specs/items/cloudProvider, specs/items/regionName'
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 将新的 'CREATE_SEARCH_INDEX, DROP_SEARCH_INDEX, LIST_SEARCH_INDEXES, UPDATE_SEARCH_INDEX' 枚举值添加到 '/items/actions/items/action' 响应属性中
POST /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 将新的 'CREATE_SEARCH_INDEX、DROP_SEARCH_INDEX、LIST_SEARCH_INDEXES、UPDATE_SEARCH_INDEX' 枚举值添加到 'actions/items/action' 响应属性中
  • 在请求属性“actions/items/操作”中添加了新的“CREATE_SEARCH_INDEX、DROP_SEARCH_INDEX、LIST_SEARCH_INDEXES、UPDATE_SEARCH_INDEX”枚举值
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 将新的 'CREATE_SEARCH_INDEX、DROP_SEARCH_INDEX、LIST_SEARCH_INDEXES、UPDATE_SEARCH_INDEX' 枚举值添加到 'actions/items/action' 响应属性中
PATCH /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 将新的 'CREATE_SEARCH_INDEX、DROP_SEARCH_INDEX、LIST_SEARCH_INDEXES、UPDATE_SEARCH_INDEX' 枚举值添加到 'actions/items/action' 响应属性中
  • 在请求属性“actions/items/操作”中添加了新的“CREATE_SEARCH_INDEX、DROP_SEARCH_INDEX、LIST_SEARCH_INDEXES、UPDATE_SEARCH_INDEX”枚举值
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将“subschema #39: AI Models API 事件类型”添加到响应的“results/items/oneOf[subschema #1: Any Other Events]/eventTypeName”响应属性“oneOf”列表中
  • 从响应的 'results/items/oneOf[subschema #1: Any Other 事件]/eventTypeName' 响应属性 'oneOf' 列表中删除 'subschema #39: AI Models 事件类型'
  • 在“results/items/oneOf[subschema #15: Atlas 项目 Atlas 审核]/eventTypeName”响应属性中添加了新的“CLUSTER_MONGODB_VERSION_UPDATED、PROJECT_ENABLE_DATA_VALIDATION_UPDATED”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 将“subschema #39: AI Models APIs 事件 Types”添加到响应的“/oneOf[subschema #1: Any Other 事件]/eventTypeName”响应属性“oneOf”列表中
  • 已从响应属性“/oneOf[subschema #1: 任何其他事件]/eventTypeName”的“oneOf”列表中移除“subschema #39: AI 模型事件类型”
  • 在“/oneOf[subschema #15: Atlas 项目审核]/eventTypeName”响应属性中添加了新的“CLUSTER_MONGODB_VERSION_UPDATED、PROJECT_ENABLE_DATA_VALIDATION_UPDATED”枚举值
POST /api/atlas/v2/groups/{groupId}/flexClusters:tenantUpgrade
Updated
  • 将新的 'ENHANCED_FULLY_WARMED' 枚举值添加到请求属性 'diskWarmingMode'
GET /api/atlas/v2/groups/{groupId}/settings
Updated
  • 在响应中添加了可选属性 'isDataValidationEnabled'
PATCH /api/atlas/v2/groups/{groupId}/settings
Updated
  • 在响应中添加了可选属性 'isDataValidationEnabled'
  • 添加了新的可选请求属性 'isDataValidationEnabled'
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 添加了新的可选请求属性“processorStatus”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}/failoverConnections
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}/failoverConnections
已交
  • 已添加端点
DELETE /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}/failoverConnections/{failoverConnectionId}
已交
  • 已添加端点
POST / API/ Atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}:startWith
Updated
  • 添加了新的可选请求属性“故障转移”
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 将“subschema #6: AI Models API 事件类型”添加到响应的“results/items/oneOf[subschema #1: Any Other Events]/eventTypeName”响应属性“oneOf”列表中
  • 从响应的 'results/items/oneOf[subschema #1: Any Other 事件]/eventTypeName' 响应属性 'oneOf' 列表中删除 'subschema #6: AI Models 事件类型'
  • 在“results/items/oneOf[subschema #8: 组织事件]/eventTypeName”响应属性中添加了新的“ORG_DELEGATION_SETTINGS_UPDATED”枚举值
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 将“subschema #6: AI Models APIs 事件 Types”添加到响应的“/oneOf[subschema #1: Any Other 事件]/eventTypeName”响应属性“oneOf”列表中
  • 已从响应属性“/oneOf[subschema #1: 任何其他事件]/eventTypeName”的“oneOf”列表中移除“subschema #6: AI 模型事件类型”
  • 已将新的“ORG_DELEGATION_SETTINGS_UPDATED”枚举值添加到响应属性“/oneOf[subschema #8: 组织事件]/eventTypeName”中
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}/lineItems:search
Updated
  • 在响应中添加了可选属性“results/items/additionalData”

2026 年 6 月 02 日发布

POST /api/atlas/v2/groups/{groupId}/clusterConfigurations:validate
Updated
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 在请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'中添加了新的 'HIGH_PERFORMANCE' 枚举值
  • 在请求属性'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'中添加了新的 'HIGH_PERFORMANCE' 枚举值
  • 在请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType'中添加了新的 'HIGH_PERFORMANCE' 枚举值。
  • 在请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 中添加了新的 'HIGH_PERFORMANCE' 枚举值。
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 在请求属性'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'中添加了新的 'HIGH_PERFORMANCE' 枚举值。
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 中。
  • 在请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'中添加了新的 'HIGH_PERFORMANCE' 枚举值
  • 在请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'中添加了新的 'HIGH_PERFORMANCE' 枚举值
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional 复制 Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/ebsVolumeType'
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType'
  • 已将新的 “HIGH_PERFORMANCE” 枚举值添加到请求属性 “clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规格]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的“HIGH_PERFORMANCE”枚举值添加到请求属性“clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”。
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 在请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'中添加了新的 'HIGH_PERFORMANCE' 枚举值
  • 在请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'中添加了新的 'HIGH_PERFORMANCE' 枚举值
  • 在请求属性“clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”中添加了新的“HIGH_PERFORMANCE”枚举值。
  • 在请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'中添加了新的 'HIGH_PERFORMANCE' 枚举值
  • 在请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'中添加了新的 'HIGH_PERFORMANCE' 枚举值
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 在请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'中添加了新的 'HIGH_PERFORMANCE' 枚举值
  • 已将新的“HIGH_PERFORMANCE”枚举值添加到请求属性“clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP 区域复制规范]/analyticsSpecs/oneOf[subschema #1： Amazon Web Services 集群硬件设置]/ebsVolumeType”
  • 在请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'中添加了新的 'HIGH_PERFORMANCE' 枚举值
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType'
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规格]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[子模式 #4: 租户区域复制规格]/electableSpecs/oneOf[子模式 #1: Amazon Web Services 集群硬件设置]/ebsVolumeType'。
GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType' 响应属性
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS Cluster 硬件 Settings]/ebsVolumeType' 响应属性
  • 在 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性中添加了新的 'HIGH_PERFORMANCE' 枚举值
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性。
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE'枚举值添加到 'results/items/effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS Cluster 硬件 Settings]/ebsVolumeType' 响应属性
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 在 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性中添加了新的 'HIGH_PERFORMANCE' 枚举值
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规格]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/复制规范/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/复制规范/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 在 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性中添加了新的 'HIGH_PERFORMANCE' 枚举值
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/ebsVolumeType' 响应属性
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/复制规范/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性中
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 在 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性中添加了新的 'HIGH_PERFORMANCE' 枚举值
  • 在 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性中添加了新的 'HIGH_PERFORMANCE' 枚举值
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/electableSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType' 响应属性中。
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 在'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规格]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'响应属性中添加了新的 'HIGH_PERFORMANCE' 枚举值。
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType”响应属性
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性
  • 在 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性中添加了新的 'HIGH_PERFORMANCE' 枚举值
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规格]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的“HIGH_PERFORMANCE”枚举值添加到“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 区域复制规格]/electableSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType' 响应属性。
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的“HIGH_PERFORMANCE”枚举值添加到“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure 区域复制规范]/analyticsSpecs/oneOf[subschema #1： Amazon Web Services 集群硬件设置]/ebsVolumeType”响应属性
  • 已将新的“HIGH_PERFORMANCE”枚举值添加到“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1： AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/readOnlySpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType' 响应属性
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性中
  • 已将新的“HIGH_PERFORMANCE”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性。
  • 已将新的“HIGH_PERFORMANCE”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性。
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 '复制规格/items/regionConfigs/items/oneOf[subschema #1: AWS 区域 复制规格]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性中
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性中
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性中
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType' 响应属性。
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType”响应属性
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性中
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性。
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType' 响应属性
  • 在响应属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规格]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'中添加了新的 'HIGH_PERFORMANCE' 枚举值。
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性中
  • 在请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 中添加了新的 'HIGH_PERFORMANCE' 枚举值。
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 将新的“HIGH_PERFORMANCE”枚举值添加到请求属性“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”中
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/ebsVolumeType'
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE'枚举值添加到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings] /ebsVolumeType'
  • 在请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 中添加了新的 'HIGH_PERFORMANCE' 枚举值
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/electableSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType'。
  • 在请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType' 中添加了新的 'HIGH_PERFORMANCE' 枚举值。
  • 将新的“HIGH_PERFORMANCE”枚举值添加到请求属性“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”
  • 将新的“HIGH_PERFORMANCE”枚举值添加到请求属性“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”中
  • 将新的“HIGH_PERFORMANCE”枚举值添加到请求属性“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”中
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[子规范 #3: GCP 区域复制规范]/effectiveReadOnlySpecs/oneOf[子规范 #1: Amazon Web Services 集群硬件设置]/ebsVolumeType'
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规格]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 在请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'中添加了新的 'HIGH_PERFORMANCE' 枚举值
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 在请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'中添加了新的 'HIGH_PERFORMANCE' 枚举值。
  • 将新的“HIGH_PERFORMANCE”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”中
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的“HIGH_PERFORMANCE”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure 区域复制规范]/readOnlySpecs/oneOf[subschema #1： Amazon Web Services 集群硬件设置]/ebsVolumeType”
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[子规范 #3: GCP 区域复制规范]/effectiveReadOnlySpecs/oneOf[子规范 #1: Amazon Web Services 集群硬件设置]/ebsVolumeType'
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 在请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional ReplicationSpecifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings] 中添加了新的 'HIGH_PERFORMANCE'枚举值/ebsVolumeType'
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 在 'providerSettings/oneOf[subschema #1: 集群的云服务提供商设置]/volumeType' 响应属性中添加了新的 'HIGH_PERFORMANCE' 枚举值。
  • 在请求属性 'providerSettings/oneOf[subschema #1: Cloud Service Provider Settings for a Cluster]/volumeType' 中添加了新的 'HIGH_PERFORMANCE' 枚举值
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType”响应属性
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性
  • 在 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性中添加了新的 'HIGH_PERFORMANCE' 枚举值
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规格]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的“HIGH_PERFORMANCE”枚举值添加到“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 区域复制规格]/electableSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType' 响应属性。
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的“HIGH_PERFORMANCE”枚举值添加到“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure 区域复制规范]/analyticsSpecs/oneOf[subschema #1： Amazon Web Services 集群硬件设置]/ebsVolumeType”响应属性
  • 已将新的“HIGH_PERFORMANCE”枚举值添加到“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1： AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/readOnlySpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType' 响应属性
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性中
  • 已将新的“HIGH_PERFORMANCE”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性。
  • 已将新的“HIGH_PERFORMANCE”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性。
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 '复制规格/items/regionConfigs/items/oneOf[subschema #1: AWS 区域 复制规格]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性中
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性中
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性中
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType' 响应属性。
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType”响应属性
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性中
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性。
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType' 响应属性
  • 在响应属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规格]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'中添加了新的 'HIGH_PERFORMANCE' 枚举值。
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性中
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType”响应属性
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性
  • 在 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性中添加了新的 'HIGH_PERFORMANCE' 枚举值
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规格]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的“HIGH_PERFORMANCE”枚举值添加到“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 区域复制规格]/electableSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType' 响应属性。
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的“HIGH_PERFORMANCE”枚举值添加到“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure 区域复制规范]/analyticsSpecs/oneOf[subschema #1： Amazon Web Services 集群硬件设置]/ebsVolumeType”响应属性
  • 已将新的“HIGH_PERFORMANCE”枚举值添加到“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1： AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/readOnlySpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType' 响应属性
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性中
  • 已将新的“HIGH_PERFORMANCE”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性。
  • 已将新的“HIGH_PERFORMANCE”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性。
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 '复制规格/items/regionConfigs/items/oneOf[subschema #1: AWS 区域 复制规格]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性中
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性中
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性中
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType' 响应属性。
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType”响应属性
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性中
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性。
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType' 响应属性
  • 在响应属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规格]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'中添加了新的 'HIGH_PERFORMANCE' 枚举值。
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 响应属性
  • 将新的“HIGH_PERFORMANCE”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”响应属性中
  • 在请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 中添加了新的 'HIGH_PERFORMANCE' 枚举值。
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 将新的“HIGH_PERFORMANCE”枚举值添加到请求属性“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”中
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/ebsVolumeType'
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE'枚举值添加到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings] /ebsVolumeType'
  • 在请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 中添加了新的 'HIGH_PERFORMANCE' 枚举值
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/electableSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType'。
  • 在请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType' 中添加了新的 'HIGH_PERFORMANCE' 枚举值。
  • 将新的“HIGH_PERFORMANCE”枚举值添加到请求属性“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”
  • 将新的“HIGH_PERFORMANCE”枚举值添加到请求属性“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”中
  • 将新的“HIGH_PERFORMANCE”枚举值添加到请求属性“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”中
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[子规范 #3: GCP 区域复制规范]/effectiveReadOnlySpecs/oneOf[子规范 #1: Amazon Web Services 集群硬件设置]/ebsVolumeType'
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规格]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 在请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'中添加了新的 'HIGH_PERFORMANCE' 枚举值
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 在请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'中添加了新的 'HIGH_PERFORMANCE' 枚举值。
  • 将新的“HIGH_PERFORMANCE”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”中
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的“HIGH_PERFORMANCE”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure 区域复制规范]/readOnlySpecs/oneOf[subschema #1： Amazon Web Services 集群硬件设置]/ebsVolumeType”
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[子规范 #3: GCP 区域复制规范]/effectiveReadOnlySpecs/oneOf[子规范 #1: Amazon Web Services 集群硬件设置]/ebsVolumeType'
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 在请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional ReplicationSpecifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings] 中添加了新的 'HIGH_PERFORMANCE'枚举值/ebsVolumeType'
POST /api/atlas/v2/groups/{groupId}/flexClusters:tenantUpgrade
Updated
  • 在请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 中添加了新的 'HIGH_PERFORMANCE' 枚举值。
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 将新的“HIGH_PERFORMANCE”枚举值添加到请求属性“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”中
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/ebsVolumeType'
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE'枚举值添加到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings] /ebsVolumeType'
  • 在请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType' 中添加了新的 'HIGH_PERFORMANCE' 枚举值
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/electableSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType'。
  • 在请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType' 中添加了新的 'HIGH_PERFORMANCE' 枚举值。
  • 将新的“HIGH_PERFORMANCE”枚举值添加到请求属性“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”
  • 将新的“HIGH_PERFORMANCE”枚举值添加到请求属性“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”中
  • 将新的“HIGH_PERFORMANCE”枚举值添加到请求属性“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”中
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[子规范 #3: GCP 区域复制规范]/effectiveReadOnlySpecs/oneOf[子规范 #1: Amazon Web Services 集群硬件设置]/ebsVolumeType'
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规格]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 在请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'中添加了新的 'HIGH_PERFORMANCE' 枚举值
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 在请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规格]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'中添加了新的 'HIGH_PERFORMANCE' 枚举值。
  • 将新的“HIGH_PERFORMANCE”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType”中
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的“HIGH_PERFORMANCE”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure 区域复制规范]/readOnlySpecs/oneOf[subschema #1： Amazon Web Services 集群硬件设置]/ebsVolumeType”
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: Amazon Web Services 集群硬件设置]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[子规范 #3: GCP 区域复制规范]/effectiveReadOnlySpecs/oneOf[子规范 #1: Amazon Web Services 集群硬件设置]/ebsVolumeType'
  • 将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType'
  • 已将新的 'HIGH_PERFORMANCE' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/ebsVolumeType'
  • 在请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional ReplicationSpecifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings] 中添加了新的 'HIGH_PERFORMANCE'枚举值/ebsVolumeType'

28 5 月2026发布

GET /api/atlas/v2
Updated
  • 为状态为“401”的响应添加了媒体类型“应用程序/json”
GET /api/atlas/v2/alertConfigs/matchers/fieldNames
Updated
  • 将“subschema #8: NDS Autoscaling Matcher Fields”（子模式 #：NDS 自动扩展匹配器字段）添加到了响应的“/items/”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“#/components/模式/NDSAutoscalingAlertConfigViewForNdsGroup”添加到响应的“results/items/”响应属性“oneOf”列表中
  • 在“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #7: Atlas Audit Types]/”响应属性中添加了新的“LOG_STREAMING_EXPORT_FAILED_NONRETRYABLE、LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED”枚举值
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“#/components/schemas/NDSAutoscalingAlertConfigViewForNdsGroup”添加到请求正文“oneOf”列表
  • 将“#/components/schemas/NDSAutoscalingAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #7: Atlas 审核 Types]/”响应属性中添加了新的“LOG_STREAMING_EXPORT_FAILED_NONRETRYABLE、LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED”枚举值
  • 在请求属性“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #7: Atlas Atlas 审核 Types]/”中添加了新的“LOG_STREAMING_EXPORT_FAILED_NONRETRYABLE、LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED”枚举值
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“#/components/schemas/NDSAutoscalingAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #7: Atlas 审核 Types]/”响应属性中添加了新的“LOG_STREAMING_EXPORT_FAILED_NONRETRYABLE、LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“#/components/schemas/NDSAutoscalingAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #7: Atlas 审核 Types]/”响应属性中添加了新的“LOG_STREAMING_EXPORT_FAILED_NONRETRYABLE、LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED”枚举值
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“#/components/schemas/NDSAutoscalingAlertConfigViewForNdsGroup”添加到请求正文“oneOf”列表
  • 将“#/components/schemas/NDSAutoscalingAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #7: Atlas 审核 Types]/”响应属性中添加了新的“LOG_STREAMING_EXPORT_FAILED_NONRETRYABLE、LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED”枚举值
  • 在请求属性“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #7: Atlas Atlas 审核 Types]/”中添加了新的“LOG_STREAMING_EXPORT_FAILED_NONRETRYABLE、LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED”枚举值
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 在“results/items/oneOf[subschema #8: Any other Alerts]/eventTypeName/oneOf[subschema #7: Atlas Audit Types]/”响应属性中添加了新的“LOG_STREAMING_EXPORT_FAILED_NONRETRYABLE、LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 在“results/items/oneOf[subschema #8: Any other Alerts]/eventTypeName/oneOf[subschema #7: Atlas Audit Types]/”响应属性中添加了新的“LOG_STREAMING_EXPORT_FAILED_NONRETRYABLE、LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 在“/oneOf[subschema #8: Any other 警报]/eventTypeName/oneOf[subschema #7: Atlas Audit Types]/”响应属性中添加了新的“LOG_STREAMING_EXPORT_FAILED_NONRETRYABLE、LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 在“/oneOf[subschema #8: Any other 警报]/eventTypeName/oneOf[subschema #7: Atlas Audit Types]/”响应属性中添加了新的“LOG_STREAMING_EXPORT_FAILED_NONRETRYABLE、LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 将“#/components/模式/NDSAutoscalingAlertConfigViewForNdsGroup”添加到响应的“results/items/”响应属性“oneOf”列表中
  • 在“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #7: Atlas Audit Types]/”响应属性中添加了新的“LOG_STREAMING_EXPORT_FAILED_NONRETRYABLE、LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED”枚举值
POST /api/atlas/v2/groups/{groupId}/clusterConfigurations:validate
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes
Updated
  • 媒体类型“应用程序/vnd.atlas.2024-05-30+json”已针对响应状态“503”更改为更通用的媒体类型“应用程序/json”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}
Updated
  • 媒体类型“应用程序/vnd.atlas.2024-05-30+json”已针对响应状态“503”更改为更通用的媒体类型“应用程序/json”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • 媒体类型“应用程序/vnd.atlas.2024-05-30+json”已针对响应状态“503”更改为更通用的媒体类型“应用程序/json”
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 在“results/items/eventTypeName”响应属性中添加了新的“CHARTS_DASBOARD_EXPORTED、CHARTS_DASHBOARD_EXPORT_FAILED、CHARTS_DASHBOARD_IMPORTED、CHARTS_DASHBOARD_IMPORT_FAILED”枚举值
  • Added the new 'CLUSTER_APPLY_CONNECTION_RATE_LIMIT_REQUESTED, LOG_STREAMING_EXPORT_FAILED_NONRETRYABLE, LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED, LOG_STREAMING_EXPORT_RECOVERED, LOG_STREAMING_REPLAY_COMPLETE, LOG_STREAMING_REPLAY_STARTED' 枚举 values to the 'results/items/oneOf[subschema #15: Atlas 项目 Atlas 审核]/eventTypeName' response 属性
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 在 '/eventTypeName' 响应属性中添加了新的 'CHARTS_DASBOARD_EXPORTED、CHARTS_DASHBOARD_EXPORT_FAILED、CHARTS_DASHBOARD_IMPORTED、CHARTS_DASHBOARD_IMPORT_FAILED'枚举值
  • Added the new 'CLUSTER_APPLY_CONNECTION_RATE_LIMIT_REQUESTED, LOG_STREAMING_EXPORT_FAILED_NONRETRYABLE, LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED, LOG_STREAMING_EXPORT_RECOVERED, LOG_STREAMING_REPLAY_COMPLETE, LOG_STREAMING_REPLAY_STARTED' 枚举 values to the '/oneOf[subschema #15: Atlas 项目 Atlas 审核]/eventTypeName' response 属性
GET /api/atlas/v2/groups/{groupId}/maintenanceWindow
Updated
  • 在响应中添加了可选属性“ectiveWaveAssignment、waveAssignment”
PATCH /api/atlas/v2/groups/{groupId}/maintenanceWindow
Updated
  • 添加了新的可选请求属性“waveAssignment”
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/groups
Updated
  • 在响应中添加了可选属性“results/items/roles”

21 5 月2026发布

GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 在“results/items/oneOf[subschema #15: Atlas 项目 Atlas 审核]/eventTypeName”响应属性中添加了新的“PROJECT_COLLECT_DATABASE_STATISTICS_UPDATED、SEARCH_HOST_DISABLE_FTS、SEARCH_HOST_PAUSE_ALL_INITIAL_SYNCS”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 在“/oneOf[subschema #15: Atlas Project Audits]/eventTypeName”响应属性中添加了新的“PROJECT_COLLECT_DATABASE_STATISTICS_UPDATED、SEARCH_HOST_DISABLE_FTS、SEARCH_HOST_PAUSE_ALL_INITIAL_SYNCS”枚举值

12 5 月2026发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在“results/items/oneOf[subschema #1: Any other 警报配置]/eventTypeName/oneOf[subschema #15: 托管事件类型]/”响应属性中添加了新的“HOST_SEARCH_PROCESS_THROTTLING”枚举值
  • 将新的“HOST_SEARCH_PROCESS_THROTTLING”枚举值添加到“results/items/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”响应属性
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #15: 托管 Event Types]/”响应属性中添加了新的“HOST_SEARCH_PROCESS_THROTTLING”枚举值
  • 将新的“HOST_SEARCH_PROCESS_THROTTLING”枚举值添加到“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”响应属性
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #15: Host Event Types]/' 中添加了新的 'HOST_SEARCH_PROCESS_THROTTLING'枚举值
  • 已将新的“HOST_SEARCH_PROCESS_THROTTLING”枚举值添加到请求属性“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #15: 托管 Event Types]/”响应属性中添加了新的“HOST_SEARCH_PROCESS_THROTTLING”枚举值
  • 将新的“HOST_SEARCH_PROCESS_THROTTLING”枚举值添加到“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”响应属性
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #15: 托管 Event Types]/”响应属性中添加了新的“HOST_SEARCH_PROCESS_THROTTLING”枚举值
  • 将新的“HOST_SEARCH_PROCESS_THROTTLING”枚举值添加到“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”响应属性
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #15: 托管 Event Types]/”响应属性中添加了新的“HOST_SEARCH_PROCESS_THROTTLING”枚举值
  • 将新的“HOST_SEARCH_PROCESS_THROTTLING”枚举值添加到“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”响应属性
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #15: Host Event Types]/' 中添加了新的 'HOST_SEARCH_PROCESS_THROTTLING'枚举值
  • 已将新的“HOST_SEARCH_PROCESS_THROTTLING”枚举值添加到请求属性“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 将新的“HOST_SEARCH_PROCESS_THROTTLING”枚举值添加到“results/items/oneOf[subschema #3: 主机警报]/eventTypeName”响应属性
  • 将新的“HOST_SEARCH_PROCESS_THROTTLING”枚举值添加到“results/items/oneOf[subschema #7: Stream Processor Alerts]/eventTypeName”响应属性
  • 在“results/items/oneOf[subschema #8: Any other Alerts]/eventTypeName/oneOf[subschema #19: 托管 Event Types]/”响应属性中添加了新的“HOST_SEARCH_PROCESS_THROTTLING”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 将新的“HOST_SEARCH_PROCESS_THROTTLING”枚举值添加到“results/items/oneOf[subschema #3: 主机警报]/eventTypeName”响应属性
  • 将新的“HOST_SEARCH_PROCESS_THROTTLING”枚举值添加到“results/items/oneOf[subschema #7: Stream Processor Alerts]/eventTypeName”响应属性
  • 在“results/items/oneOf[subschema #8: Any other Alerts]/eventTypeName/oneOf[subschema #19: 托管 Event Types]/”响应属性中添加了新的“HOST_SEARCH_PROCESS_THROTTLING”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将新的“HOST_SEARCH_PROCESS_THROTTLING”枚举值添加到“/oneOf[subschema #3: Host Alerts]/eventTypeName”响应属性
  • 将新的“HOST_SEARCH_PROCESS_THROTTLING”枚举值添加到“/oneOf[subschema #7: Stream Processor 警报]/eventTypeName”响应属性
  • 在“/oneOf[subschema #8: Any other 警报]/eventTypeName/oneOf[subschema #19: 托管 事件 Types]/”响应属性中添加了新的“HOST_SEARCH_PROCESS_THROTTLING”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将新的“HOST_SEARCH_PROCESS_THROTTLING”枚举值添加到“/oneOf[subschema #3: Host Alerts]/eventTypeName”响应属性
  • 将新的“HOST_SEARCH_PROCESS_THROTTLING”枚举值添加到“/oneOf[subschema #7: Stream Processor 警报]/eventTypeName”响应属性
  • 在“/oneOf[subschema #8: Any other 警报]/eventTypeName/oneOf[subschema #19: 托管 事件 Types]/”响应属性中添加了新的“HOST_SEARCH_PROCESS_THROTTLING”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 在“results/items/oneOf[subschema #1: Any other 警报配置]/eventTypeName/oneOf[subschema #15: 托管事件类型]/”响应属性中添加了新的“HOST_SEARCH_PROCESS_THROTTLING”枚举值
  • 将新的“HOST_SEARCH_PROCESS_THROTTLING”枚举值添加到“results/items/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”响应属性
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 已将新的 'HOST_SEARCH_PROCESS_NOT_THROTTLING、HOST_SEARCH_PROCESS_THROTTLING'枚举值添加到 'results/items/oneOf[subschema #13: 托管事件]/eventTypeName' 响应属性
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 在 '/oneOf[subschema #13: Host Events]/eventTypeName' 响应属性中添加了新的 'HOST_SEARCH_PROCESS_NOT_THROTTLING、HOST_SEARCH_PROCESS_THROTTLING'枚举值

07 5 月2026发布

POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 更新了 NO_PAYMENT_INFORMATION_FOUND 错误消息，添加了一个链接，以便用户在未找到付款信息时添加付款方式。
  • 更新了 NO_PAYMENT_INFORMATION_FOUND 错误消息，添加了一个链接，以便用户在未找到付款信息时添加付款方式。
  • 更新了 NO_PAYMENT_INFORMATION_FOUND 错误消息，添加了一个链接，以便用户在未找到付款信息时添加付款方式。
  • 更新了 NO_PAYMENT_INFORMATION_FOUND 错误消息，添加了一个链接，以便用户在未找到付款信息时添加付款方式。
  • 更新了 NO_PAYMENT_INFORMATION_FOUND 错误消息，添加了一个链接，以便用户在未找到付款信息时添加付款方式。
  • 更新了 NO_PAYMENT_INFORMATION_FOUND 错误消息，添加了一个链接，以便用户在未找到付款信息时添加付款方式。
  • 更新了 NO_PAYMENT_INFORMATION_FOUND 错误消息，添加了一个链接，以便用户在未找到付款信息时添加付款方式。
  • 更新了 NO_PAYMENT_INFORMATION_FOUND 错误消息，添加了一个链接，以便用户在未找到付款信息时添加付款方式。
  • 更新了 NO_PAYMENT_INFORMATION_FOUND 错误消息，添加了一个链接，以便用户在未找到付款信息时添加付款方式。
  • 更新了 NO_PAYMENT_INFORMATION_FOUND 错误消息，添加了一个链接，以便用户在未找到付款信息时添加付款方式。
POST /api/atlas/v2/groups/{groupId}/flexClusters
Updated
  • 更新了 NO_PAYMENT_INFORMATION_FOUND 错误消息，添加了一个链接，以便用户在未找到付款信息时添加付款方式。
  • 更新了 NO_PAYMENT_INFORMATION_FOUND 错误消息，添加了一个链接，以便用户在未找到付款信息时添加付款方式。
  • 更新了 NO_PAYMENT_INFORMATION_FOUND 错误消息，添加了一个链接，以便用户在未找到付款信息时添加付款方式。
POST /api/atlas/v2/groups/{groupId}/flexClusters:tenantUpgrade
Updated
  • 更新了 NO_PAYMENT_INFORMATION_FOUND 错误消息，添加了一个链接，以便用户在未找到付款信息时添加付款方式。
  • 更新了 NO_PAYMENT_INFORMATION_FOUND 错误消息，添加了一个链接，以便用户在未找到付款信息时添加付款方式。
  • 更新了 NO_PAYMENT_INFORMATION_FOUND 错误消息，添加了一个链接，以便用户在未找到付款信息时添加付款方式。
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 更新了 NO_PAYMENT_INFORMATION_FOUND 错误消息，添加了一个链接，以便用户在未找到付款信息时添加付款方式。
  • 更新了 NO_PAYMENT_INFORMATION_FOUND 错误消息，添加了一个链接，以便用户在未找到付款信息时添加付款方式。
  • 更新了 NO_PAYMENT_INFORMATION_FOUND 错误消息，添加了一个链接，以便用户在未找到付款信息时添加付款方式。
  • 更新了 NO_PAYMENT_INFORMATION_FOUND 错误消息，添加了一个链接，以便用户在未找到付款信息时添加付款方式。
  • 更新了 NO_PAYMENT_INFORMATION_FOUND 错误消息，添加了一个链接，以便用户在未找到付款信息时添加付款方式。
  • 更新了 NO_PAYMENT_INFORMATION_FOUND 错误消息，添加了一个链接，以便用户在未找到付款信息时添加付款方式。
  • 更新了 NO_PAYMENT_INFORMATION_FOUND 错误消息，添加了一个链接，以便用户在未找到付款信息时添加付款方式。
  • 更新了 NO_PAYMENT_INFORMATION_FOUND 错误消息，添加了一个链接，以便用户在未找到付款信息时添加付款方式。
  • 更新了 NO_PAYMENT_INFORMATION_FOUND 错误消息，添加了一个链接，以便用户在未找到付款信息时添加付款方式。

06 5 月2026发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在“results/items/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #13: 自动伸缩 Atlas 审核 Types]/”响应属性中添加了新的“CLUSTER_RESHARDING_COMPLETED”枚举值
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #13: 自动伸缩 Atlas 审核 Types]/”响应属性中添加了新的“CLUSTER_RESHARDING_COMPLETED”枚举值
  • 已将新的“CLUSTER_RESHARDING_COMPLETED”枚举值添加到请求属性“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #13: 自动伸缩 Atlas 审核 Types]/”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #13: 自动伸缩 Atlas 审核 Types]/”响应属性中添加了新的“CLUSTER_RESHARDING_COMPLETED”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #13: 自动伸缩 Atlas 审核 Types]/”响应属性中添加了新的“CLUSTER_RESHARDING_COMPLETED”枚举值
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #13: 自动伸缩 Atlas 审核 Types]/”响应属性中添加了新的“CLUSTER_RESHARDING_COMPLETED”枚举值
  • 已将新的“CLUSTER_RESHARDING_COMPLETED”枚举值添加到请求属性“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #13: 自动伸缩 Atlas 审核 Types]/”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 将“#/components/schemas/FlexMetricAlert”添加到响应的“results/items/”响应属性“oneOf”列表中
  • 将新的 'CLUSTER_RESHARDING_COMPLETED'枚举添加到 'results/items/oneOf[subschema #7: Any other 警报 -> subschema #8: Any other 警报]/eventTypeName/oneOf[subschema #16: 自动伸缩 Atlas 审核 Types]/' 响应属性
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 将“#/components/schemas/FlexMetricAlert”添加到响应的“results/items/”响应属性“oneOf”列表中
  • 将新的 'CLUSTER_RESHARDING_COMPLETED'枚举添加到 'results/items/oneOf[subschema #7: Any other 警报 -> subschema #8: Any other 警报]/eventTypeName/oneOf[subschema #16: 自动伸缩 Atlas 审核 Types]/' 响应属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“#/components/schemas/FlexMetricAlert”添加到响应的响应正文“oneOf”列表中
  • 将新的 'CLUSTER_RESHARDING_COMPLETED'枚举值添加到 '/oneOf[subschema #7: Any Other 警报 -> subschema #8: Any Other 警报]/eventTypeName/oneOf[subschema #16: 自动伸缩 Atlas 审核类型]/' 响应属性
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“#/components/schemas/FlexMetricAlert”添加到响应的响应正文“oneOf”列表中
  • 将新的 'CLUSTER_RESHARDING_COMPLETED'枚举值添加到 '/oneOf[subschema #7: Any Other 警报 -> subschema #8: Any Other 警报]/eventTypeName/oneOf[subschema #16: 自动伸缩 Atlas 审核类型]/' 响应属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 在“results/items/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #13: 自动伸缩 Atlas 审核 Types]/”响应属性中添加了新的“CLUSTER_RESHARDING_COMPLETED”枚举值
GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到“results/items/effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到“results/items/effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将 'results/items/ectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes] 的枚举值]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制规格]/analyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 设置]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M400_NVME_GEN_2”、“M40_GEN_2”、“M40_NVME_GEN_2”、“M50_GEN_2”、“M50_NVME_GEN_2”、“M60_GEN_2”、“M60_NVME_GEN_2”、“M80_GEN_2”、“M80_NVME_GEN_2”、“R200_GEN_2”、“R300_GEN_2”、“R400_GEN_2”、“R40_GEN_2”、“R50_GEN_2”、“R60_GEN_2”、“R700_GEN_2”、“R80_GEN_2”枚举值到“results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例 Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 实例 Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M400_NVME_GEN_2”、“M40_GEN_2”、“M40_NVME_GEN_2”、“M50_GEN_2”、“M50_NVME_GEN_2”、“M60_GEN_2”、“M60_NVME_GEN_2”、“M80_GEN_2”、“M80_NVME_GEN_2”、“R200_GEN_2”、“R300_GEN_2”、“R400_GEN_2”、“R40_GEN_2”、“R50_GEN_2”、“R60_GEN_2”、“R700_GEN_2”、“R80_GEN_2”枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制规格]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'results/items/effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到“results/items/effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到 'results/items/ectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize ' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到 'results/items/ectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes] ]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到 'results/items/effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/analyticsAutoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes]/' 属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群 Hardware Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R 80_GEN_2”枚举值到“results/items/effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/autoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到 'results/items/ectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 实例大小]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'results/items/effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'results/items/ectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication 规范]/有效ElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/instanceSize ' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'results/items/effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize ' 属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R 80_GEN_2将 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize 的枚举值' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R 80_GEN_2”枚举值到“results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize”响应属性中。
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到 'results/items/ectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例大小]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 实例大小]/' 响应属性
  • 添加了新的“M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2”枚举值到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/instanceSize ' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到 'results/items/ectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例大小]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到 'results/items/ectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 实例大小]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/instanceSize ' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到 'results/items/ectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize ' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R 80_GEN_2”枚举值到“results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到“results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到“results/items/replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2' 枚举值到 'results/items/复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到“results/items/复制规格/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制规格]/analyticsAutoScaling/compute/最小实例大小/oneOf[subschema #1: AWS 实例大小]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到“results/items/复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/analyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将 'results/items/复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/autoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将 'results/items/复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/autoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes] 的枚举值]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'results/items/复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/ validElectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize ' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'results/items/复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Schedules]/forcedReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/instanceSize ' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到“results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制规格]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到 'results/items/复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/readOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize ' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到 'results/items/复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes] ]/' 属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes] ]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize ' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R 80_GEN_2将 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes] 的枚举值]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R 80_GEN_2将 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes] 的枚举值]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'results/items/复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/forcedAnalyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize ' 属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/有效ElectableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize ' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'results/items/复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/forcedReadOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize ' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R 80_GEN_2将 'results/items/复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件设置]/instanceSize 的枚举值' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R 80_GEN_2将 'results/items/复制/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication 规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/instanceSize 的枚举值' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例大小]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 实例大小]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R 80_GEN_2将 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication 复制]/analyticsSpecs/oneOf[subschema #1: AWS Cluster 硬件 Settings]/instanceSize 的枚举值' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例大小]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 实例大小]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'results/items/复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 设置]/instanceSize ' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'results/items/复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 规范]/ validReadOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize ' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R 80_GEN_2将 'results/items/复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 设置]/instanceSize 的枚举值' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R 80_GEN_2将 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication 规范]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize 的枚举值' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到“results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize”响应属性
  • 添加了可选属性 'results/items/adaptiveCapacity、results/items/effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput、results/items/effectiveReplicationSpecs/items/regionConfigs /items/oneOf[subschema #1: AWS Regional 复制规范]/analyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1：AWS 集群硬件设置]/diskThroughput, 结果/项目/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1：AWS 区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/electableSpecs/oneOf[subschema # 1：AWS 集群硬件设置]/diskThroughput，results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1：AWS 区域复制规范]/readOnlySpecs/oneOf[subschema #1：AWS 集群硬件设置]/diskThroughput, 结果/项目/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, Results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema # 2： Azure区域复制规范]/electableSpecs/oneOf[subschema #1：AWS 集群硬件设置]/diskThroughput，results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsSpecs/ oneOf[sub schema #1：AWS 集群硬件设置]/diskThroughput，results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, 结果/项目/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/ diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制规范]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[ subschema #4：租户区域复制规范]/electableSpecs/oneOf[subschema #1：AWS 集群硬件设置]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1：AWS 集群硬件设置]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/analyticsSpecs/oneOf[subschema #1：AWS 集群硬件设置]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, 结果/ items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1 [subschema #1: AWS 集群硬件设置]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/readOnlySpecs/oneOf[ subschema #1：AWS 集群硬件设置]/diskThroughput，results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/analyticsSpecs/oneOf[subschema #1： AWS 集群硬件设置]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, results/items/replicationSpecs/items/ regionConfigs/items/oneOf[subschema #2: Azure Regional 复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[ subschema #2: Azure区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/ readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput、results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/effectiveAnalyticsSpecs /oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput , results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, results/items/replicationSpecs /items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items /oneOf[subschema #3: GCP Regional 复制规范]/electableSpecs/oneOf[subschema #1：AWS 集群硬件设置]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/readOnlySpecs/ oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput' 到响应
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'forcedReplicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/analyticsAutoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制规格]/analyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 设置]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制规范]/autoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes]/' 属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/ effectiveElectableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'enefableReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/ validReadOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/readOnlySpecs/oneOf[subschema #1: AWS Cluster 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M400_NVME_GEN_2”、“M40_GEN_2”、“M40_NVME_GEN_2”、“M50_GEN_2”、“M50_NVME_GEN_2”、“M60_GEN_2”、“M60_NVME_GEN_2”、“M80_GEN_2”、“M80_NVME_GEN_2”、“R200_GEN_2”、“R300_GEN_2”、“R400_GEN_2”、“R40_GEN_2”、“R50_GEN_2”、“R60_GEN_2”、“R700_GEN_2”、“R80_GEN_2”枚举值到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制规格]/analyticsAutoScaling/compute/min实例大小/oneOf[subschema #1: AWS Instance Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/analyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例 Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/autoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/readOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值到 'enefableReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/analyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制规格]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例 Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制规范]/autoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/ effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/readOnlySpecs/oneOf[subschema #1: AWS Cluster 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional 复制Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到“replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制规格]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例大小]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到“复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/analyticsSpecs/oneOf[subschema #1: AWS Cluster 硬件 Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举值添加到“复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/autoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/autoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/forcedAnalyticsSpecs/oneOf[subschema #1: AWS 集群 硬件设置]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/ectiveElectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/forcedReadOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制规格]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到“复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制规格]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例大小]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/forcedAnalyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/forcedReadOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到“复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到“复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/analyticsAutoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/analyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication 规范]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 实例大小]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/forcedAnalyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 '复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/ validElectableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/forcedReadOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/readOnlySpecs/oneOf[subschema #1: AWS Cluster 硬件 Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件 Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'forcedReplicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值枚举到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例 Sizes]/'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到请求属性'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制规格]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'ective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/analyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/autoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'ective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/autoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS Cluster 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/readOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到请求属性“effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/”
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'enefableReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/analyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/autoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/autoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes]/'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS Cluster 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/ effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制]/electableSpecs/oneOf[subschema #1: AWS Cluster 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/readOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'enefableReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例大小]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'enefableReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 实例大小]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2' 枚举值添加到 请求 属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/analyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'enefableReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例大小]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'forcedReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 实例大小]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'enefableReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/enemyAnalyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'enefableReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/ validElectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'enefableReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/ validReadOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/readOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional 复制 Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R 80_GEN_2请求属性'replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS Cluster 硬件 Settings]/instanceSize' 的枚举值
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到请求属性'复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制规格]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 实例大小]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/analyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举值到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制规格]/autoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/ectiveElectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/ validReadOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制 Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例大小]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到请求属性'复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/analyticsAutoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/ectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/ectiveElectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/forcedReadOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到请求属性'复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例大小]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/analyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例大小]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 实例大小]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/forcedAnalyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/有效ReadOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/readOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional ReplicationSpecifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了可选属性 'adaptiveCapacity, validReplicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/forcedAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/有效ElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置] /diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/有效ReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThrou ghput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/ oneOf[subschema #1: AWS Regional ReplicationSpecifications]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/有效分析规范/oneOf[subschema # 1：AWS 集群硬件设置]/diskThroughput，有效ReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/有效ElectableSpecs/oneOf[subschema #1：AWS 集群 H ardware Settings]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/有效ReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/ regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsSpecs/ oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/有效分析规范/oneOf[sub schema #1: AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/有效ElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/有效ReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/regionConfigs/ items/oneOf[subschema #3: GCP区域复制规范]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/readOnlySpecs/oneOf[subschema #1：AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4：租户区域复制规范]/ electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/ items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/analyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/有效分析规范/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/有效ElectableSpecs/oneOf[ subschema #1: AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/有效ReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThrou ghput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, replicationSpecs/items/regionConfigs/items/ oneOf[subschema #1: AWS Regional ReplicationSpecifications]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/有效分析规范/oneOf[subschema # 1：AWS 集群硬件设置]/diskThroughput，replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/有效ElectableSpecs/oneOf[subschema #1：AWS 集群硬件设置]/ diskThroughput,replicatio nSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/有效ReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[ subschema #2： Azure区域复制规范]/electableSpecs/oneOf[subschema #1：AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsSpecs/oneOf[subschema #1：AWS 集群硬件设置]/diskThroughput，replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/ validAnalyticsSpecs/oneOf[subschema #1：AWS 集群硬件设置]/diskThroughput， replicationSpecs/items/regio nConfigs/items/oneOf[subschema #3: GCP区域复制规范]/有效ElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/ validReadOnlySpecs/oneOf[subschema #1：AWS 集群硬件设置]/diskThroughput，replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/electableSpecs/ oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群Hardware Settings]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput' 到响应
  • 添加了新的可选请求属性“adaptiveCapacity”
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到“providerSettings/oneOf[subschema #1: Cloud Service Provider Settings for a Cluster]/autoScaling/compute/maxInstanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举到 'providerSettings/oneOf[subschema #1: Cloud Service Provider Settings for a Cluster]/autoScaling/compute/minInstanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到“providerSettings/oneOf[subschema #1: Cloud Service Provider Settings for a Cluster]/instanceSizeName”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R 80_GEN_2请求属性'providerSettings/oneOf[subschema #1: Cloud Service Provider Settings for a Cluster]/autoScaling/compute/maxInstanceSize' 的枚举值
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R 80_GEN_2请求属性'providerSettings/oneOf[subschema #1: Cloud Service Provider Settings for a Cluster]/autoScaling/compute/minInstanceSize' 的枚举值
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R 80_GEN_2请求属性'providerSettings/oneOf[subschema #1: 云 服务 提供商 Settings for a 集群]/instanceSizeName' 的枚举值
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgradeToServerless
Updated
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'providerSettings/effectiveInstanceSizeName/oneOf[subschema #1: AWS 实例 Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R 80_GEN_2'请求属性'providerSettings/forcedInstanceSizeName/oneOf[subschema #1: AWS Instance Sizes]/' 的枚举值
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'forcedReplicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/analyticsAutoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制规格]/analyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 设置]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制规范]/autoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes]/' 属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/ effectiveElectableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'enefableReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/ validReadOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/readOnlySpecs/oneOf[subschema #1: AWS Cluster 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M400_NVME_GEN_2”、“M40_GEN_2”、“M40_NVME_GEN_2”、“M50_GEN_2”、“M50_NVME_GEN_2”、“M60_GEN_2”、“M60_NVME_GEN_2”、“M80_GEN_2”、“M80_NVME_GEN_2”、“R200_GEN_2”、“R300_GEN_2”、“R400_GEN_2”、“R40_GEN_2”、“R50_GEN_2”、“R60_GEN_2”、“R700_GEN_2”、“R80_GEN_2”枚举值到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制规格]/analyticsAutoScaling/compute/min实例大小/oneOf[subschema #1: AWS Instance Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/analyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例 Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/autoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/readOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值到 'enefableReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/analyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制规格]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例 Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制规范]/autoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/ effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/readOnlySpecs/oneOf[subschema #1: AWS Cluster 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional 复制Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到“replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制规格]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例大小]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到“复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/analyticsSpecs/oneOf[subschema #1: AWS Cluster 硬件 Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举值添加到“复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/autoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/autoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/forcedAnalyticsSpecs/oneOf[subschema #1: AWS 集群 硬件设置]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/ectiveElectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/forcedReadOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制规格]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到“复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制规格]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例大小]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/forcedAnalyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/forcedReadOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到“复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到“复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/analyticsAutoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/analyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication 规范]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 实例大小]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/forcedAnalyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 '复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/ validElectableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/forcedReadOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/readOnlySpecs/oneOf[subschema #1: AWS Cluster 硬件 Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件 Settings]/instanceSize”响应属性
  • 添加了可选属性 'adaptiveCapacity, validReplicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/forcedAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/有效ElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置] /diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/有效ReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThrou ghput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/ oneOf[subschema #1: AWS Regional ReplicationSpecifications]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/有效分析规范/oneOf[subschema # 1：AWS 集群硬件设置]/diskThroughput，有效ReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/有效ElectableSpecs/oneOf[subschema #1：AWS 集群 H ardware Settings]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/有效ReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/ regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsSpecs/ oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/有效分析规范/oneOf[sub schema #1: AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/有效ElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/有效ReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/regionConfigs/ items/oneOf[subschema #3: GCP区域复制规范]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/readOnlySpecs/oneOf[subschema #1：AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4：租户区域复制规范]/ electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/ items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/analyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/有效分析规范/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/有效ElectableSpecs/oneOf[ subschema #1: AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/有效ReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThrou ghput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, replicationSpecs/items/regionConfigs/items/ oneOf[subschema #1: AWS Regional ReplicationSpecifications]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/有效分析规范/oneOf[subschema # 1：AWS 集群硬件设置]/diskThroughput，replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/有效ElectableSpecs/oneOf[subschema #1：AWS 集群硬件设置]/ diskThroughput,replicatio nSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/有效ReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[ subschema #2： Azure区域复制规范]/electableSpecs/oneOf[subschema #1：AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsSpecs/oneOf[subschema #1：AWS 集群硬件设置]/diskThroughput，replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/ validAnalyticsSpecs/oneOf[subschema #1：AWS 集群硬件设置]/diskThroughput， replicationSpecs/items/regio nConfigs/items/oneOf[subschema #3: GCP区域复制规范]/有效ElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/ validReadOnlySpecs/oneOf[subschema #1：AWS 集群硬件设置]/diskThroughput，replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/electableSpecs/ oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群Hardware Settings]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput' 到响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'forcedReplicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/analyticsAutoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制规格]/analyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 设置]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制规范]/autoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes]/' 属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/ effectiveElectableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'enefableReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/ validReadOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/readOnlySpecs/oneOf[subschema #1: AWS Cluster 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M400_NVME_GEN_2”、“M40_GEN_2”、“M40_NVME_GEN_2”、“M50_GEN_2”、“M50_NVME_GEN_2”、“M60_GEN_2”、“M60_NVME_GEN_2”、“M80_GEN_2”、“M80_NVME_GEN_2”、“R200_GEN_2”、“R300_GEN_2”、“R400_GEN_2”、“R40_GEN_2”、“R50_GEN_2”、“R60_GEN_2”、“R700_GEN_2”、“R80_GEN_2”枚举值到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制规格]/analyticsAutoScaling/compute/min实例大小/oneOf[subschema #1: AWS Instance Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/analyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例 Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/autoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/readOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值到 'enefableReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/analyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到“effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制规格]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例 Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制规范]/autoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes]/' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2' 枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制规范]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/ effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/readOnlySpecs/oneOf[subschema #1: AWS Cluster 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'effective复制Specs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional 复制Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到“replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制规格]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例大小]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到“复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/analyticsSpecs/oneOf[subschema #1: AWS Cluster 硬件 Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举值添加到“复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/autoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/autoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/forcedAnalyticsSpecs/oneOf[subschema #1: AWS 集群 硬件设置]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/ectiveElectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/forcedReadOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制规格]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到“复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制规格]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例大小]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/forcedAnalyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/forcedReadOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到“复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到“复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/analyticsAutoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/analyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication 规范]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 实例大小]/”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/forcedAnalyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 '复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/ validElectableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/forcedReadOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize' 响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/readOnlySpecs/oneOf[subschema #1: AWS Cluster 硬件 Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/oneOf[subschema #1: AWS 集群硬件 Settings]/instanceSize”响应属性
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'forcedReplicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值枚举到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例 Sizes]/'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到请求属性'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制规格]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'ective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/analyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/autoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'ective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/autoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS Cluster 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/readOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到请求属性“effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/”
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'enefableReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/analyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/autoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/autoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes]/'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS Cluster 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/ effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制]/electableSpecs/oneOf[subschema #1: AWS Cluster 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/readOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'enefableReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例大小]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'enefableReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 实例大小]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2' 枚举值添加到 请求 属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/analyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'enefableReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例大小]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'forcedReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 实例大小]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'enefableReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/enemyAnalyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'enefableReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/ validElectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'enefableReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/ validReadOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/readOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional 复制 Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R 80_GEN_2请求属性'replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS Cluster 硬件 Settings]/instanceSize' 的枚举值
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到请求属性'复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制规格]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 实例大小]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/analyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举值到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制规格]/autoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/ectiveElectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/ validReadOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制 Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例大小]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到请求属性'复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/analyticsAutoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/ectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/ectiveElectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/forcedReadOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到请求属性'复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例大小]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/analyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例大小]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 实例大小]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/forcedAnalyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/有效ReadOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/readOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional ReplicationSpecifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了可选属性 'adaptiveCapacity, validReplicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/forcedAnalyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/有效ElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置] /diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/有效ReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThrou ghput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/ oneOf[subschema #1: AWS Regional ReplicationSpecifications]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/有效分析规范/oneOf[subschema # 1：AWS 集群硬件设置]/diskThroughput，有效ReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/有效ElectableSpecs/oneOf[subschema #1：AWS 集群 H ardware Settings]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/有效ReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/ regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsSpecs/ oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/有效分析规范/oneOf[sub schema #1: AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/有效ElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/有效ReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/regionConfigs/ items/oneOf[subschema #3: GCP区域复制规范]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/readOnlySpecs/oneOf[subschema #1：AWS 集群硬件设置]/diskThroughput, validReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4：租户区域复制规范]/ electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/ items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/analyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/有效分析规范/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/有效ElectableSpecs/oneOf[ subschema #1: AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制规范]/有效ReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThrou ghput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, replicationSpecs/items/regionConfigs/items/ oneOf[subschema #1: AWS Regional ReplicationSpecifications]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional复制规范]/analyticsSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/有效分析规范/oneOf[subschema # 1：AWS 集群硬件设置]/diskThroughput，replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/有效ElectableSpecs/oneOf[subschema #1：AWS 集群硬件设置]/ diskThroughput,replicatio nSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/有效ReadOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[ subschema #2： Azure区域复制规范]/electableSpecs/oneOf[subschema #1：AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsSpecs/oneOf[subschema #1：AWS 集群硬件设置]/diskThroughput，replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/ validAnalyticsSpecs/oneOf[subschema #1：AWS 集群硬件设置]/diskThroughput， replicationSpecs/items/regio nConfigs/items/oneOf[subschema #3: GCP区域复制规范]/有效ElectableSpecs/oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/ validReadOnlySpecs/oneOf[subschema #1：AWS 集群硬件设置]/diskThroughput，replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/electableSpecs/ oneOf[subschema #1: AWS 集群硬件设置]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS 集群Hardware Settings]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput' 到响应
  • 添加了新的可选请求属性“adaptiveCapacity”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 请求属性“specs/items/nodeCount”变为可选
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 请求属性“specs/items/nodeCount”变为可选
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 响应属性“results/items/oneOf[subschema #19: ReplicaSet Events]/replicaSetName”变为可为 null
  • 在“results/items/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #39: Ai Models Event Types]/”响应中添加了新的“AI_MODELS_API_KEY_UPDATED、AI_MODELS_RATE_LIMIT_RESET、AI_MODELS_RATE_LIMIT_UPDATED”枚举值属性
  • 将新的枚举值“CLUSTER_MONGUARD_DISABLED、CLUSTER_MONGUARD_ENABLED、CLUSTER_RESET_FORCE_RECONFIG_REQUESTED、MAINTENANCE_WAVE_ASSIGNMENT_ADDED、MAINTENANCE_WAVE_ASSIGNMENT_MODIFIED、MAINTENANCE_WAVE_ASSIGNMENT_REMOVED”添加到“results/items/oneOf[subschema #15: Atlas 项目 Atlas 审核]/eventTypeName” 响应属性
  • 在“results/items/oneOf[subschema #16: 自动伸缩 Atlas 审核]/eventTypeName”响应属性中添加了新的“CLUSTER_RESHARDING_COMPLETED”枚举值
  • 在响应中添加了可选属性“results/items/oneOf[subschema #19: ReplicaSet 事件]/hostname”
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 响应属性“/oneOf[subschema #19: ReplicaSet 事件]/replicaSetName”变为可为 null
  • 在“/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #39: Ai model Event Types]/”响应属性中添加了新的“AI_MODELS_API_KEY_UPDATED、AI_MODELS_RATE_LIMIT_RESET、AI_MODELS_RATE_LIMIT_UPDATED”枚举值
  • 在 '/oneOf[subschema #15: Atlas 项目审核]/eventTypeName' 响应属性中添加了新的 'CLUSTER_MONGUARD_DISABLED、CLUSTER_MONGUARD_ENABLED、CLUSTER_RESET_FORCE_RECONFIG_REQUESTED、MAINTENANCE_WAVE_ASSIGNMENT_ADDED、MAINTENANCE_WAVE_ASSIGNMENT_MODIFIED、MAINTENANCE_WAVE_ASSIGNMENT_REMOVED' 枚举值
  • 已将新的“CLUSTER_RESHARDING_COMPLETED”枚举值添加到“/oneOf[subschema #16: 自动伸缩 Atlas 审核]/eventTypeName”响应属性
  • 在响应中添加了可选属性“/oneOf[subschema #19: ReplicaSet Events]/hostname”
POST /api/atlas/v2/groups/{groupId}/flexClusters:tenantUpgrade
Updated
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'forcedReplicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值枚举到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例 Sizes]/'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到请求属性'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制规格]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'ective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/analyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/autoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'ective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/autoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制 Specifications]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS Cluster 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/readOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到请求属性“effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/”
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'enefableReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/analyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/autoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/autoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes]/'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS Cluster 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制 Specifications]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/ effectiveReadOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制]/electableSpecs/oneOf[subschema #1: AWS Cluster 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/readOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'enefableReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例大小]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'enefableReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 实例大小]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2' 枚举值添加到 请求 属性 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/analyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'enefableReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例大小]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'forcedReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 实例大小]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'enefableReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/enemyAnalyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'enefableReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/ validElectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'enefableReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/ validReadOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effective复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/readOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional 复制 Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R 80_GEN_2请求属性'replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS Cluster 硬件 Settings]/instanceSize' 的枚举值
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到请求属性'复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/analyticsAutoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制规格]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 实例大小]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/analyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举值到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制规格]/autoScaling/compute/max实例Size/oneOf[subschema #1: AWS 实例 Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'复制Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制Specifications]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/ectiveElectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/ validReadOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域复制 Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional ReplicationSpecifications]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例大小]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到请求属性'复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/analyticsAutoScaling/compute/min实例Size/oneOf[subschema #1: AWS 实例 Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/ectiveAnalyticsSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/ectiveElectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/forcedReadOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2”枚举值到请求属性'复制Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 复制Specifications]/electableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例大小]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/analyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 实例大小]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 实例大小]/ '
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/forcedAnalyticsSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'复制Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制Specifications]/effectiveElectableSpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/有效ReadOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 复制 Specifications]/readOnlySpecs/oneOf[subschema #1: AWS 集群 硬件 Settings]/instanceSize'
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional ReplicationSpecifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 添加了新的可选请求属性“adaptiveCapacity”
GET /api/atlas/v2/groups/{groupId}/mongoDBVersions
Updated
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值添加到“results/items/实例大小/oneOf[subschema #1: AWS 实例大小]/”响应属性
POST /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}/endpoint
Updated
  • 添加了请求鉴别器
  • 添加了新的可选请求属性 '/oneOf[subschema #1: AWS]/cloudProvider、/oneOf[subschema #2: AZURE]/cloudProvider、/oneOf[subschema #3: GCP]/cloudProvider、 cloudProvider '
GET /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds
Updated
  • “results/items/endpointId”响应的属性模式“^vpce-[0-9af]{17}$”已删除
  • 将新的“AZURE”枚举值添加到“results/items/ 提供商”响应属性
POST /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds
Updated
  • 从请求属性“endpointId”中删除了模式“^vpce-[0-9af]{17}$”
  • “results/items/endpointId”响应的属性模式“^vpce-[0-9af]{17}$”已删除
  • 将新的“AZURE”枚举值添加到“results/items/ 提供商”响应属性
  • 已将新的 'AZURE'枚举值添加到请求属性' 提供商'
GET /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds/{endpointId}
Updated
  • “endpointId”响应的属性模式“^vpce-[0-9af]{17}$”已删除
  • 已将新的“AZURE”枚举值添加到“提供商”响应属性
GET /api/atlas/v2/groups/{groupId}/serverless
Updated
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2将枚举值枚举到“results/items/providerSettings/forcedInstanceSizeName/oneOf[subschema #1: AWS Instance Sizes]/”响应属性
GET /api/atlas/v2/groups/{groupId}/serverless/{name}
Updated
  • 添加了新的“M140_GEN_2”、“M200_GEN_2”、“M200_NVME_GEN_2”、“M300_GEN_2”、“M30_GEN_2”、“M 400_NVME_GEN_2、M40_GEN_2、M40_NVME_GEN_2、M50_GEN_2、M50_NVME_GEN_2、M60_GEN_2、M60_NVME_GEN_2、M80_GEN_2、M80_NVME_GEN_2、 R200_GEN_2、 R300_GEN_2、 R400_GEN_2、 R40_GEN_2、 R50_GEN_2、 R60_GEN_2、 R700_GEN_2、 R80_GEN_2'枚举值添加到 'providerSettings/effectiveInstanceSizeName/oneOf[subschema #1: AWS 实例 Sizes]/' 响应属性
GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在“results/items/dataProcessRegion/ 区域/”响应属性中添加了新的“PARIS_FRA, australiaeast, brazilsouth”枚举值
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在“dataProcessRegion/ 地区/”响应属性中添加了新的“PARIS_FRA, australiaeast, brazilsouth”枚举值
  • 在请求属性“dataProcessRegion/区域/”中添加了新的“PARIS_FRA, australiaeast, brazilsouth”枚举值
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在“dataProcessRegion/ 地区/”响应属性中添加了新的“PARIS_FRA, australiaeast, brazilsouth”枚举值
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在“dataProcessRegion/ 地区/”响应属性中添加了新的“PARIS_FRA, australiaeast, brazilsouth”枚举值
  • 向请求属性“区域 /”添加了新的“PARIS_FRA, australiaeast, brazilsouth”枚举值
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
Updated
  • 在“dataProcessRegion/ 地区/”响应属性中添加了新的“PARIS_FRA, australiaeast, brazilsouth”枚举值
GET /api/atlas/v2/groups/{groupId}/users
Updated
  • “查询”请求参数“orgMembershipStatus”已弃用，且未提供取消日期
  • 响应属性“results/items/invitationExpiresAt”变为可为 null
  • 响应属性“results/items/invitationExpiresAt”变为可选
  • 添加了新的可选“查询”请求参数“orgMembershipStatuses”
  • 添加了“INVITATION_REJECTED, INVITATION_EXPIRED”鉴别器映射键到“results/items/”响应属性
  • 在“results/items/orgMembershipStatus”响应属性中添加了新的“INVITATION_EXPIRED、INVITATION_REJECTED”枚举值
POST /api/atlas/v2/groups/{groupId}/users
Updated
  • 响应属性“/invitationExpiresAt”变为可为 null
  • 响应属性“/invitationExpiresAt”变为可选
  • 已将 'INVITATION_EXPIRED, INVITATION_REJECTED' 映射键添加到响应状态 '201' 的响应鉴别器
  • 在“/orgMembershipStatus”响应属性中添加了新的“INVITATION_EXPIRED、INVITATION_REJECTED”枚举值
  • 在“orgMembershipStatus”响应属性中添加了新的“INVITATION_EXPIRED、INVITATION_REJECTED”枚举值
GET /api/atlas/v2/groups/{groupId}/users/{userId}
Updated
  • 响应属性“/invitationExpiresAt”变为可为 null
  • 响应属性“/invitationExpiresAt”变为可选
  • 添加了新的可选“查询”请求参数“orgMembershipStatuses”
  • 已将 'INVITATION_EXPIRED, INVITATION_REJECTED' 映射键添加到响应状态 '200' 的响应鉴别器
  • 在“/orgMembershipStatus”响应属性中添加了新的“INVITATION_EXPIRED、INVITATION_REJECTED”枚举值
  • 在“orgMembershipStatus”响应属性中添加了新的“INVITATION_EXPIRED、INVITATION_REJECTED”枚举值
POST /api/atlas/v2/groups/{groupId}/users/{userId}:addRole
Updated
  • 响应属性“/invitationExpiresAt”变为可为 null
  • 响应属性“/invitationExpiresAt”变为可选
  • 已将 'INVITATION_EXPIRED, INVITATION_REJECTED' 映射键添加到响应状态 '200' 的响应鉴别器
  • 在“/orgMembershipStatus”响应属性中添加了新的“INVITATION_EXPIRED、INVITATION_REJECTED”枚举值
  • 在“orgMembershipStatus”响应属性中添加了新的“INVITATION_EXPIRED、INVITATION_REJECTED”枚举值
POST /api/atlas/v2/groups/{groupId}/users/{userId}:removeRole
Updated
  • 响应属性“/invitationExpiresAt”变为可为 null
  • 响应属性“/invitationExpiresAt”变为可选
  • 已将 'INVITATION_EXPIRED, INVITATION_REJECTED' 映射键添加到响应状态 '200' 的响应鉴别器
  • 在“/orgMembershipStatus”响应属性中添加了新的“INVITATION_EXPIRED、INVITATION_REJECTED”枚举值
  • 在“orgMembershipStatus”响应属性中添加了新的“INVITATION_EXPIRED、INVITATION_REJECTED”枚举值
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 将新的 'CREDIT_AWS_ACCOUNT_ID_MODIFIED、CREDIT_AWS_LICENSE_ARN_MODIFIED'枚举值添加到 'results/items/oneOf[subschema #6: 计费 事件]/eventTypeName' 响应属性
  • 在“results/items/oneOf[subschema #8: 组织事件]/eventTypeName”响应属性中添加了新的“ORG_WAVE_ASSIGNMENT_MODE_ENV_TAG_MAPPING、ORG_WAVE_ASSIGNMENT_MODE_MANUAL”枚举值
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 将新的 'CREDIT_AWS_ACCOUNT_ID_MODIFIED、CREDIT_AWS_LICENSE_ARN_MODIFIED'枚举值添加到 '/oneOf[subschema #6: 计费 事件]/eventTypeName' 响应属性
  • 在 '/oneOf[subschema #8: Organization Events]/eventTypeName' 响应属性中添加了新的 'ORG_WAVE_ASSIGNMENT_MODE_ENV_TAG_MAPPING、ORG_WAVE_ASSIGNMENT_MODE_MANUAL'枚举值
GET /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users
Updated
  • “查询”请求参数“orgMembershipStatus”已弃用，且未提供取消日期
  • 响应属性“results/items/invitationExpiresAt”变为可为 null
  • 响应属性“results/items/invitationExpiresAt”变为可选
  • 添加了新的可选“查询”请求参数“orgMembershipStatuses”
  • 添加了 'INVITATION_EXPIRED, INVITATION_REJECTED' 鉴别器映射键到 'results/items/' 响应属性
  • 在“results/items/orgMembershipStatus”响应属性中添加了新的“INVITATION_EXPIRED、INVITATION_REJECTED”枚举值
POST /api/atlas/v2/orgs/{orgId}/teams/{teamId}:addUser
Updated
  • 响应属性“/invitationExpiresAt”变为可为 null
  • 响应属性“/invitationExpiresAt”变为可选
  • 已将 'INVITATION_REJECTED, INVITATION_EXPIRED' 映射键添加到响应状态 '200' 的响应鉴别器
  • 在“/orgMembershipStatus”响应属性中添加了新的“INVITATION_EXPIRED、INVITATION_REJECTED”枚举值
  • 在“orgMembershipStatus”响应属性中添加了新的“INVITATION_EXPIRED、INVITATION_REJECTED”枚举值
POST /api/atlas/v2/orgs/{orgId}/teams/{teamId}:removeUser
Updated
  • 响应属性“/invitationExpiresAt”变为可为 null
  • 响应属性“/invitationExpiresAt”变为可选
  • 已将 'INVITATION_EXPIRED, INVITATION_REJECTED' 映射键添加到响应状态 '200' 的响应鉴别器
  • 在“/orgMembershipStatus”响应属性中添加了新的“INVITATION_EXPIRED、INVITATION_REJECTED”枚举值
  • 在“orgMembershipStatus”响应属性中添加了新的“INVITATION_EXPIRED、INVITATION_REJECTED”枚举值
GET /api/atlas/v2/orgs/{orgId}/users
Updated
  • “查询”请求参数“orgMembershipStatus”已弃用，且未提供取消日期
  • 响应属性“results/items/invitationExpiresAt”变为可为 null
  • 响应属性“results/items/invitationExpiresAt”变为可选
  • 添加了新的可选“查询”请求参数“orgMembershipStatuses”
  • 添加了 'INVITATION_EXPIRED, INVITATION_REJECTED' 鉴别器映射键到 'results/items/' 响应属性
  • 在“results/items/orgMembershipStatus”响应属性中添加了新的“INVITATION_EXPIRED、INVITATION_REJECTED”枚举值
POST /api/atlas/v2/orgs/{orgId}/users
Updated
  • 响应属性“/invitationExpiresAt”变为可为 null
  • 响应属性“/invitationExpiresAt”变为可选
  • 已将 'INVITATION_EXPIRED, INVITATION_REJECTED' 映射键添加到响应状态 '201' 的响应鉴别器
  • 在“/orgMembershipStatus”响应属性中添加了新的“INVITATION_EXPIRED、INVITATION_REJECTED”枚举值
  • 在“orgMembershipStatus”响应属性中添加了新的“INVITATION_EXPIRED、INVITATION_REJECTED”枚举值
GET /api/atlas/v2/orgs/{orgId}/users/{userId}
Updated
  • 响应属性“/invitationExpiresAt”变为可为 null
  • 响应属性“/invitationExpiresAt”变为可选
  • 添加了新的可选“查询”请求参数“orgMembershipStatuses”
  • 已将 'INVITATION_EXPIRED, INVITATION_REJECTED' 映射键添加到响应状态 '200' 的响应鉴别器
  • 在“/orgMembershipStatus”响应属性中添加了新的“INVITATION_EXPIRED、INVITATION_REJECTED”枚举值
  • 在“orgMembershipStatus”响应属性中添加了新的“INVITATION_EXPIRED、INVITATION_REJECTED”枚举值
PATCH /api/atlas/v2/orgs/{orgId}/users/{userId}
Updated
  • 响应属性“/invitationExpiresAt”变为可为 null
  • 响应属性“/invitationExpiresAt”变为可选
  • 已将 'INVITATION_EXPIRED, INVITATION_REJECTED' 映射键添加到响应状态 '200' 的响应鉴别器
  • 在“/orgMembershipStatus”响应属性中添加了新的“INVITATION_EXPIRED、INVITATION_REJECTED”枚举值
  • 在“orgMembershipStatus”响应属性中添加了新的“INVITATION_EXPIRED、INVITATION_REJECTED”枚举值
POST /api/atlas/v2/orgs/{orgId}/users/{userId}:addRole
Updated
  • 响应属性“/invitationExpiresAt”变为可为 null
  • 响应属性“/invitationExpiresAt”变为可选
  • 已将 'INVITATION_EXPIRED, INVITATION_REJECTED' 映射键添加到响应状态 '200' 的响应鉴别器
  • 在“/orgMembershipStatus”响应属性中添加了新的“INVITATION_EXPIRED、INVITATION_REJECTED”枚举值
  • 在“orgMembershipStatus”响应属性中添加了新的“INVITATION_EXPIRED、INVITATION_REJECTED”枚举值
POST /api/atlas/v2/orgs/{orgId}/users/{userId}:removeRole
Updated
  • 响应属性“/invitationExpiresAt”变为可为 null
  • 响应属性“/invitationExpiresAt”变为可选
  • 已将 'INVITATION_EXPIRED, INVITATION_REJECTED' 映射键添加到响应状态 '200' 的响应鉴别器
  • 在“/orgMembershipStatus”响应属性中添加了新的“INVITATION_EXPIRED、INVITATION_REJECTED”枚举值
  • 在“orgMembershipStatus”响应属性中添加了新的“INVITATION_EXPIRED、INVITATION_REJECTED”枚举值

2026 年 4 月 29 日发布

GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 在“results/items/oneOf[subschema #1: Any other 事件]/eventTypeName/oneOf[subschema #4: 集群 Connection Atlas 审核 Types]/”响应属性中添加了新的“CLUSTER_CONNECTION_FIND_DOCUMENTS”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 在“/oneOf[subschema #1: Any other 事件]/eventTypeName/oneOf[subschema #4: 集群 Connection Atlas 审核 Types]/”响应属性中添加了新的“CLUSTER_CONNECTION_FIND_DOCUMENTS”枚举值
GET /api/atlas/v2/groups/{groupId}/logIntegrations
Updated
  • 在响应中添加了可选属性“results/items/oneOf[subschema #1: S3 日志 Export Integration Response]/useLegacyPathStructure”
帖子 /api/atlas/v2/groups/{groupId}/logIntegrations
Updated
  • 在响应中添加了可选属性“/oneOf[subschema #1: S3 日志导出集成响应]/useLegacyPathStructure”
  • 添加了新的可选请求属性“/oneOf[subschema #1: S3 日志 Export Integration Request]/useLegacyPathStructure”
GET /api/atlas/v2/groups/{groupId}/logIntegrations/{id}
Updated
  • 在响应中添加了可选属性“/oneOf[subschema #1: S3 日志导出集成响应]/useLegacyPathStructure”
PUT /api/atlas/v2/groups/{groupId}/logIntegrations/{id}
Updated
  • 在响应中添加了可选属性“/oneOf[subschema #1: S3 日志导出集成响应]/useLegacyPathStructure”
  • 添加了新的可选请求属性“/oneOf[subschema #1: S3 日志 Export Integration Request]/useLegacyPathStructure”

2026 年 4 月 28 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在响应中添加了可选属性“results/items/oneOf[subschema #17: Stream Processor Metric Alert Configuration]/metricThreshold”
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在响应中添加了可选属性“/oneOf[subschema #17：流处理器指标警报配置]/metricThreshold”
  • 添加了新的可选请求属性“/oneOf[subschema #17：流处理器指标警报配置]/metricThreshold”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在响应中添加了可选属性“/oneOf[subschema #17：流处理器指标警报配置]/metricThreshold”
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在响应中添加了可选属性“/oneOf[subschema #17：流处理器指标警报配置]/metricThreshold”
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在响应中添加了可选属性“/oneOf[subschema #17：流处理器指标警报配置]/metricThreshold”
  • 添加了新的可选请求属性“/oneOf[subschema #17：流处理器指标警报配置]/metricThreshold”
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 在响应中添加了可选属性“results/items/oneOf[subschema #17: Stream Processor Metric Alert Configuration]/metricThreshold”

2026 年 4 月 20 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“SEARCH_PROCESS_THROTTLING”鉴别器映射键添加到“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性
  • 将“#/components/schemas/SearchProcessThrotdlingRawMetricThresholdView”添加到“results/items/oneOf[subschema #9: 托管 指标 警报 Configuration]/指标Threshold”响应属性“oneOf”列表中
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“SEARCH_PROCESS_THROTTLING”鉴别器映射键添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性
  • 将“#/components/schemas/SearchProcessThrotdlingRawMetricThresholdView”添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性“oneOf”列表
  • 将“SEARCH_PROCESS_THROTTLING”鉴别器映射键添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性
  • 将“#/components/schemas/SearchProcessThrotdlingRawMetricThresholdView”添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“SEARCH_PROCESS_THROTTLING”鉴别器映射键添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性
  • 将“#/components/schemas/SearchProcessThrotdlingRawMetricThresholdView”添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性“oneOf”列表中
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“SEARCH_PROCESS_THROTTLING”鉴别器映射键添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性
  • 将“#/components/schemas/SearchProcessThrotdlingRawMetricThresholdView”添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性“oneOf”列表中
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“SEARCH_PROCESS_THROTTLING”鉴别器映射键添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性
  • 将“#/components/schemas/SearchProcessThrotdlingRawMetricThresholdView”添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性“oneOf”列表
  • 将“SEARCH_PROCESS_THROTTLING”鉴别器映射键添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性
  • 将“#/components/schemas/SearchProcessThrotdlingRawMetricThresholdView”添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 将“SEARCH_PROCESS_THROTTLING”鉴别器映射键添加到“results/items/oneOf[subschema #4: 托管 指标 警报s]/”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 将“SEARCH_PROCESS_THROTTLING”鉴别器映射键添加到“results/items/oneOf[subschema #4: 托管 指标 警报s]/”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“SEARCH_PROCESS_THROTTLING”鉴别器映射键添加到“/oneOf[subschema #4: 主机指标警报]/”响应属性
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“SEARCH_PROCESS_THROTTLING”鉴别器映射键添加到“/oneOf[subschema #4: 主机指标警报]/”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 将“SEARCH_PROCESS_THROTTLING”鉴别器映射键添加到“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性
  • 将“#/components/schemas/SearchProcessThrotdlingRawMetricThresholdView”添加到“results/items/oneOf[subschema #9: 托管 指标 警报 Configuration]/指标Threshold”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将“SEARCH_PROCESS_THROTTLING”鉴别器映射键添加到“results/items/oneOf[subschema #14: Host Metric Events]/”响应属性
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 将“SEARCH_PROCESS_THROTTLING”鉴别器映射键添加到“/oneOf[subschema #14: 托管 Metric 事件]/”响应属性

2026 年 4 月 16 日发布

POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor
Updated
  • 在响应中添加了可选属性“层级”
  • 添加了新的可选请求属性“层级”

2026 年 4 月 15 日发布

GET /api/atlas/v2/alertConfigs/matchers/fieldNames
Updated
  • 将新的“ATLAS_NODE_TYPE”枚举值添加到“/items/oneOf[subschema #3: 托管匹配器字段]/”响应属性
GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将新的“ATLAS_NODE_TYPE”枚举值添加到“results/items/oneOf[subschema #8: Host Alert Configuration]/matchers/items/fieldName”响应属性
  • 将新的“ATLAS_NODE_TYPE”枚举值添加到“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/matchers/items/fieldName”响应属性
  • 在“results/items/oneOf[subschema #1: Any other 警报配置]/eventTypeName/oneOf[subschema #13: 自动伸缩 Atlas 审核类型]/”响应属性中添加了新的“COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_ANALYTICS、COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_BASE”枚举值
  • 在“results/items/oneOf[subschema #4: 计费阈值警报配置]/eventTypeName”响应属性中添加了新的“DAILY_BILLING_CHANGE_OVER_THRESHOLD”、“MONTHLY_BILLING_CHANGE_OVER_THRESHOLD”和“WEEKLY_BILLING_CHANGE_OVER_THRESHOLD”枚举值
  • 将新的“FTS_INDEX_CLEANED_UP”枚举值添加到“results/items/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #4: FTS Index Atlas 审核 Types]/”响应属性
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将新的“ATLAS_NODE_TYPE”枚举值添加到“/oneOf[subschema #8: Host Alert Configuration]/matchers/items/fieldName”响应属性
  • 将新的“ATLAS_NODE_TYPE”枚举值添加到“/oneOf[subschema #9: 托管指标警报 Configuration]/matchers/items/fieldName”响应属性
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #13: 自动伸缩 Atlas 审核 Types]/”响应属性中添加了新的“COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_ANALYTICS、COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_BASE”枚举值
  • 在“/oneOf[subschema #4: Billing Threshold Alert Configuration]/eventTypeName”响应属性中添加了新的“DAILY_BILLING_CHANGE_OVER_THRESHOLD”、“MONTHLY_BILLING_CHANGE_OVER_THRESHOLD”和“WEEKLY_BILLING_CHANGE_OVER_THRESHOLD”枚举值
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #4: FTS Index Audit Types]/”响应属性中添加了新的“FTS_INDEX_CLEANED_UP”枚举值
  • 已将新的“ATLAS_NODE_TYPE”枚举值添加到请求属性“/oneOf[subschema #8: Host 警报配置]/matchers/items/fieldName”
  • 已将新的“ATLAS_NODE_TYPE”枚举值添加到请求属性“/oneOf[subschema #9: 托管指标警报 Configuration]/matchers/items/fieldName”
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #13: Auto Scaling Audit Types]/' 中添加了新的 'COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_ANALYTICS、COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_BASE'枚举值
  • 已将新的“DAILY_BILLING_CHANGE_OVER_THRESHOLD”、“MONTHLY_BILLING_CHANGE_OVER_THRESHOLD”和“WEEKLY_BILLING_CHANGE_OVER_THRESHOLD”枚举值添加到请求属性“/oneOf[subschema #4: Billing Threshold Alert Configuration]/eventTypeName”
  • 已将新的“FTS_INDEX_CLEANED_UP”枚举值添加到请求属性“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #4: Full Text Search 索引 Audit Types]/”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将新的“ATLAS_NODE_TYPE”枚举值添加到“/oneOf[subschema #8: Host Alert Configuration]/matchers/items/fieldName”响应属性
  • 将新的“ATLAS_NODE_TYPE”枚举值添加到“/oneOf[subschema #9: 托管指标警报 Configuration]/matchers/items/fieldName”响应属性
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #13: 自动伸缩 Atlas 审核 Types]/”响应属性中添加了新的“COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_ANALYTICS、COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_BASE”枚举值
  • 在“/oneOf[subschema #4: Billing Threshold Alert Configuration]/eventTypeName”响应属性中添加了新的“DAILY_BILLING_CHANGE_OVER_THRESHOLD”、“MONTHLY_BILLING_CHANGE_OVER_THRESHOLD”和“WEEKLY_BILLING_CHANGE_OVER_THRESHOLD”枚举值
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #4: FTS Index Audit Types]/”响应属性中添加了新的“FTS_INDEX_CLEANED_UP”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将新的“ATLAS_NODE_TYPE”枚举值添加到“/oneOf[subschema #8: Host Alert Configuration]/matchers/items/fieldName”响应属性
  • 将新的“ATLAS_NODE_TYPE”枚举值添加到“/oneOf[subschema #9: 托管指标警报 Configuration]/matchers/items/fieldName”响应属性
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #13: 自动伸缩 Atlas 审核 Types]/”响应属性中添加了新的“COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_ANALYTICS、COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_BASE”枚举值
  • 在“/oneOf[subschema #4: Billing Threshold Alert Configuration]/eventTypeName”响应属性中添加了新的“DAILY_BILLING_CHANGE_OVER_THRESHOLD”、“MONTHLY_BILLING_CHANGE_OVER_THRESHOLD”和“WEEKLY_BILLING_CHANGE_OVER_THRESHOLD”枚举值
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #4: FTS Index Audit Types]/”响应属性中添加了新的“FTS_INDEX_CLEANED_UP”枚举值
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将新的“ATLAS_NODE_TYPE”枚举值添加到“/oneOf[subschema #8: Host Alert Configuration]/matchers/items/fieldName”响应属性
  • 将新的“ATLAS_NODE_TYPE”枚举值添加到“/oneOf[subschema #9: 托管指标警报 Configuration]/matchers/items/fieldName”响应属性
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #13: 自动伸缩 Atlas 审核 Types]/”响应属性中添加了新的“COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_ANALYTICS、COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_BASE”枚举值
  • 在“/oneOf[subschema #4: Billing Threshold Alert Configuration]/eventTypeName”响应属性中添加了新的“DAILY_BILLING_CHANGE_OVER_THRESHOLD”、“MONTHLY_BILLING_CHANGE_OVER_THRESHOLD”和“WEEKLY_BILLING_CHANGE_OVER_THRESHOLD”枚举值
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #4: FTS Index Audit Types]/”响应属性中添加了新的“FTS_INDEX_CLEANED_UP”枚举值
  • 已将新的“ATLAS_NODE_TYPE”枚举值添加到请求属性“/oneOf[subschema #8: Host 警报配置]/matchers/items/fieldName”
  • 已将新的“ATLAS_NODE_TYPE”枚举值添加到请求属性“/oneOf[subschema #9: 托管指标警报 Configuration]/matchers/items/fieldName”
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #13: Auto Scaling Audit Types]/' 中添加了新的 'COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_ANALYTICS、COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_BASE'枚举值
  • 已将新的“DAILY_BILLING_CHANGE_OVER_THRESHOLD”、“MONTHLY_BILLING_CHANGE_OVER_THRESHOLD”和“WEEKLY_BILLING_CHANGE_OVER_THRESHOLD”枚举值添加到请求属性“/oneOf[subschema #4: Billing Threshold Alert Configuration]/eventTypeName”
  • 已将新的“FTS_INDEX_CLEANED_UP”枚举值添加到请求属性“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #4: Full Text Search 索引 Audit Types]/”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 在“results/items/oneOf[subschema #7: Any other 警报]/eventTypeName/oneOf[subschema #16: 自动伸缩 Atlas 审核 Types]/”响应属性中添加了新的“COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_ANALYTICS、COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_BASE”枚举值
  • 在“results/items/oneOf[subschema #7: Any other 警报]/eventTypeName/oneOf[subschema #1: 计费 事件 Types]/”响应属性中添加了新的“DAILY_BILLING_CHANGE_OVER_THRESHOLD、MONTHLY_BILLING_CHANGE_OVER_THRESHOLD、WEEKLY_BILLING_CHANGE_OVER_THRESHOLD”枚举值
  • 将新的“FTS_INDEX_CLEANED_UP”枚举值添加到“results/items/oneOf[subschema #7: Any other 警报]/eventTypeName/oneOf[subschema #4: FTS Index Atlas 审核 Types]/”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 在“results/items/oneOf[subschema #7: Any other 警报]/eventTypeName/oneOf[subschema #16: 自动伸缩 Atlas 审核 Types]/”响应属性中添加了新的“COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_ANALYTICS、COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_BASE”枚举值
  • 在“results/items/oneOf[subschema #7: Any other 警报]/eventTypeName/oneOf[subschema #1: 计费 事件 Types]/”响应属性中添加了新的“DAILY_BILLING_CHANGE_OVER_THRESHOLD、MONTHLY_BILLING_CHANGE_OVER_THRESHOLD、WEEKLY_BILLING_CHANGE_OVER_THRESHOLD”枚举值
  • 将新的“FTS_INDEX_CLEANED_UP”枚举值添加到“results/items/oneOf[subschema #7: Any other 警报]/eventTypeName/oneOf[subschema #4: FTS Index Atlas 审核 Types]/”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 在“/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #16: 自动伸缩 Audit Types]/”响应属性中添加了新的“COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_ANALYTICS、COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_BASE”枚举值
  • 在 '/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #1: Billing Event Types]/' 响应属性中添加了新的 'DAILY_BILLING_CHANGE_OVER_THRESHOLD、MONTHLY_BILLING_CHANGE_OVER_THRESHOLD、WEEKLY_BILLING_CHANGE_OVER_THRESHOLD'枚举值
  • 将新的“FTS_INDEX_CLEANED_UP”枚举值添加到“/oneOf[subschema #7: Any other 警报]/eventTypeName/oneOf[subschema #4: FTS Index Audit Types]/”响应属性
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 在“/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #16: 自动伸缩 Audit Types]/”响应属性中添加了新的“COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_ANALYTICS、COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_BASE”枚举值
  • 在 '/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #1: Billing Event Types]/' 响应属性中添加了新的 'DAILY_BILLING_CHANGE_OVER_THRESHOLD、MONTHLY_BILLING_CHANGE_OVER_THRESHOLD、WEEKLY_BILLING_CHANGE_OVER_THRESHOLD'枚举值
  • 将新的“FTS_INDEX_CLEANED_UP”枚举值添加到“/oneOf[subschema #7: Any other 警报]/eventTypeName/oneOf[subschema #4: FTS Index Audit Types]/”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 将新的“ATLAS_NODE_TYPE”枚举值添加到“results/items/oneOf[subschema #8: Host Alert Configuration]/matchers/items/fieldName”响应属性
  • 将新的“ATLAS_NODE_TYPE”枚举值添加到“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/matchers/items/fieldName”响应属性
  • 在“results/items/oneOf[subschema #1: Any other 警报配置]/eventTypeName/oneOf[subschema #13: 自动伸缩 Atlas 审核类型]/”响应属性中添加了新的“COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_ANALYTICS、COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_BASE”枚举值
  • 在“results/items/oneOf[subschema #4: 计费阈值警报配置]/eventTypeName”响应属性中添加了新的“DAILY_BILLING_CHANGE_OVER_THRESHOLD”、“MONTHLY_BILLING_CHANGE_OVER_THRESHOLD”和“WEEKLY_BILLING_CHANGE_OVER_THRESHOLD”枚举值
  • 将新的“FTS_INDEX_CLEANED_UP”枚举值添加到“results/items/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #4: FTS Index Atlas 审核 Types]/”响应属性
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots
Updated
  • 添加了新的可选“查询”请求参数“oplogInc”
  • 添加了新的可选“查询”请求参数“oplogTs”
  • 添加了新的可选“查询”请求参数“pointInTimeUtcSeconds”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/index
Updated
  • 添加了状态为“ 409 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将“subschema #37: 分片键 Advisor 事件类型”添加到“results/items/oneOf[subschema #1: 任何其他事件]/eventTypeName”响应属性“oneOf”列表中
  • Added the new 'CLUSTER_CREATED_VIA_ANIS, ENCRYPTION_AT_REST_PRIVATE_ENDPOINT_CREATED, ENCRYPTION_AT_REST_PRIVATE_ENDPOINT_DELETED, OTEL_METRIC_INTEGRATION_CONFIGURATION_UPDATED, OTEL_METRIC_INTEGRATION_DISABLED, OTEL_METRIC_INTEGRATION_ENABLED' 枚举 values to the 'results/items/oneOf[subschema #15: Atlas 项目 审核]/eventTypeName' response 属性
  • 在“results/items/oneOf[subschema #16: 自动伸缩 Audits]/eventTypeName”响应属性中添加了新的“COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_ANALYTICS、COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_BASE”枚举值
  • Added the new 'DAILY_BILLING_CHANGE_NORMAL, DAILY_BILLING_CHANGE_OVER_THRESHOLD, MONTHLY_BILLING_CHANGE_NORMAL, MONTHLY_BILLING_CHANGE_OVER_THRESHOLD, WEEKLY_BILLING_CHANGE_NORMAL, WEEKLY_BILLING_CHANGE_OVER_THRESHOLD' 枚举 values to the 'results/items/oneOf[subschema #8: 计费 事件]/eventTypeName' response 属性
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 将“subschema #37: Shard Key Advisor Event Types”添加到“/oneOf[subschema #1: Any other Events]/eventTypeName”响应属性“oneOf”列表中
  • Added the new 'CLUSTER_CREATED_VIA_ANIS, ENCRYPTION_AT_REST_PRIVATE_ENDPOINT_CREATED, ENCRYPTION_AT_REST_PRIVATE_ENDPOINT_DELETED, OTEL_METRIC_INTEGRATION_CONFIGURATION_UPDATED, OTEL_METRIC_INTEGRATION_DISABLED, OTEL_METRIC_INTEGRATION_ENABLED' 枚举 values to the '/oneOf[subschema #15: Atlas 项目 Atlas 审核]/eventTypeName' response 属性
  • 在 '/oneOf[subschema #16: 自动伸缩 Atlas 审核]/eventTypeName' 响应属性中添加了新的 'COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_ANALYTICS、COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_BASE'枚举值
  • 已将新的 'DAILY_BILLING_CHANGE_NORMAL、DAILY_BILLING_CHANGE_OVER_THRESHOLD、MONTHLY_BILLING_CHANGE_NORMAL、MONTHLY_BILLING_CHANGE_OVER_THRESHOLD、WEEKLY_BILLING_CHANGE_NORMAL、WEEKLY_BILLING_CHANGE_OVER_THRESHOLD' 枚举值添加到 '/oneOf[subschema #8: Billing Events]/eventTypeName' 响应属性
POST /api/atlas/v2/orgs/{orgId}/billing/costExplorer/usage
Updated
  • 在请求属性“services/items/”中添加了新的“Native Reranking”枚举值
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 将“subschema #6: AI Models 事件 Types”添加到“results/items/oneOf[subschema #1: Any other 事件]/eventTypeName”响应属性“oneOf”列表中
  • Added the new 'ORG_DAILY_BILLING_CHANGE_NORMAL, ORG_DAILY_BILLING_CHANGE_OVER_THRESHOLD, ORG_MONTHLY_BILLING_CHANGE_NORMAL, ORG_MONTHLY_BILLING_CHANGE_OVER_THRESHOLD, ORG_WEEKLY_BILLING_CHANGE_NORMAL, ORG_WEEKLY_BILLING_CHANGE_OVER_THRESHOLD, PROJECT_CREATED_VIA_ANIS' 枚举 values to the 'results/items/oneOf[subschema #8: 组织 事件]/eventTypeName' response 属性
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 将“subschema #6: AI Models 事件 Types”添加到“/oneOf[subschema #1: Any Other 事件]/eventTypeName”响应属性“oneOf”列表中
  • Added the new 'ORG_DAILY_BILLING_CHANGE_NORMAL, ORG_DAILY_BILLING_CHANGE_OVER_THRESHOLD, ORG_MONTHLY_BILLING_CHANGE_NORMAL, ORG_MONTHLY_BILLING_CHANGE_OVER_THRESHOLD, ORG_WEEKLY_BILLING_CHANGE_NORMAL, ORG_WEEKLY_BILLING_CHANGE_OVER_THRESHOLD, PROJECT_CREATED_VIA_ANIS' 枚举 values to the '/oneOf[subschema #8: 组织 事件]/eventTypeName' response 属性
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}/lineItems:search
Updated
  • 在请求属性“filters/skuServices/items/”中添加了新的“Native Reranking”枚举值

2026 年 4 月 03 日发布

PATCH /api/atlas/v2/groups/{groupId}
Updated
  • 添加了新的可选请求属性“withDefaultAlertsSettings”
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 在“results/items/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #11: Group Atlas 审核 Types]/”响应属性中添加了新的“GROUP_DEFAULT_ALERTS_SETTINGS_CHANGED”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 在“/oneOf[subschema #1: Any other 事件]/eventTypeName/oneOf[subschema #11: Group Atlas 审核 Types]/”响应属性中添加了新的“GROUP_DEFAULT_ALERTS_SETTINGS_CHANGED”枚举值

2026 年 3 月 30 日发布

GET / API/ Atlas/v2/groups/{groupId}/clusters/{clusterName}/queryShapeInsights/summaries
Updated
  • 在响应中添加了可选属性“summaries/items/cpuTime”
GET / API/ Atlas/v2/groups/{groupId}/clusters/{clusterName}/queryShapeInsights/{queryShapeHash}/details
Updated
  • 在响应中添加了可选属性“queryStats/cpuTime”
GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 将“GCPPubSub”鉴别器映射键添加到“results/items/connections/items/”响应属性
  • 将“#/components/schemas/StreamsGCPPubSubConnection”添加到响应的“results/items/connections/items/”响应属性“oneOf”列表中
  • 在“results/items/connections/items/type”响应属性中添加了新的“AzureBlobStorage, GCPPubSub”枚举值
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 将“GCPPubSub”鉴别器映射键添加到“connections/items/”请求属性
  • 将 '#/components/schemas/StreamsGCPPubSubConnection' 添加到 'connections/items/'请求属性'oneOf' 列表
  • 将“GCPPubSub”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/模式/StreamsGCPPubSubConnection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 在“connections/items/type”响应属性中添加了新的“AzureBlobStorage、GCPPubSub”枚举值
  • 在请求属性“connections/items/type”中添加了新的“AzureBlobStorage, GCPPubSub”枚举值
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 将“GCPPubSub”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/模式/StreamsGCPPubSubConnection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 在“connections/items/type”响应属性中添加了新的“AzureBlobStorage、GCPPubSub”枚举值
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 将“GCPPubSub”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/模式/StreamsGCPPubSubConnection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 在“connections/items/type”响应属性中添加了新的“AzureBlobStorage、GCPPubSub”枚举值
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 将“GCPPubSub”鉴别器映射键添加到“results/items/”响应属性
  • 将“#/components/schemas/StreamsGCPPubSubConnection”添加到响应的“results/items/”响应属性“oneOf”列表中
  • 在“results/items/type”响应属性中添加了新的“AzureBlobStorage, GCPPubSub”枚举值
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 将“GCPPubSub”映射键添加到请求鉴别器
  • 将 '#/components/schemas/StreamsGCPPubSubConnection' 添加到请求正文 'oneOf' 列表
  • 已将“GCPPubSub”映射键添加到响应状态“200”的响应鉴别器
  • 将“#/components/schemas/StreamsGCPPubSubConnection”添加到响应的响应正文“oneOf”列表中
  • 在 '/type' 响应属性中添加了新的 'AzureBlobStorage, GCPPubSub'枚举值
  • 在“类型”响应属性中添加了新的“AzureBlobStorage、GCPPubSub”枚举值
  • 已将新的“AzureBlobStorage, GCPPubSub”枚举值添加到请求属性“/type”
  • 已将新的“AzureBlobStorage、GCPPubSub”枚举值添加到请求属性“type”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 已将“GCPPubSub”映射键添加到响应状态“200”的响应鉴别器
  • 将“#/components/schemas/StreamsGCPPubSubConnection”添加到响应的响应正文“oneOf”列表中
  • 在 '/type' 响应属性中添加了新的 'AzureBlobStorage, GCPPubSub'枚举值
  • 在“类型”响应属性中添加了新的“AzureBlobStorage、GCPPubSub”枚举值
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 将“GCPPubSub”映射键添加到请求鉴别器
  • 将 '#/components/schemas/StreamsGCPPubSubConnection' 添加到请求正文 'oneOf' 列表
  • 已将“GCPPubSub”映射键添加到响应状态“200”的响应鉴别器
  • 将“#/components/schemas/StreamsGCPPubSubConnection”添加到响应的响应正文“oneOf”列表中
  • 在 '/type' 响应属性中添加了新的 'AzureBlobStorage, GCPPubSub'枚举值
  • 在“类型”响应属性中添加了新的“AzureBlobStorage、GCPPubSub”枚举值
  • 已将新的“AzureBlobStorage, GCPPubSub”枚举值添加到请求属性“/type”
  • 已将新的“AzureBlobStorage、GCPPubSub”枚举值添加到请求属性“type”
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
Updated
  • 将“GCPPubSub”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/模式/StreamsGCPPubSubConnection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 在“connections/items/type”响应属性中添加了新的“AzureBlobStorage、GCPPubSub”枚举值

2026 年 3 月 26 日发布

GET / API/ Atlas/v2/groups/{groupId}/clusters/{clusterName}/queryShapeInsights/summaries
Updated
  • 在响应中添加了可选属性“summaries/items/cpuNanos”
GET / API/ Atlas/v2/groups/{groupId}/clusters/{clusterName}/queryShapeInsights/{queryShapeHash}/details
Updated
  • 在响应中添加了可选属性“queryStats/cpuNanos”
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将“subschema #38: AI Models 事件 Types”添加到“results/items/oneOf[subschema #1: Any other 事件]/eventTypeName”响应属性“oneOf”列表中
  • 在“results/items/oneOf[subschema #15: Atlas 项目审核]/eventTypeName”响应属性中添加了新的“ENCRYPTION_AT_REST_KEY_ROTATION_STARTED、NODE_HIDDEN_BY_ADMIN、NODE_UNHIDDEN_BY_ADMIN”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 将“subschema #38: AI Models 事件 Types”添加到“/oneOf[subschema #1: Any Other 事件]/eventTypeName”响应属性“oneOf”列表中
  • 在“/oneOf[subschema #15: Atlas Project Audits]/eventTypeName”响应属性中添加了新的“ENCRYPTION_AT_REST_KEY_ROTATION_STARTED、NODE_HIDDEN_BY_ADMIN、NODE_UNHIDDEN_BY_ADMIN”枚举值
POST /api/atlas/v2/groups/{groupId}/privateEndpoint/endpointService
Updated
  • 添加了新的可选请求属性“supportedRemoteRegions”
PATCH /api/atlas/v2/groups/{groupId}/privateEndpoint/endpointService/{endpointServiceId}
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/settings
Updated
  • 在响应中添加了可选属性“isNativeRerankingEnabled”
PATCH /api/atlas/v2/groups/{groupId}/settings
Updated
  • 在响应中添加了可选属性“isNativeRerankingEnabled”
  • 添加了新的可选请求属性“isNativeRerankingEnabled”
GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 将“AzureBlobStorage”鉴别器映射键添加到“results/items/connections/items/”响应属性
  • 将“#/components/schemas/StreamsAzureBlobStorageConnection”添加到响应的“results/items/connections/items/”响应属性“oneOf”列表中
  • 在响应中添加了可选属性“results/items/connections/items/id”
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 将“AzureBlobStorage”鉴别器映射键添加到“connections/items/”请求属性
  • 将“#/components/schemas/StreamsAzureBlobStorageConnection”添加到“connections/items/”请求属性“oneOf”列表
  • 将“AzureBlobStorage”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/schemas/StreamsAzureBlobStorageConnection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 在响应中添加了可选属性“connections/items/id”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 将“AzureBlobStorage”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/schemas/StreamsAzureBlobStorageConnection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 在响应中添加了可选属性“connections/items/id”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 将“AzureBlobStorage”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/schemas/StreamsAzureBlobStorageConnection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 在响应中添加了可选属性“connections/items/id”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 将“AzureBlobStorage”鉴别器映射键添加到“results/items/”响应属性
  • 将“#/components/schemas/StreamsAzureBlobStorageConnection”添加到响应的“results/items/”响应属性“oneOf”列表中
  • 在响应中添加了可选属性“results/items/ ID ”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 将“AzureBlobStorage”映射键添加到请求鉴别器
  • 将“#/components/schemas/StreamsAzureBlobStorageConnection”添加到请求正文“oneOf”列表
  • 已将“AzureBlobStorage”映射键添加到响应状态“200”的响应鉴别器
  • 将“#/components/schemas/StreamsAzureBlobStorageConnection”添加到响应的响应正文“oneOf”列表中
  • 在响应中添加了可选属性“/id, id”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 已将“AzureBlobStorage”映射键添加到响应状态“200”的响应鉴别器
  • 将“#/components/schemas/StreamsAzureBlobStorageConnection”添加到响应的响应正文“oneOf”列表中
  • 在响应中添加了可选属性“/id, id”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 将“AzureBlobStorage”映射键添加到请求鉴别器
  • 将“#/components/schemas/StreamsAzureBlobStorageConnection”添加到请求正文“oneOf”列表
  • 已将“AzureBlobStorage”映射键添加到响应状态“200”的响应鉴别器
  • 将“#/components/schemas/StreamsAzureBlobStorageConnection”添加到响应的响应正文“oneOf”列表中
  • 在响应中添加了可选属性“/id, id”
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
Updated
  • 将“AzureBlobStorage”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/schemas/StreamsAzureBlobStorageConnection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 在响应中添加了可选属性“connections/items/id”
POST /api/atlas/v2/groups/{groupId}:migrate
Updated
  • 添加了状态为“ 402 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 将新的“PAYMENT_DUE_DATE_EXTENDED”枚举值添加到“results/items/oneOf[subschema #6: Billing Events]/eventTypeName”响应属性
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 将新的 'PAYMENT_DUE_DATE_EXTENDED'枚举值添加到 '/oneOf[subschema #6: 计费 事件]/eventTypeName' 响应属性

2026 年 3 月 23 日发布

GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 在“results/items/oneOf[subschema #1: Any other 事件]/eventTypeName/oneOf[subschema #22: Private Link Atlas 审核 Types]/”响应属性中添加了新的“INTERFACE_ENDPOINT_RETRIED”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 在“/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #22: Private Link Atlas 审核 Types]/”响应属性中添加了新的“INTERFACE_ENDPOINT_RETRIED”枚举值

2026 年 3 月 18 日发布

GET /api/atlas/v2/groups/{groupId}/settings
Updated
  • 在响应中添加了可选属性“isClusterAiAssistantEnabled”
PATCH /api/atlas/v2/groups/{groupId}/settings
Updated
  • 在响应中添加了可选属性“isClusterAiAssistantEnabled”
  • 添加了新的可选请求属性“isClusterAiAssistantEnabled”

2026 年 3 月 10 日发布

DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 在响应中添加了可选属性“autoCopySettingsEnabled”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 在响应中添加了可选属性“autoCopySettingsEnabled”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 在响应中添加了可选属性“autoCopySettingsEnabled”
  • 添加了新的可选请求属性“autoCopySettingsEnabled”
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 在“results/items/oneOf[subschema #1: 任何其他事件]/eventTypeName/oneOf[subschema #4: 合作事件类型]/”响应属性中添加了新的“VERCEL_INVOICE_OVERDUE”枚举值
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 在“/oneOf[subschema #1: Any other 事件]/eventTypeName/oneOf[subschema #4: 合作 事件 Types]/”响应属性中添加了新的“VERCEL_INVOICE_OVERDUE”枚举值

2026 年 3 月 06 日发布

帖子 /api/atlas/v2/groups/{groupId}/logIntegrations
Updated
  • 在请求属性“/oneOf[subschema #1: S3 Log Export Integration Request]/logTypes/items/”中添加了新的“MONGOD、MONGOD_AUDIT、MNGOS、MNGOS_AUDIT”枚举值
  • 在请求属性“/oneOf[subschema #2: DataDog 日志 Export Integration Request]/logTypes/items/”中添加了新的“MONGOD、MONGOD_AUDIT、MNGOS、MNGOS_AUDIT”枚举值
  • 在请求属性“/oneOf[subschema #3: GCS Log Export Integration Request]/logTypes/items/”中添加了新的“MONGOD、MONGOD_AUDIT、MNGOS、MNGOS_AUDIT”枚举值
  • 在请求属性“/oneOf[subschema #4: OTel Log Export Integration Request]/logTypes/items/”中添加了新的“MONGOD、MONGOD_AUDIT、MNGOS、MNGOS_AUDIT”枚举值
  • 在请求属性“/oneOf[subschema #5: Splunk Log Export Integration Request]/logTypes/items/”中添加了新的“MONGOD、MONGOD_AUDIT、MNGOS、MNGOS_AUDIT”枚举值
  • 在请求属性“/oneOf[subschema #6: Azure Log Export Integration Request]/logTypes/items/”中添加了新的“MONGOD、MONGOD_AUDIT、MNGOS、MNGOS_AUDIT”枚举值
  • 在请求属性“logTypes/items/”中添加了新的“MONGOD、MONGOD_AUDIT、MONGOS、MNGOS_AUDIT”枚举值
PUT /api/atlas/v2/groups/{groupId}/logIntegrations/{id}
Updated
  • 在请求属性“/oneOf[subschema #1: S3 Log Export Integration Request]/logTypes/items/”中添加了新的“MONGOD、MONGOD_AUDIT、MNGOS、MNGOS_AUDIT”枚举值
  • 在请求属性“/oneOf[subschema #2: DataDog 日志 Export Integration Request]/logTypes/items/”中添加了新的“MONGOD、MONGOD_AUDIT、MNGOS、MNGOS_AUDIT”枚举值
  • 在请求属性“/oneOf[subschema #3: GCS Log Export Integration Request]/logTypes/items/”中添加了新的“MONGOD、MONGOD_AUDIT、MNGOS、MNGOS_AUDIT”枚举值
  • 在请求属性“/oneOf[subschema #4: OTel Log Export Integration Request]/logTypes/items/”中添加了新的“MONGOD、MONGOD_AUDIT、MNGOS、MNGOS_AUDIT”枚举值
  • 在请求属性“/oneOf[subschema #5: Splunk Log Export Integration Request]/logTypes/items/”中添加了新的“MONGOD、MONGOD_AUDIT、MNGOS、MNGOS_AUDIT”枚举值
  • 在请求属性“/oneOf[subschema #6: Azure Log Export Integration Request]/logTypes/items/”中添加了新的“MONGOD、MONGOD_AUDIT、MNGOS、MNGOS_AUDIT”枚举值
  • 在请求属性“logTypes/items/”中添加了新的“MONGOD、MONGOD_AUDIT、MONGOS、MNGOS_AUDIT”枚举值

2026 年 3 月 05 日发布

GET /api/atlas/v2
Updated
  • 响应属性“apiKey/accessList, apiKey/roles”变为必填项
GET /api/atlas/v2/clusters
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/eventTypes
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs
Updated
  • 响应属性“results, results/items/roleMappings/items/roleAssignments”变为必填项
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
Updated
  • 响应属性“roleMappings/items/roleAssignments”变为必填项
PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
Updated
  • 响应属性“roleMappings/items/roleAssignments”变为必填项
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings
Updated
  • 响应属性“results, results/items/roleAssignments”变为必填项
POST /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings
Updated
  • 响应属性“roleAssignments”变为必需
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings/{id}
Updated
  • 响应属性“roleAssignments”变为必需
PUT /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings/{id}
Updated
  • 响应属性“roleAssignments”变为必需
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders
Updated
  • 响应属性 'results, results/items/associatedOrgs/items/roleMappings/items/roleAssignments, results/items/oneOf[subschema #1: SAML]/同类Orgs/items/roleMappings/items/roleAssignments, results/items/oneOf [subschema #2: OIDC WORKFORCE]/同类Orgs/items/roleMappings/items/roleAssignments, results/items/oneOf[subschema #3: OIDC 工作负载]/同类Orgs/items/roleMappings/items/roleAssignments' 变为必填项
POST /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders
Updated
  • 响应属性 '/oneOf[subschema #1: OIDC WORKFORCE]/关联Orgs/items/roleMappings/items/roleAssignments, /oneOf[subschema #2: OIDC 工作负载]/ associatedOrgs/items/roleMappings/items/roleAssignments, associatedOrgs/items/roleMappings/items/roleAssignments' 变为必填项
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 响应属性 '/oneOf[subschema #1: SAML]/关联Orgs/items/roleMappings/items/roleAssignments, /oneOf[subschema #2: OIDC WORKFORCE]/关联Orgs/items/roleMappings/items/roleAssignments, / oneOf[subschema #3: OIDC 工作负载]/关联Orgs/items/roleMappings/items/roleAssignments, associatedOrgs/items/roleMappings/items/roleAssignments' 变为必填项
PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 响应属性 '/oneOf[subschema #1: SAML]/关联Orgs/items/roleMappings/items/roleAssignments, /oneOf[subschema #2: OIDC WORKFORCE]/关联Orgs/items/roleMappings/items/roleAssignments, / oneOf[subschema #3: OIDC 工作负载]/关联Orgs/items/roleMappings/items/roleAssignments, associatedOrgs/items/roleMappings/items/roleAssignments' 变为必填项
GET /api/atlas/v2/groups
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/accessList
Updated
  • 响应属性“结果”变为必需
POST /api/atlas/v2/groups/{groupId}/accessList
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将新的“PROFILER_CONFIGURED_TOO_WIDELY”枚举值添加到“results/items/oneOf[subschema #1: Any other 警报 Configurations]/事件TypeName/oneOf[subschema #15: 托管 事件 Types]/”响应属性
  • 将新的“PROFILER_CONFIGURED_TOO_WIDELY”枚举值添加到“results/items/oneOf[subschema #8: 托管 警报 Configuration]/eventTypeName”响应属性
  • 响应属性“结果”变为必需
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/事件TypeName/oneOf[subschema #15: 托管 事件 Types]/”响应属性中添加了新的“PROFILER_CONFIGURED_TOO_WIDELY”枚举值
  • 将新的“PROFILER_CONFIGURED_TOO_WIDELY”枚举值添加到“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”响应属性
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #15: Host Event Types]/' 中添加了新的 'PROFILER_CONFIGURED_TOO_WIDELY'枚举值
  • 在请求属性“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”中添加了新的“PROFILER_CONFIGURED_TOO_WIDELY”枚举值
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/事件TypeName/oneOf[subschema #15: 托管 事件 Types]/”响应属性中添加了新的“PROFILER_CONFIGURED_TOO_WIDELY”枚举值
  • 将新的“PROFILER_CONFIGURED_TOO_WIDELY”枚举值添加到“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”响应属性
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/事件TypeName/oneOf[subschema #15: 托管 事件 Types]/”响应属性中添加了新的“PROFILER_CONFIGURED_TOO_WIDELY”枚举值
  • 将新的“PROFILER_CONFIGURED_TOO_WIDELY”枚举值添加到“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”响应属性
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/事件TypeName/oneOf[subschema #15: 托管 事件 Types]/”响应属性中添加了新的“PROFILER_CONFIGURED_TOO_WIDELY”枚举值
  • 将新的“PROFILER_CONFIGURED_TOO_WIDELY”枚举值添加到“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”响应属性
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #15: Host Event Types]/' 中添加了新的 'PROFILER_CONFIGURED_TOO_WIDELY'枚举值
  • 在请求属性“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”中添加了新的“PROFILER_CONFIGURED_TOO_WIDELY”枚举值
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 将新的“PROFILER_CONFIGURED_TOO_WIDELY”枚举值添加到“results/items/oneOf[subschema #3: Host Alerts]/eventTypeName”响应属性
  • 将新的“PROFILER_CONFIGURED_TOO_WIDELY”枚举值添加到“results/items/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName”响应属性
  • 将新的“PROFILER_CONFIGURED_TOO_WIDELY”枚举值添加到“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #19: Host Event Types]/”响应属性
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 将新的“PROFILER_CONFIGURED_TOO_WIDELY”枚举值添加到“results/items/oneOf[subschema #3: Host Alerts]/eventTypeName”响应属性
  • 将新的“PROFILER_CONFIGURED_TOO_WIDELY”枚举值添加到“results/items/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName”响应属性
  • 将新的“PROFILER_CONFIGURED_TOO_WIDELY”枚举值添加到“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #19: Host Event Types]/”响应属性
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将新的“PROFILER_CONFIGURED_TOO_WIDELY”枚举值添加到“/oneOf[subschema #3: 托管警报]/eventTypeName”响应属性
  • 将新的“PROFILER_CONFIGURED_TOO_WIDELY”枚举值添加到“/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName”响应属性
  • 将新的“PROFILER_CONFIGURED_TOO_WIDELY”枚举值添加到“/oneOf[subschema #7: Any other 警报]/eventTypeName/oneOf[subschema #19: 托管 事件 Types]/”响应属性
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将新的“PROFILER_CONFIGURED_TOO_WIDELY”枚举值添加到“/oneOf[subschema #3: 托管警报]/eventTypeName”响应属性
  • 将新的“PROFILER_CONFIGURED_TOO_WIDELY”枚举值添加到“/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName”响应属性
  • 将新的“PROFILER_CONFIGURED_TOO_WIDELY”枚举值添加到“/oneOf[subschema #7: Any other 警报]/eventTypeName/oneOf[subschema #19: 托管 事件 Types]/”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 将新的“PROFILER_CONFIGURED_TOO_WIDELY”枚举值添加到“results/items/oneOf[subschema #1: Any other 警报 Configurations]/事件TypeName/oneOf[subschema #15: 托管 事件 Types]/”响应属性
  • 将新的“PROFILER_CONFIGURED_TOO_WIDELY”枚举值添加到“results/items/oneOf[subschema #8: 托管 警报 Configuration]/eventTypeName”响应属性
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/apiKeys
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/backup/exportBuckets
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/ 备份/{cloudProvider}/privateEndpoints
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/cloudProviderAccess
Updated
  • 将“ATLAS_LOG_INTEGRATION”鉴别器映射键添加到“awsIamRoles/items/featureUsages/items/”响应属性
  • 将“ATLAS_LOG_INTEGRATION”鉴别器映射键添加到“azureServicePrincipals/items/featureUsages/items/”响应属性
  • 将“ATLAS_LOG_INTEGRATION”鉴别器映射键添加到“gcpServiceAccounts/items/featureUsages/items/”响应属性
  • 将新的“ATLAS_LOG_INTEGRATION”枚举值添加到“awsIamRoles/items/featureUsages/items/featureType”响应属性中
  • 在“azureServicePrincipals/items/featureUsages/items/featureType”响应属性中添加了新的“ATLAS_LOG_INTEGRATION”枚举值
  • 已将新的“ATLAS_LOG_INTEGRATION”枚举值添加到“gcpServiceAccounts/items/featureUsages/items/featureType”响应属性
POST /api/atlas/v2/groups/{groupId}/cloudProviderAccess
Updated
  • 将“ATLAS_LOG_INTEGRATION”鉴别器映射键添加到“/featureUsages/items/”请求属性
  • 将“ATLAS_LOG_INTEGRATION”鉴别器映射键添加到“/featureUsages/items/”请求属性
  • 将“ATLAS_LOG_INTEGRATION”鉴别器映射键添加到“/featureUsages/items/”请求属性
  • 将“ATLAS_LOG_INTEGRATION”鉴别器映射键添加到“/featureUsages/items/”响应属性
  • 将“ATLAS_LOG_INTEGRATION”鉴别器映射键添加到“/featureUsages/items/”响应属性
  • 将“ATLAS_LOG_INTEGRATION”鉴别器映射键添加到“/featureUsages/items/”响应属性
  • 将新的“ATLAS_LOG_INTEGRATION”枚举值添加到“/featureUsages/items/featureType”响应属性中
  • 已将新的“ATLAS_LOG_INTEGRATION”枚举值添加到请求属性“/featureUsages/items/featureType”
GET /api/atlas/v2/groups/{groupId}/cloudProviderAccess/{roleId}
Updated
  • 将“ATLAS_LOG_INTEGRATION”鉴别器映射键添加到“/featureUsages/items/”响应属性
  • 将“ATLAS_LOG_INTEGRATION”鉴别器映射键添加到“/featureUsages/items/”响应属性
  • 将“ATLAS_LOG_INTEGRATION”鉴别器映射键添加到“/featureUsages/items/”响应属性
  • 将新的“ATLAS_LOG_INTEGRATION”枚举值添加到“/featureUsages/items/featureType”响应属性中
PATCH /api/atlas/v2/groups/{groupId}/cloudProviderAccess/{roleId}
Updated
  • 将“ATLAS_LOG_INTEGRATION”鉴别器映射键添加到“/featureUsages/items/”响应属性
  • 将“ATLAS_LOG_INTEGRATION”鉴别器映射键添加到“/featureUsages/items/”响应属性
  • 将“ATLAS_LOG_INTEGRATION”鉴别器映射键添加到“/featureUsages/items/”响应属性
  • 将新的“ATLAS_LOG_INTEGRATION”枚举值添加到“/featureUsages/items/featureType”响应属性中
GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/clusters/provider/regions
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs
Updated
  • 响应属性“结果”变为必需
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 响应属性“policies、policy/items/policyItems”变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 响应属性“policies、policy/items/policyItems”变为必填项
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 响应属性“policies、policy/items/policyItems”变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/shardedClusters
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backupCheckpoints
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • 响应属性“pinnedNamespaces”变为必需
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • 响应属性“pinnedNamespaces”变为必需
PUT /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • 响应属性“pinnedNamespaces”变为必需
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/unpin
Updated
  • 响应属性“pinnedNamespaces”变为必需
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/queryShapes
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs
Updated
  • 响应属性“结果”变为必需
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs
Updated
  • 响应属性“结果”变为必需
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • 添加了新的可选请求属性“definition/oneOf[subschema #2: 向量搜索 索引 Definition]/nestedRoot”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • 添加了新的可选请求属性“definition/oneOf[subschema #2: 向量搜索 索引 Definition]/nestedRoot”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/{clusterView}/collStats/namespaces
Updated
  • 响应属性“rankedNamespaces”变为必填项
GET /api/atlas/v2/groups/{groupId}/containers
Updated
  • 响应属性“results, results/items/oneOf[subschema #2: GCP]/regions”成为必需
POST /api/atlas/v2/groups/{groupId}/containers
Updated
  • 响应属性'/oneOf[subschema #2: GCP]/regions' 变为必需
GET /api/atlas/v2/groups/{groupId}/containers/all
Updated
  • 响应属性“results, results/items/oneOf[subschema #2: GCP]/regions”成为必需
GET /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 响应属性'/oneOf[subschema #2: GCP]/regions' 变为必需
PATCH /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 响应属性'/oneOf[subschema #2: GCP]/regions' 变为必需
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 响应属性“/items/actions/items/resources”变为必填项
POST /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 响应属性“actions/items/resources”变为必填项
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 响应属性“actions/items/resources”变为必填项
PATCH /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 响应属性“actions/items/resources”变为必填项
GET /api/atlas/v2/groups/{groupId}/databaseUsers
Updated
  • 响应属性“结果、结果/项目/角色”成为必需
POST /api/atlas/v2/groups/{groupId}/databaseUsers
Updated
  • 响应属性“角色”变为必需
GET /api/atlas/v2/groups/{groupId}/databaseUsers/{databaseName}/{username}
Updated
  • 响应属性“角色”变为必需
PATCH /api/atlas/v2/groups/{groupId}/databaseUsers/{databaseName}/{username}
Updated
  • 响应属性“角色”变为必需
GET /api/atlas/v2/groups/{groupId}/databaseUsers/{username}/certs
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/dbAccessHistory/clusters/{clusterName}
Updated
  • 对于“查询”请求参数“end”，最小值已设立为“1199145600000.00”
  • 对于“查询”请求参数“start”，最小值已设立为“1199145600000.00”
GET /api/atlas/v2/groups/{groupId}/dbAccessHistory/processes/{hostname}
Updated
  • 对于“查询”请求参数“end”，最小值已设立为“1199145600000.00”
  • 对于“查询”请求参数“start”，最小值已设立为“1199145600000.00”
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 在“results/items/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #22: Private Link Atlas 审核 Types]/”响应属性中添加了新的“CROSS_REGION_SUPPORTED_REGION_MODIFIED”枚举值
  • 在“results/items/oneOf[subschema #13: 托管 事件]/eventTypeName”响应属性中添加了新的“HOST_MOGOT_RESTARTED、PROFILER_CONFIGURED_TOO_WIDELY”枚举值
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 在“/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #22: Private Link Atlas 审核 Types]/”响应属性中添加了新的“CROSS_REGION_SUPPORTED_REGION_MODIFIED”枚举值
  • 在“/oneOf[subschema #13: 托管 Events]/eventTypeName”响应属性中添加了新的“HOST_MOGOT_RESTARTED、PROFILER_CONFIGURED_TOO_WIDELY”枚举值
GET /api/atlas/v2/groups/{groupId}/flexClusters
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/restoreJobs
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/snapshots
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics
Updated
  • 响应属性“hardwareMetrics、indexMetrics、statusMetrics”成为必需
GET /api/atlas/v2/groups/{groupId}/integrations
Updated
  • 响应属性“结果”变为必需
POST /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 响应属性“结果”变为必需
PUT /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/logIntegrations
Updated
  • 添加了“GCS_LOG_EXPORT、OTEL_LOG_EXPORT、SPLUNK_LOG_EXPORT、AZURE_LOG_EXPORT、DATADOG_LOG_EXPORT”鉴别器映射键到“results/items/”响应属性
  • 将 '#/components/schemas/DatadogLogIntegrationResponse, #/components/schemas/GcsLogIntegrationResponse, #/components/schemas/OtelLogIntegrationResponse, #/components/schemas/SplunkLogIntegrationResponse, #/components/schemas/AzureLogIntegrationResponse' 添加到 'results/items/'响应的响应属性“oneOf”列表
  • “results/items/oneOf[subschema #1: S3 Log Export Integration Response]/iamRoleId”响应的属性模式'^[a-fA-F0-9]{24}$' 已添加
  • 响应属性“results, results/items/logTypes, results/items/oneOf[subschema #1: S3 Log Export Integration Response]/logTypes”已成为必需
帖子 /api/atlas/v2/groups/{groupId}/logIntegrations
Updated
  • 已将模式'^[a-fA-F0-9]{24}$' 添加到请求属性'/oneOf[subschema #1: S3 日志导出集成请求]/iamRoleId'
  • 向请求鉴别器添加了“GCS_LOG_EXPORT、OTEL_LOG_EXPORT、SPLUNK_LOG_EXPORT、AZURE_LOG_EXPORT、DATADOG_LOG_EXPORT”映射键
  • 将 '#/components/schemas/DatadogLogIntegrationRequest, #/components/schemas/GcsLogIntegrationRequest, #/components/schemas/OtelLogIntegrationRequest, #/components/schemas/SplunkLogIntegrationRequest, #/components/schemas/AzureLogIntegrationRequest' 添加到请求正文 'oneOf' 列表
  • 已将“SPLUNK_LOG_EXPORT、AZURE_LOG_EXPORT、DATADOG_LOG_EXPORT、GCS_LOG_EXPORT、OTEL_LOG_EXPORT”映射键添加到响应状态“201”的响应鉴别器
  • 将 '#/components/模式/DatadogLogIntegrationResponse, #/components/模式/GcsLogIntegrationResponse, #/components/模式/OtelLogIntegrationResponse, #/components/模式/SplunkLogIntegrationResponse, #/components/模式/AzureLogIntegrationResponse' 添加到响应正文 'oneOf' 列表对于响应
  • '/oneOf[subschema #1: S3 Log Export Integration Response]/iamRoleId' 响应的属性模式'^[a-fA-F0-9]{24}$ ' 已添加
  • 在请求属性“type”中添加了新的“AZURE_LOG_EXPORT、DATADOG_LOG_EXPORT、GCS_LOG_EXPORT、OTEL_LOG_EXPORT、SPLUNK_LOG_EXPORT”枚举值
  • 响应属性“/oneOf[subschema #1: S3 Log Export Integration Response]/logTypes, logTypes”变为必填项
GET /api/atlas/v2/groups/{groupId}/logIntegrations/{id}
Updated
  • 已将“AZURE_LOG_EXPORT、DATADOG_LOG_EXPORT、GCS_LOG_EXPORT、OTEL_LOG_EXPORT、SPLUNK_LOG_EXPORT”映射键添加到响应状态“200”的响应鉴别器
  • 将 '#/components/模式/DatadogLogIntegrationResponse, #/components/模式/GcsLogIntegrationResponse, #/components/模式/OtelLogIntegrationResponse, #/components/模式/SplunkLogIntegrationResponse, #/components/模式/AzureLogIntegrationResponse' 添加到响应正文 'oneOf' 列表对于响应
  • '/oneOf[subschema #1: S3 Log Export Integration Response]/iamRoleId' 响应的属性模式'^[a-fA-F0-9]{24}$ ' 已添加
  • 响应属性“/oneOf[subschema #1: S3 Log Export Integration Response]/logTypes, logTypes”变为必填项
PUT /api/atlas/v2/groups/{groupId}/logIntegrations/{id}
Updated
  • 已将模式'^[a-fA-F0-9]{24}$' 添加到请求属性'/oneOf[subschema #1: S3 日志导出集成请求]/iamRoleId'
  • 向请求鉴别器添加了“SPLUNK_LOG_EXPORT、AZURE_LOG_EXPORT、DATADOG_LOG_EXPORT、GCS_LOG_EXPORT、OTEL_LOG_EXPORT”映射键
  • 将 '#/components/schemas/DatadogLogIntegrationRequest, #/components/schemas/GcsLogIntegrationRequest, #/components/schemas/OtelLogIntegrationRequest, #/components/schemas/SplunkLogIntegrationRequest, #/components/schemas/AzureLogIntegrationRequest' 添加到请求正文 'oneOf' 列表
  • 已将“AZURE_LOG_EXPORT、DATADOG_LOG_EXPORT、GCS_LOG_EXPORT、OTEL_LOG_EXPORT、SPLUNK_LOG_EXPORT”映射键添加到响应状态“200”的响应鉴别器
  • 将 '#/components/模式/DatadogLogIntegrationResponse, #/components/模式/GcsLogIntegrationResponse, #/components/模式/OtelLogIntegrationResponse, #/components/模式/SplunkLogIntegrationResponse, #/components/模式/AzureLogIntegrationResponse' 添加到响应正文 'oneOf' 列表对于响应
  • '/oneOf[subschema #1: S3 Log Export Integration Response]/iamRoleId' 响应的属性模式'^[a-fA-F0-9]{24}$ ' 已添加
  • 在请求属性“type”中添加了新的“AZURE_LOG_EXPORT、DATADOG_LOG_EXPORT、GCS_LOG_EXPORT、OTEL_LOG_EXPORT、SPLUNK_LOG_EXPORT”枚举值
  • 响应属性“/oneOf[subschema #1: S3 Log Export Integration Response]/logTypes, logTypes”变为必填项
GET /api/atlas/v2/groups/{groupId}/mongoDBVersions
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/peers
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/availableSnapshots
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/runs
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds
Updated
  • 响应属性“结果”变为必需
POST /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/processes
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/collStats/namespaces
Updated
  • 响应属性“rankedNamespaces”变为必填项
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/databases
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/disks
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/serverless
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/restoreJobs
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/snapshots
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/serviceAccounts
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/accessList
Updated
  • 响应属性“结果”变为必需
POST /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/accessList
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 响应属性“结果”变为必需
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 请求可选属性“connections/items/区域”变为非只读属性
  • 请求可选属性“connections/items/区域”变为非只读属性
  • 请求可选属性“connections/items/区域”变为非只读属性
  • 请求可选属性“connections/items/区域”变为非只读属性
  • 请求可选属性“connections/items/区域”变为非只读属性
  • 请求可选属性“connections/items/区域”变为非只读属性
  • 请求可选属性“connections/items/区域”变为非只读属性
  • 请求可选属性“connections/items/区域”变为非只读属性
  • 请求可选属性“connections/items/区域”变为非只读属性
GET /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 响应属性“结果”变为必需
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 请求可选属性“/ 区域”变为非只读
  • 请求可选属性“/ 区域”变为非只读
  • 请求可选属性“/ 区域”变为非只读
  • 请求可选属性“/ 区域”变为非只读
  • 请求可选属性“/ 区域”变为非只读
  • 请求可选属性“/ 区域”变为非只读
  • 请求可选属性“/ 区域”变为非只读
  • 请求可选属性“/ 区域”变为非只读
  • 请求可选属性“区域”变为非只读属性
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 请求可选属性“/ 区域”变为非只读
  • 请求可选属性“/ 区域”变为非只读
  • 请求可选属性“/ 区域”变为非只读
  • 请求可选属性“/ 区域”变为非只读
  • 请求可选属性“/ 区域”变为非只读
  • 请求可选属性“/ 区域”变为非只读
  • 请求可选属性“/ 区域”变为非只读
  • 请求可选属性“/ 区域”变为非只读
  • 请求可选属性“区域”变为非只读属性
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processors
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/teams
Updated
  • 响应属性“结果”变为必需
POST /api/atlas/v2/groups/{groupId}/teams
Updated
  • 响应属性“结果”变为必需
PATCH /api/atlas/v2/groups/{groupId}/teams/{teamId}
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/groups/{groupId}/users
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/orgs
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/orgs/{orgId}/apiKeys
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList
Updated
  • 响应属性“结果”变为必需
POST /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/orgs/{orgId}/federationSettings
Updated
  • 响应属性“federatedDomains”变为必需
GET /api/atlas/v2/orgs/{orgId}/groups
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/orgs/{orgId}/invoices
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}/lineItems:search
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/orgs/{orgId}/liveMigrations/availableProjects
Updated
  • 响应属性“/items/deployments, /items/migrationHosts”变为必填项
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/accessList
Updated
  • 响应属性“结果”变为必需
POST /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/accessList
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/groups
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/orgs/{orgId}/teams
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users
Updated
  • 响应属性“结果”变为必需
POST /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users
Updated
  • 响应属性“结果、结果/项目/角色”成为必需
GET /api/atlas/v2/orgs/{orgId}/users
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/rateLimits
Updated
  • 响应属性“结果”变为必需
GET /api/atlas/v2/skus
Updated
  • 响应属性“结果”变为必需
POST /api/atlas/v2/users
Updated
  • 响应属性“角色”变为必需
GET /api/atlas/v2/users/byName/{userName}
Updated
  • 响应属性“角色”变为必需
GET /api/atlas/v2/users/{userId}
Updated
  • 响应属性“角色”变为必需

2026 年 2 月 24 日发布

GET /api/atlas/v2
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/alertConfigs/matchers/fieldNames
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/clusters
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/eventTypes
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings/{id}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings/{id}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PUT /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings/{id}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}/jwks
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}/metadata.xml
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/byName/{groupName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/access
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/accessList
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/accessList
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/accessList/{entryValue}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/accessList/{entryValue}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/accessList/{entryValue}/status
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/activityFeed
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/apiKeys
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/apiKeys
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/auditLog
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/auditLog
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/awsCustomDNS
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/awsCustomDNS
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/backup/exportBuckets
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/backup/exportBuckets
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/backup/exportBuckets/{exportBucketId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/backup/exportBuckets/{exportBucketId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/ 备份/exportBuckets/{exportBucketId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/ 备份/{cloudProvider}/privateEndpoints
Updated
  • 添加了状态为“ 429 ”的非成功响应
帖子 /api/atlas/v2/groups/{groupId}/备份/{cloudProvider}/privateEndpoints
Updated
  • 添加了状态为“ 429 ”的非成功响应
删除 /api/atlas/v2/groups/{groupId}/备份/{cloudProvider}/privateEndpoints/{endpointId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/ 备份/{cloudProvider}/privateEndpoints/{endpointId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/backupCompliancePolicy
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/backupCompliancePolicy
Updated
  • 添加了状态为“ 429 ”的非成功响应
PUT /api/atlas/v2/groups/{groupId}/backupCompliancePolicy
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/cloudProviderAccess
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/cloudProviderAccess
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/cloudProviderAccess/{cloudProvider}/{roleId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/cloudProviderAccess/{roleId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/cloudProviderAccess/{roleId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/provider/regions
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgradeToServerless
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET / API/ Atlas/v2/groups/{groupId}/clusters/{clusterName}/autoScalingConfiguration
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports/{exportId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs/{restoreJobId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs/{restoreJobId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/shardedCluster/{snapshotId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/shardedCluster/{snapshotId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/shardedClusters
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/download
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/restore
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/restores
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/restores/{restoreId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/snapshots
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/snapshots/{snapshotId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backupCheckpoints
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backupCheckpoints/{checkpointId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • 添加了状态为“ 429 ”的非成功响应
PUT /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/unpin
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{databaseName}/{collectionName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/customZoneMapping
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/customZoneMapping
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/managedNamespaces
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/managedNamespaces
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/queryLogs.gz
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/outageSimulation
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/outageSimulation
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/outageSimulation
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restartPrimaries
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs/{jobId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshotSchedule
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshotSchedule
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots/{snapshotId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots/{snapshotId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots/{snapshotId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/status
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/{clusterView}/collStats/namespaces
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/{clusterView}/{databaseName}/{collectionName}/collStats/measurements
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}:grantMongoDBEmployeeAccess
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}:pinFeatureCompatibilityVersion
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}:revokeMongoDBEmployeeAccess
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}:unpinFeatureCompatibilityVersion
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{hostName}/logs/{logName}.gz
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/collStats/metrics
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/containers
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/containers
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/containers/all
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/dataFederation
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/dataFederation
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/limits
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/limits/{limitName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/limits/{limitName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/limits/{limitName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/queryLogs.gz
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/databaseUsers
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/databaseUsers
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/databaseUsers/{databaseName}/{username}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/databaseUsers/{databaseName}/{username}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/databaseUsers/{databaseName}/{username}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/databaseUsers/{username}/certs
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/databaseUsers/{username}/certs
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints/{endpointId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints/{endpointId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/flexClusters
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/flexClusters
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/flexClusters/{name}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/flexClusters/{name}
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/download
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/restoreJobs
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/restoreJobs
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/restoreJobs/{restoreJobId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/snapshots
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/snapshots/{snapshotId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/flexClusters:tenantUpgrade
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/integrations
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PUT /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/invites
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/invites
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/invites
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/invites/{invitationId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/invites/{invitationId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/invites/{invitationId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/ipAddresses
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/limits
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/limits/{limitName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/limits/{limitName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/limits/{limitName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/liveMigrations
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/liveMigrations/validate
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/liveMigrations/validate/{validationId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/liveMigrations/{liveMigrationId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PUT /api/atlas/v2/groups/{groupId}/liveMigrations/{liveMigrationId}/cutover
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/logIntegrations
Updated
  • 添加了状态为“ 429 ”的非成功响应
帖子 /api/atlas/v2/groups/{groupId}/logIntegrations
Updated
  • 添加了状态为“ 429 ”的非成功响应
删除 /api/atlas/v2/groups/{groupId}/logIntegrations/{id}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/logIntegrations/{id}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PUT /api/atlas/v2/groups/{groupId}/logIntegrations/{id}
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/maintenanceWindow
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/maintenanceWindow
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/maintenanceWindow
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/maintenanceWindow/autoDefer
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/maintenanceWindow/defer
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/mongoDBVersions
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/peers
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/peers
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/peers/{peerId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/peers/{peerId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/peers/{peerId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/pipelines
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/pipelines
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/availableSchedules
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/availableSnapshots
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/pause
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/resume
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/runs
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/runs/{pipelineRunId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/runs/{pipelineRunId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/trigger
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/privateEndpoint/endpointService
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/regionalMode
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/privateEndpoint/regionalMode
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint/{endpointId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint/{endpointId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint/{endpointId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}/endpoint
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}/endpoint/{endpointId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}/endpoint/{endpointId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/privateIpMode
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/privateIpMode
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds/{endpointId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds/{endpointId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/processes
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/processes/{processId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/collStats/namespaces
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/databases
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/databases/{databaseName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/databases/{databaseName}/measurements
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/disks
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/disks/{partitionName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/disks/{partitionName}/measurements
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/measurements
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/{databaseName}/{collectionName}/collStats/measurements
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/sampleDatasetLoad/{name}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/sampleDatasetLoad/{sampleDatasetId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/serverless
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/serverless
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/restoreJobs
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/restoreJobs
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/restoreJobs/{restoreJobId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/snapshots
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/serverless/{name}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/serverless/{name}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/serverless/{name}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/serviceAccounts
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/serviceAccounts
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/accessList
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/accessList
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/accessList/{ipAddress}
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/secrets
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/secrets/{secretId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}:invite
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/settings
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/settings
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/streams/accountDetails
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/streams/activeVpcPeeringConnections
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections/{connectionId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections/{connectionId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/streams/vpcPeeringConnections
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/streams/vpcPeeringConnections/{id}
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/streams/vpcPeeringConnections/{id}:accept
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/streams/vpcPeeringConnections/{id}:reject
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/auditLogs
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}:start
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST / API/ Atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}:startWith
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}:stop
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processors
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}:downloadOperationalLogs
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/teams
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/teams
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/teams/{teamId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET / API/ Atlas/v2/groups/{groupId}/teams/{teamId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/teams/{teamId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/userSecurity
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/userSecurity
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/userSecurity/customerX509
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/userSecurity/ldap/userToDNMapping
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/userSecurity/ldap/verify
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/userSecurity/ldap/verify/{requestId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/users
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/users
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/users/{userId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/users/{userId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PUT /api/atlas/v2/groups/{groupId}/users/{userId}/roles
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/users/{userId}:addRole
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/users/{userId}:removeRole
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}:migrate
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/orgs
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/orgs/{orgId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/orgs/{orgId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/activityFeed
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/apiKeys
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/orgs/{orgId}/apiKeys
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList/{ipAddress}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList/{ipAddress}
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/orgs/{orgId}/billing/costExplorer/usage
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/billing/costExplorer/usage/{token}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/federationSettings
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/groups
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/invites
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/orgs/{orgId}/invites
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/orgs/{orgId}/invites
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/invoices
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}/csv
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}/lineItems:search
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/liveMigrations/availableProjects
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/orgs/{orgId}/liveMigrations/linkTokens
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/orgs/{orgId}/liveMigrations/linkTokens
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/nonCompliantResources
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/resourcePolicies
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/orgs/{orgId}/resourcePolicies
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/orgs/{orgId}/resourcePolicies/{resourcePolicyId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/resourcePolicies/{resourcePolicyId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/orgs/{orgId}/resourcePolicies/{resourcePolicyId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/orgs/{orgId}/resourcePolicies:validate
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/orgs/{orgId}/serviceAccounts
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/accessList
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/accessList
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/accessList/{ipAddress}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/groups
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/secrets
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/secrets/{secretId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/settings
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/teams
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/orgs/{orgId}/teams
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/teams/byName/{teamName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/orgs/{orgId}/teams/{teamId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/teams/{teamId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/orgs/{orgId}/teams/{teamId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users/{userId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/orgs/{orgId}/teams/{teamId}:addUser
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/orgs/{orgId}/teams/{teamId}:removeUser
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/users
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/orgs/{orgId}/users
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/orgs/{orgId}/users/{userId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/orgs/{orgId}/users/{userId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PATCH /api/atlas/v2/orgs/{orgId}/users/{userId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
PUT /api/atlas/v2/orgs/{orgId}/users/{userId}/roles
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/orgs/{orgId}/users/{userId}:addRole
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/orgs/{orgId}/users/{userId}:removeRole
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/rateLimits
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/rateLimits/{endpointSetId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/skus
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/skus/{skuId}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/unauth/controlPlaneIPAddresses
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/users
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/users/byName/{userName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/users/{userId}
Updated
  • 添加了状态为“ 429 ”的非成功响应

2026 年 2 月 23 日发布

GET /api/atlas/v2/rateLimits
已交
  • 已添加端点
GET /api/atlas/v2/rateLimits/{endpointSetId}
已交
  • 已添加端点

2026 年 2 月 18 日发布

GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/auditLogs
Updated
  • 添加了新的可选“查询”请求参数“spName”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}:downloadOperationalLogs
已交
  • 已添加端点

2026 年 2 月 17 日发布

POST /api/atlas/v2/orgs/{orgId}/billing/costExplorer/usage
Updated
  • 在请求属性“services/items/”中添加了新的“DSC Compute、DSC Storage”枚举值
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}/lineItems:search
Updated
  • 在请求属性“过滤器/skuServices/items/”中添加了新的“DSC Compute、DSC Storage”枚举值

2026 年 2 月 12 日发布

PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 添加了状态为“ 405 ”的非成功响应
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}/metadata.xml
Updated
  • 添加了状态为“ 405 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“subschema #7: Atlas 审核 Types”、“subschema #8: 维护窗口 审核 Types”、“subschema #13: 自动伸缩 审核 Types” 添加到“results/items/oneOf[subschema #1: Any 其他 警报 配置]/eventTypeName” 响应的响应属性“oneOf” 列表
  • 从“results/items/oneOf[subschema #1”中删除了“subschema #7: NDS Atlas 审核类型”、“subschema #8: NDS 维护窗口 Atlas 审核类型”、“subschema #13: NDS 自动伸缩 Atlas 审核类型” : 响应的任何其他警报配置]/eventTypeName' 响应属性'oneOf' 列表
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在“/oneOf[subschema #1：任何其他警报配置”中添加了“subschema #7： Atlas Atlas 审核类型、subschema #8：维护窗口审核类型、subschema #13：自动伸缩 审核类型” ]/eventTypeName'请求属性'oneOf' 列表
  • 在“/oneOf[subschema #1：任何其他警报配置”中添加了“subschema #7： Atlas审核类型、subschema #8：维护窗口审核类型、subschema #13：自动伸缩 审核类型” ]/eventTypeName' 响应的响应属性'oneOf' 列表
  • 从 '/oneOf[subschema #1: Any other] 中删除了 'subschema #7: NDS Atlas 审核类型、subschema #8: NDS 维护窗口 Atlas 审核类型、subschema #13: NDS 自动伸缩 Atlas 审核类型' 警报配置]/eventTypeName' 响应的响应属性'oneOf' 列表
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在“/oneOf[subschema #1：任何其他警报配置”中添加了“subschema #7： Atlas审核类型、subschema #8：维护窗口审核类型、subschema #13：自动伸缩 审核类型” ]/eventTypeName' 响应的响应属性'oneOf' 列表
  • 从 '/oneOf[subschema #1: Any other] 中删除了 'subschema #7: NDS Atlas 审核类型、subschema #8: NDS 维护窗口 Atlas 审核类型、subschema #13: NDS 自动伸缩 Atlas 审核类型' 警报配置]/eventTypeName' 响应的响应属性'oneOf' 列表
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在“/oneOf[subschema #1：任何其他警报配置”中添加了“subschema #7： Atlas审核类型、subschema #8：维护窗口审核类型、subschema #13：自动伸缩 审核类型” ]/eventTypeName' 响应的响应属性'oneOf' 列表
  • 从 '/oneOf[subschema #1: Any other] 中删除了 'subschema #7: NDS Atlas 审核类型、subschema #8: NDS 维护窗口 Atlas 审核类型、subschema #13: NDS 自动伸缩 Atlas 审核类型' 警报配置]/eventTypeName' 响应的响应属性'oneOf' 列表
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在“/oneOf[subschema #1：任何其他警报配置”中添加了“subschema #7： Atlas Atlas 审核类型、subschema #8：维护窗口审核类型、subschema #13：自动伸缩 审核类型” ]/eventTypeName'请求属性'oneOf' 列表
  • 在“/oneOf[subschema #1：任何其他警报配置”中添加了“subschema #7： Atlas审核类型、subschema #8：维护窗口审核类型、subschema #13：自动伸缩 审核类型” ]/eventTypeName' 响应的响应属性'oneOf' 列表
  • 从 '/oneOf[subschema #1: Any other] 中删除了 'subschema #7: NDS Atlas 审核类型、subschema #8: NDS 维护窗口 Atlas 审核类型、subschema #13: NDS 自动伸缩 Atlas 审核类型' 警报配置]/eventTypeName' 响应的响应属性'oneOf' 列表
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 将“子模式 #7： Atlas审核类型、子模式 #8：维护窗口审核类型、子模式 #9：x509 用户身份验证事件类型、子模式 #16：自动伸缩审核类型”添加到响应的“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表
  • 从响应的“results/items/oneOf[subschema #7: Any other 警报]/eventTypeName”响应属性“oneOf”列表中删除了“子模式 #7：NDS Atlas 审核类型、子模式 #8：NDS 维护窗口Atlas 审核类型、子模式 #9：NDS x509 用户身份验证事件类型、子模式 #16：NDS 自动伸缩Atlas 审核”
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 将“子模式 #7： Atlas审核类型、子模式 #8：维护窗口审核类型、子模式 #9：x509 用户身份验证事件类型、子模式 #16：自动伸缩审核类型”添加到响应的“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表
  • 从响应的“results/items/oneOf[subschema #7: Any other 警报]/eventTypeName”响应属性“oneOf”列表中删除了“子模式 #7：NDS Atlas 审核类型、子模式 #8：NDS 维护窗口Atlas 审核类型、子模式 #9：NDS x509 用户身份验证事件类型、子模式 #16：NDS 自动伸缩Atlas 审核”
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“子模式 #7： Atlas审核类型、子模式 #8：维护窗口审核类型、子模式 #9：x509 用户身份验证事件类型、子模式 #16：自动伸缩审核类型”添加到响应的 '/oneOf[subschema #7: Any other Alerts]/eventTypeName' 属性'oneOf' 列表
  • 删除了“子模式 #7：NDS Atlas 审核类型、子模式 #8：NDS 维护窗口Atlas 审核类型、子模式 #9：NDS x509 用户身份验证事件类型、子模式 #16：NDS 自动伸缩Atlas 审核”响应的“/oneOf[subschema #7: Any other 警报]/eventTypeName”响应属性“oneOf”列表中的“Types”
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“子模式 #7： Atlas审核类型、子模式 #8：维护窗口审核类型、子模式 #9：x509 用户身份验证事件类型、子模式 #16：自动伸缩审核类型”添加到响应的 '/oneOf[subschema #7: Any other Alerts]/eventTypeName' 属性'oneOf' 列表
  • 删除了“子模式 #7：NDS Atlas 审核类型、子模式 #8：NDS 维护窗口Atlas 审核类型、子模式 #9：NDS x509 用户身份验证事件类型、子模式 #16：NDS 自动伸缩Atlas 审核”响应的“/oneOf[subschema #7: Any other 警报]/eventTypeName”响应属性“oneOf”列表中的“Types”
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 将“subschema #7: Atlas 审核 Types”、“subschema #8: 维护窗口 审核 Types”、“subschema #13: 自动伸缩 审核 Types” 添加到“results/items/oneOf[subschema #1: Any 其他 警报 配置]/eventTypeName” 响应的响应属性“oneOf” 列表
  • 从“results/items/oneOf[subschema #1”中删除了“subschema #7: NDS Atlas 审核类型”、“subschema #8: NDS 维护窗口 Atlas 审核类型”、“subschema #13: NDS 自动伸缩 Atlas 审核类型” : 响应的任何其他警报配置]/eventTypeName' 响应属性'oneOf' 列表
GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 在响应中添加了可选属性“results/items/effectiveReplicationSpecs”
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 添加了新的可选“标头”请求参数“Use-Effective-Fields-复制-Specs”
  • 在请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/regionName/oneOf[subschema #2: Azure 区域]/'中添加了新的“US_GOV_ARIZONA、US_GOV_TEXAS、US_GOV_VIRGINIA”枚举值。
  • 已将新的“US_GOV_ARIZONA、US_GOV_TEXAS、US_GOV_VIRGINIA”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/regionName/oneOf[subschema #2: Azure 区域]/”
  • 在请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/regionName/oneOf[subschema #2: Azure区域]/'
  • 在请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/regionName/oneOf[subschema #2: Azure区域]/'中添加了新的“US_GOV_ARIZONA、US_GOV_TEXAS、US_GOV_VIRGINIA”枚举值。
  • 已将新的“US_GOV_ARIZONA、US_GOV_TEXAS、US_GOV_VIRGINIA”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #2: Azure Regions]/”
  • 在响应中添加了可选属性“有效复制规范”
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 在请求属性“providerSettings/oneOf[subschema #2: Cloud Service Provider Settings for a Cluster]/regionName”中添加了新的“US_GOV_ARIZONA、US_GOV_TEXAS、US_GOV_VIRGINIA”枚举值
  • 在响应中添加了可选属性“deleteAfterCreationHours、deleteAfterDate”
  • 添加了新的可选请求属性“deleteAfterCreationHours”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 添加了新的可选“标头”请求参数“Use-Effective-Fields-复制-Specs”
  • 在响应中添加了可选属性“有效复制规范”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 添加了新的可选“标头”请求参数“Use-Effective-Fields-复制-Specs”
  • 在请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/regionName/oneOf[subschema #2: Azure 区域]/'中添加了新的“US_GOV_ARIZONA、US_GOV_TEXAS、US_GOV_VIRGINIA”枚举值。
  • 已将新的“US_GOV_ARIZONA、US_GOV_TEXAS、US_GOV_VIRGINIA”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/regionName/oneOf[subschema #2: Azure 区域]/”
  • 在请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/regionName/oneOf[subschema #2: Azure区域]/'
  • 在请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/regionName/oneOf[subschema #2: Azure区域]/'中添加了新的“US_GOV_ARIZONA、US_GOV_TEXAS、US_GOV_VIRGINIA”枚举值。
  • 已将新的“US_GOV_ARIZONA、US_GOV_TEXAS、US_GOV_VIRGINIA”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #2: Azure Regions]/”
  • 在响应中添加了可选属性“有效复制规范”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 在响应中添加了可选的只写入属性“deleteCopySnapshots”
  • 在响应中添加了可选的只写入属性“updateCopySnapshots”
  • 在响应中添加了可选属性“copyPolicyItemsEnabled、copySettings/items/copyPolicyItems、copySettings/items/lastNumberOfSnapshots”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 在响应中添加了可选的只写入属性“deleteCopySnapshots”
  • 在响应中添加了可选的只写入属性“updateCopySnapshots”
  • 在响应中添加了可选属性“copyPolicyItemsEnabled、copySettings/items/copyPolicyItems、copySettings/items/lastNumberOfSnapshots”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 在响应中添加了可选的只写入属性“deleteCopySnapshots”
  • 在响应中添加了可选的只写入属性“updateCopySnapshots”
  • 在响应中添加了可选属性“copyPolicyItemsEnabled、copySettings/items/copyPolicyItems、copySettings/items/lastNumberOfSnapshots”
  • 添加了新的可选请求属性“copyPolicyItemsEnabled、copySettings/items/copyPolicyItems、copySettings/items/lastNumberOfSnapshots、deleteCopySnapshots、updateCopySnapshots”
POST /api/atlas/v2/groups/{groupId}/containers
Updated
  • 已将新的“US_GOV_ARIZONA、US_GOV_TEXAS、US_GOV_VIRGINIA”枚举值添加到请求属性“/oneOf[subschema #1: AZURE]/区域”
PATCH /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 已将新的“US_GOV_ARIZONA、US_GOV_TEXAS、US_GOV_VIRGINIA”枚举值添加到请求属性“/oneOf[subschema #1: AZURE]/区域”
POST /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 在请求属性“actions/items/操作”中添加了新的“MODIFY_STREAM_PROCESSOR”枚举值
PATCH /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 在请求属性“actions/items/操作”中添加了新的“MODIFY_STREAM_PROCESSOR”枚举值
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 在“azureKeyVault/azureEnvironment”响应属性中添加了新的“AZURE_US_GOVERNMENT”枚举值
PATCH /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 在“azureKeyVault/azureEnvironment”响应属性中添加了新的“AZURE_US_GOVERNMENT”枚举值
  • 在请求属性“azureKeyVault/azureEnvironment”中添加了新的“AZURE_US_GOVERNMENT”枚举值
POST /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
Updated
  • 在请求属性'/oneOf[subschema #1: Azure Key Vault EAR 私有端点]/regionName/oneOf[subschema #1: Azure Regions]/' 中添加了新的 'US_GOV_ARIZONA、US_GOV_TEXAS、US_GOV_VIRGINIA'枚举值
  • 在请求属性'/oneOf[subschema #2: AWS Key Management Service EAR Private Endpoint]/regionName/oneOf[subschema #1: Azure Regions]/' 中添加了新的 'US_GOV_ARIZONA、US_GOV_TEXAS、US_GOV_VIRGINIA'枚举值
  • 已将新的“US_GOV_ARIZONA、US_GOV_TEXAS、US_GOV_VIRGINIA”枚举值添加到请求属性“regionName/oneOf[subschema #1: Azure Regions]/”
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 添加了 'subschema #15: DB Check Atlas 审核类型、子模式 #16: Data Validation Atlas 审核类型、子模式 #17: 维护窗口 Atlas 审核类型、子模式 #18: 无服务器 Auto Scaling Atlas 审核类型、子模式 #19: 租户终结点服务部署Atlas 审核类型，子模式 #20: x509 用户身份验证事件类型 ' 到 'results/items/oneOf[subschema #1: Any other 事件]/eventTypeName' 响应属性' oneOf' 响应列表
  • 删除了“子模式 #15：NDS DB Check Atlas 审核类型、子模式 #16：NDS 数据验证 Atlas 审核类型、子模式 #17：NDS 维护窗口 Atlas 审核类型、子模式 #18：NDS 无服务器 自动伸缩 Atlas 审核类型、子模式 #19：NDS 租户终结点服务部署 Atlas 审核类型，子模式 #20：“results/items/oneOf[subschema #1：任何其他事件]”中的 NDS x509 用户身份验证事件类型/eventTypeName' 响应的响应属性'oneOf' 列表
  • 将新的 'CLUSTER_CANCELING_CONFIG_SERVER_TRANSITION_REQUESTED'枚举值添加到 'results/items/oneOf[subschema #15: NDS Audits -> subschema #15: Atlas 项目 Audits]/eventTypeName' 响应属性
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 添加了 'subschema #15: DB Check Atlas 审核类型、子模式 #16: Data 验证 Atlas 审核类型、子模式 #17: 维护窗口 Atlas 审核类型、子模式 #18: 无服务器 Auto Scaling Atlas 审核类型、子模式 #19：租户终结点服务部署 Atlas 审核类型、子模式“#20：x509 用户身份验证事件类型”添加到“/oneOf[subschema #1：任何其他事件]/eventTypeName”响应属性“oneOf”列表对于响应
  • 删除了“子模式 #15：NDS DB Check Atlas 审核类型、子模式 #16：NDS 数据验证 Atlas 审核类型、子模式 #17：NDS 维护窗口 Atlas 审核类型、子模式 #18：NDS 无服务器自动伸缩 Atlas 审核类型、子模式 #19：NDS 租户端结点服务部署 Atlas 审核类型，子模式 #20：“/oneOf[subschema #1：任何其他事件]/事件类型名称”中的 NDS x509 用户身份验证事件类型响应的响应属性“oneOf”列表
  • 将新的“CLUSTER_CANCELING_CONFIG_SERVER_TRANSITION_REQUESTED”枚举值添加到“/oneOf[subschema #15: NDS Audits -> subschema #15: Atlas Project Audits]/eventTypeName”响应属性
POST /api/atlas/v2/groups/{groupId}/flexClusters:tenantUpgrade
Updated
  • 在请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/regionName/oneOf[subschema #2: Azure 区域]/'中添加了新的“US_GOV_ARIZONA、US_GOV_TEXAS、US_GOV_VIRGINIA”枚举值。
  • 已将新的“US_GOV_ARIZONA、US_GOV_TEXAS、US_GOV_VIRGINIA”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/regionName/oneOf[subschema #2: Azure 区域]/”
  • 在请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/regionName/oneOf[subschema #2: Azure区域]/'
  • 在请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/regionName/oneOf[subschema #2: Azure区域]/'中添加了新的“US_GOV_ARIZONA、US_GOV_TEXAS、US_GOV_VIRGINIA”枚举值。
  • 已将新的“US_GOV_ARIZONA、US_GOV_TEXAS、US_GOV_VIRGINIA”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #2: Azure Regions]/”
GET /api/atlas/v2/groups/{groupId}/logIntegrations
Updated
  • 在响应中添加了可选属性“results/items/logTypes”
帖子 /api/atlas/v2/groups/{groupId}/logIntegrations
Updated
  • 添加了请求鉴别器
  • 将“#/components/schemas/S3LogIntegrationRequest”添加到请求正文“oneOf”列表
  • 在响应中添加了可选属性“logTypes”
GET /api/atlas/v2/groups/{groupId}/logIntegrations/{id}
Updated
  • 在响应中添加了可选属性“logTypes”
PUT /api/atlas/v2/groups/{groupId}/logIntegrations/{id}
Updated
  • 在响应中添加了可选属性“logTypes”
POST /api/atlas/v2/groups/{groupId}/privateEndpoint/endpointService
Updated
  • 添加了新的可选请求属性“portMappingEnabled”
GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在响应中添加了可选属性“results/items/connections/items/区域”
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在响应中添加了可选属性“connections/items/区域”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在响应中添加了可选属性“connections/items/区域”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在响应中添加了可选属性“connections/items/区域”
  • 添加了新的可选请求属性“streamConfig”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 在响应中添加了可选属性“results/items/区域”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 在响应中添加了可选属性“/ 区域, 区域”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 在响应中添加了可选属性“/ 区域, 区域”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 在响应中添加了可选属性“/ 区域, 区域”
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
Updated
  • 在响应中添加了可选属性“connections/items/区域”
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 将新的“MARKETPLACE_REFUND_ISSUED”枚举值添加到“results/items/oneOf[subschema #6: Billing Events]/eventTypeName”响应属性
  • 将新的“ORG_LOCKED_ACCELERATED”枚举值添加到“results/items/oneOf[subschema #8: Org Events -> subschema #8: Organization Events]/eventTypeName”响应属性
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 将新的“MARKETPLACE_REFUND_ISSUED”枚举值添加到“/oneOf[subschema #6: Billing Events]/eventTypeName”响应属性
  • 将新的“ORG_LOCKED_ACCELERATED”枚举值添加到“/oneOf[subschema #8: Org Events -> subschema #8: Organization Events]/eventTypeName”响应属性
PATCH /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
Updated
  • 删除了“groupRoleAssignments/items/groupRole”响应属性中的“GROUP_STREAM_PROCESSING_OWNER”枚举值

2026 年 2 月 03 日发布

POST / API/ Atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}:startWith
Updated
  • 添加了新的可选请求属性“resumeFromCheckpoint”

2026 年 1 月 30 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“SEARCH_MAX_NGRAM_FIELDS_INDEXED”鉴别器映射键添加到“results/items/oneOf[subschema #9: 托管 Metric 警报 Configuration]/metricThreshold”响应属性
  • 将“#/components/schemas/SearchMaxNgramFieldsIndexedRawMetricThresholdView”添加到响应的“results/items/oneOf[subschema #9: 托管 警报 Configuration]/metricThreshold”响应属性“oneOf”列表
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“SEARCH_MAX_NGRAM_FIELDS_INDEXED”鉴别器映射键添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性
  • 将“#/components/schemas/SearchMaxNgramFieldsIndexedRawMetricThresholdView”添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性“oneOf”列表
  • 将“SEARCH_MAX_NGRAM_FIELDS_INDEXED”鉴别器映射键添加到“/oneOf[subschema #9: 托管 警报 Configuration]/metricThreshold”响应属性
  • 将“#/components/schemas/SearchMaxNgramFieldsIndexedRawMetricThresholdView”添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“SEARCH_MAX_NGRAM_FIELDS_INDEXED”鉴别器映射键添加到“/oneOf[subschema #9: 托管 警报 Configuration]/metricThreshold”响应属性
  • 将“#/components/schemas/SearchMaxNgramFieldsIndexedRawMetricThresholdView”添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性“oneOf”列表中
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“SEARCH_MAX_NGRAM_FIELDS_INDEXED”鉴别器映射键添加到“/oneOf[subschema #9: 托管 警报 Configuration]/metricThreshold”响应属性
  • 将“#/components/schemas/SearchMaxNgramFieldsIndexedRawMetricThresholdView”添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性“oneOf”列表中
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“SEARCH_MAX_NGRAM_FIELDS_INDEXED”鉴别器映射键添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性
  • 将“#/components/schemas/SearchMaxNgramFieldsIndexedRawMetricThresholdView”添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性“oneOf”列表
  • 将“SEARCH_MAX_NGRAM_FIELDS_INDEXED”鉴别器映射键添加到“/oneOf[subschema #9: 托管 警报 Configuration]/metricThreshold”响应属性
  • 将“#/components/schemas/SearchMaxNgramFieldsIndexedRawMetricThresholdView”添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 将“SEARCH_MAX_NGRAM_FIELDS_INDEXED”鉴别器映射键添加到“results/items/oneOf[subschema #4: 托管指标警报]/”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 将“SEARCH_MAX_NGRAM_FIELDS_INDEXED”鉴别器映射键添加到“results/items/oneOf[subschema #4: 托管指标警报]/”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“SEARCH_MAX_NGRAM_FIELDS_INDEXED”鉴别器映射键添加到“/oneOf[subschema #4: Host Metric Alerts]/”响应属性
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“SEARCH_MAX_NGRAM_FIELDS_INDEXED”鉴别器映射键添加到“/oneOf[subschema #4: Host Metric Alerts]/”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 将“SEARCH_MAX_NGRAM_FIELDS_INDEXED”鉴别器映射键添加到“results/items/oneOf[subschema #9: 托管 Metric 警报 Configuration]/metricThreshold”响应属性
  • 将“#/components/schemas/SearchMaxNgramFieldsIndexedRawMetricThresholdView”添加到响应的“results/items/oneOf[subschema #9: 托管 警报 Configuration]/metricThreshold”响应属性“oneOf”列表
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将“SEARCH_MAX_NGRAM_FIELDS_INDEXED”鉴别器映射键添加到“results/items/oneOf[subschema #14: 托管 Metric Events]/”响应属性
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 将“SEARCH_MAX_NGRAM_FIELDS_INDEXED”鉴别器映射键添加到“/oneOf[subschema #14: 托管 Metric Events]/”响应属性
DELETE /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 端点已弃用
GET /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 端点已弃用
PATCH /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 端点已弃用
POST /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 端点已弃用

2026 年 1 月 28 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“SEARCH_MAX_FIELDS_INDEXED”鉴别器映射键添加到“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性
  • 将“#/components/schemas/SearchMaxFieldsIndexedRawMetricThresholdView”添加到“results/items/oneOf[subschema #9: 托管 Metric 警报 Configuration]/metricThreshold”响应属性“oneOf”列表中
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“SEARCH_MAX_FIELDS_INDEXED”鉴别器映射键添加到“/oneOf[subschema #9: 托管 Metric 警报 Configuration]/metricThreshold”请求属性
  • 将“#/components/schemas/SearchMaxFieldsIndexedRawMetricThresholdView”添加到“/oneOf[subschema #9: 托管 警报 Configuration]/metricThreshold”请求属性“oneOf”列表
  • 将“SEARCH_MAX_FIELDS_INDEXED”鉴别器映射键添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性
  • 将“#/components/schemas/SearchMaxFieldsIndexedRawMetricThresholdView”添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应模式“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“SEARCH_MAX_FIELDS_INDEXED”鉴别器映射键添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性
  • 将“#/components/schemas/SearchMaxFieldsIndexedRawMetricThresholdView”添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应模式“oneOf”列表中
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“SEARCH_MAX_FIELDS_INDEXED”鉴别器映射键添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性
  • 将“#/components/schemas/SearchMaxFieldsIndexedRawMetricThresholdView”添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应模式“oneOf”列表中
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“SEARCH_MAX_FIELDS_INDEXED”鉴别器映射键添加到“/oneOf[subschema #9: 托管 Metric 警报 Configuration]/metricThreshold”请求属性
  • 将“#/components/schemas/SearchMaxFieldsIndexedRawMetricThresholdView”添加到“/oneOf[subschema #9: 托管 警报 Configuration]/metricThreshold”请求属性“oneOf”列表
  • 将“SEARCH_MAX_FIELDS_INDEXED”鉴别器映射键添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性
  • 将“#/components/schemas/SearchMaxFieldsIndexedRawMetricThresholdView”添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应模式“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 将“SEARCH_MAX_FIELDS_INDEXED”鉴别器映射键添加到“results/items/oneOf[subschema #4: Host Metric Alerts]/”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 将“SEARCH_MAX_FIELDS_INDEXED”鉴别器映射键添加到“results/items/oneOf[subschema #4: Host Metric Alerts]/”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“SEARCH_MAX_FIELDS_INDEXED”鉴别器映射键添加到“/oneOf[subschema #4: Host Metric Alerts]/”响应属性
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“SEARCH_MAX_FIELDS_INDEXED”鉴别器映射键添加到“/oneOf[subschema #4: Host Metric Alerts]/”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 将“SEARCH_MAX_FIELDS_INDEXED”鉴别器映射键添加到“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性
  • 将“#/components/schemas/SearchMaxFieldsIndexedRawMetricThresholdView”添加到“results/items/oneOf[subschema #9: 托管 Metric 警报 Configuration]/metricThreshold”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将“SEARCH_MAX_FIELDS_INDEXED”鉴别器映射键添加到“results/items/oneOf[subschema #14: Host Metric Events]/”响应属性
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 将“SEARCH_MAX_FIELDS_INDEXED”鉴别器映射键添加到“/oneOf[subschema #14: Host Metric Events]/”响应属性

2026 年 1 月 22 日发布

GET /api/atlas/v2/groups/{groupId}/activityFeed
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 已从“results/items/oneOf[subschema #9: 托管 指标 警报 Configuration]/ 通知 /items/oneOf[subschema #3: Group notification]/roles/items/”响应属性中删除“GROUP_STREAM_PROCESSING_OWNER” 枚举 值
GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 在响应中添加了可选属性“results/items/retainBackups”
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 在响应中添加了可选属性“retainBackups”
  • 添加了新的可选请求属性“retainBackups”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 在响应中添加了可选属性“retainBackups”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 在响应中添加了可选属性“retainBackups”
  • 添加了新的可选请求属性“retainBackups”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/download
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2026-01-22”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/restore
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2026-01-22”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/restores
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2026-01-22”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/restores/{restoreId}
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2026-01-22”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/snapshots
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2026-01-22”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/snapshots/{snapshotId}
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2026-01-22”
POST /api/atlas/v2/groups/{groupId}/flexClusters:tenantUpgrade
Updated
  • 添加了新的可选请求属性“retainBackups”
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2026-01-22”
POST /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2026-01-22”
DELETE /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint/{endpointId}
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2026-01-22”
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint/{endpointId}
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2026-01-22”
PATCH /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint/{endpointId}
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2026-01-22”
POST /api/atlas/v2/groups/{groupId}/serverless
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2026-01-22”
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/restoreJobs
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2026-01-22”
POST /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/restoreJobs
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2026-01-22”
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/restoreJobs/{restoreJobId}
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2026-01-22”
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/snapshots
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2026-01-22”
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/snapshots/{snapshotId}
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2026-01-22”
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/performanceAdvisor/autoIndexing
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2026-01-22”
POST /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/performanceAdvisor/autoIndexing
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2026-01-22”
DELETE /api/atlas/v2/groups/{groupId}/serverless/{name}
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2026-01-22”
PATCH /api/atlas/v2/groups/{groupId}/serverless/{name}
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2026-01-22”
GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在响应中添加了可选属性“results/items/connections/items/state”
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在响应中添加了可选属性“connections/items/state”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在响应中添加了可选属性“connections/items/state”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在响应中添加了可选属性“connections/items/state”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 在响应中添加了可选属性“results/items/state”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 在响应中添加了可选属性“/state, state”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 在响应中添加了可选属性“/state, state”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 在响应中添加了可选属性“/state, state”
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
Updated
  • 在响应中添加了可选属性“connections/items/state”
GET /api/atlas/v2/orgs/{orgId}/activityFeed
已交
  • 已添加端点
GET /api/atlas/v2/skus
已交
  • 已添加端点
GET /api/atlas/v2/skus/{skuId}
已交
  • 已添加端点

2026 年 1 月 21 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“#/components/schemas/MongotuneAlertConfigViewForNdsGroup”添加到响应的“results/items/”响应属性“oneOf”列表中
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“#/components/schemas/MongotuneAlertConfigViewForNdsGroup”添加到请求正文“oneOf”列表
  • 将“#/components/schemas/MongotuneAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“#/components/schemas/MongotuneAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“#/components/schemas/MongotuneAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“#/components/schemas/MongotuneAlertConfigViewForNdsGroup”添加到请求正文“oneOf”列表
  • 将“#/components/schemas/MongotuneAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 将“#/components/schemas/MongotuneAlertConfigViewForNdsGroup”添加到响应的“results/items/”响应属性“oneOf”列表中

2026 年 1 月 16 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性中添加了新的“ACTIVE_LEGACY_TLS_CONNECTIONS”枚举值
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性中添加了新的“ACTIVE_LEGACY_TLS_CONNECTIONS”枚举值
  • 已将新的“ACTIVE_LEGACY_TLS_CONNECTIONS”枚举值添加到请求属性“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #5: Group 事件 Types]/”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性中添加了新的“ACTIVE_LEGACY_TLS_CONNECTIONS”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性中添加了新的“ACTIVE_LEGACY_TLS_CONNECTIONS”枚举值
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性中添加了新的“ACTIVE_LEGACY_TLS_CONNECTIONS”枚举值
  • 已将新的“ACTIVE_LEGACY_TLS_CONNECTIONS”枚举值添加到请求属性“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #5: Group 事件 Types]/”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 将新的“ACTIVE_LEGACY_TLS_CONNECTIONS”枚举值添加到“results/items/oneOf[subschema #7: Any other 警报]/eventTypeName/oneOf[subschema #5: Group 事件类型]/”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 将新的“ACTIVE_LEGACY_TLS_CONNECTIONS”枚举值添加到“results/items/oneOf[subschema #7: Any other 警报]/eventTypeName/oneOf[subschema #5: Group 事件类型]/”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 在“/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性中添加了新的“ACTIVE_LEGACY_TLS_CONNECTIONS”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 在“/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性中添加了新的“ACTIVE_LEGACY_TLS_CONNECTIONS”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 在“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性中添加了新的“ACTIVE_LEGACY_TLS_CONNECTIONS”枚举值
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 在“results/items/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #12: Group Event Types]/”响应属性中添加了新的“ACTIVE_LEGACY_TLS_CONNECTIONS、NO_ACTIVE_LEGACY_TLS_CONNECTIONS”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 在“/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #12: Group Event Types]/”响应属性中添加了新的“ACTIVE_LEGACY_TLS_CONNECTIONS、NO_ACTIVE_LEGACY_TLS_CONNECTIONS”枚举值
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 将新的“AWS_PAYMENT_PAID”枚举值添加到“results/items/oneOf[subschema #6: Billing Events]/eventTypeName”响应属性
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 将新的“AWS_PAYMENT_PAID”枚举值添加到“/oneOf[subschema #6: 计费事件]/事件类型名称”响应属性

2026 年 1 月 15 日发布

GET /api/atlas/v2/groups/{groupId}/serverless
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2026-01-15”
GET /api/atlas/v2/groups/{groupId}/serverless/{name}
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2026-01-15”

2026 年 1 月 08 日发布

PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • 添加了新的可选请求属性“definition/oneOf[subschema #1: 文本搜索索引定义]/sort”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • 添加了新的可选请求属性“definition/oneOf[subschema #1: 文本搜索索引定义]/sort”
GET /api/atlas/v2/groups/{groupId}/integrations
Updated
  • 从“results/items/”响应属性中删除了“S3_LOG_EXPORT”鉴别器映射键
  • 已从响应的“results/items/”响应属性“oneOf”列表中删除了“#/components/schemas/S3LogExport”
GET /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 已从响应状态“200”的响应鉴别器中删除“S3_日志_EXPORT”映射键
  • 已从响应的响应正文“oneOf”列表中删除“#/components/模式/S3LogExport”
POST /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 从请求鉴别器中删除了“S3_LOG_EXPORT”映射键
  • 从“results/items/”响应属性中删除了“S3_LOG_EXPORT”鉴别器映射键
  • 已从响应的“results/items/”响应属性“oneOf”列表中删除了“#/components/schemas/S3LogExport”
PUT /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 从请求鉴别器中删除了“S3_LOG_EXPORT”映射键
  • 从“results/items/”响应属性中删除了“S3_LOG_EXPORT”鉴别器映射键
  • 已从响应的“results/items/”响应属性“oneOf”列表中删除了“#/components/schemas/S3LogExport”
GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 将“SchemaRegistry”鉴别器映射键添加到“results/items/connections/items/”响应属性
  • 将 '#/components/schemas/StreamsSchemaRegistryConnection' 添加到响应的 'results/items/connections/items/' 响应属性'oneOf' 列表
  • 将新的 'SchemaRegistry'枚举值添加到 'results/items/connections/items/type' 响应属性
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 将“SchemaRegistry”鉴别器映射键添加到“connections/items/”请求属性
  • 将 '#/components/schemas/StreamsSchemaRegistryConnection' 添加到 'connections/items/'请求属性'oneOf' 列表
  • 将“SchemaRegistry”鉴别器映射键添加到“connections/items/”响应属性
  • 已将 '#/components/schemas/StreamsSchemaRegistryConnection' 添加到响应的 'connections/items/' 响应属性'oneOf' 列表
  • 将新的 'SchemaRegistry'枚举值添加到 'connections/items/type' 响应属性
  • 将新的“SchemaRegistry”枚举值添加到请求属性“connections/items/type”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 将“SchemaRegistry”鉴别器映射键添加到“connections/items/”响应属性
  • 已将 '#/components/schemas/StreamsSchemaRegistryConnection' 添加到响应的 'connections/items/' 响应属性'oneOf' 列表
  • 将新的 'SchemaRegistry'枚举值添加到 'connections/items/type' 响应属性
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 将“SchemaRegistry”鉴别器映射键添加到“connections/items/”响应属性
  • 已将 '#/components/schemas/StreamsSchemaRegistryConnection' 添加到响应的 'connections/items/' 响应属性'oneOf' 列表
  • 将新的 'SchemaRegistry'枚举值添加到 'connections/items/type' 响应属性
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 将“SchemaRegistry”鉴别器映射键添加到“results/items/”响应属性
  • 将“#/components/schemas/StreamsSchemaRegistryConnection”添加到响应的“results/items/”响应属性“oneOf”列表中
  • 将新的 'SchemaRegistry'枚举值添加到 'results/items/type' 响应属性
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 将“SchemaRegistry”映射键添加到请求鉴别器
  • 将 '#/components/schemas/StreamsSchemaRegistryConnection' 添加到请求正文 'oneOf' 列表
  • 已将“SchemaRegistry”映射键添加到响应状态“200”的响应鉴别器
  • 将“#/components/schemas/StreamsSchemaRegistryConnection”添加到响应的响应正文“oneOf”列表中
  • 已将新的 'SchemaRegistry'枚举值添加到 '/type' 响应属性
  • 已将新的 'SchemaRegistry'枚举值添加到 'type' 响应属性
  • 将新的 'SchemaRegistry'枚举值添加到请求属性'/type'
  • 已将新的 'SchemaRegistry'枚举值添加到请求属性'type'
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 已将“SchemaRegistry”映射键添加到响应状态“200”的响应鉴别器
  • 将“#/components/schemas/StreamsSchemaRegistryConnection”添加到响应的响应正文“oneOf”列表中
  • 已将新的 'SchemaRegistry'枚举值添加到 '/type' 响应属性
  • 已将新的 'SchemaRegistry'枚举值添加到 'type' 响应属性
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 将“SchemaRegistry”映射键添加到请求鉴别器
  • 将 '#/components/schemas/StreamsSchemaRegistryConnection' 添加到请求正文 'oneOf' 列表
  • 已将“SchemaRegistry”映射键添加到响应状态“200”的响应鉴别器
  • 将“#/components/schemas/StreamsSchemaRegistryConnection”添加到响应的响应正文“oneOf”列表中
  • 已将新的 'SchemaRegistry'枚举值添加到 '/type' 响应属性
  • 已将新的 'SchemaRegistry'枚举值添加到 'type' 响应属性
  • 将新的 'SchemaRegistry'枚举值添加到请求属性'/type'
  • 已将新的 'SchemaRegistry'枚举值添加到请求属性'type'
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
Updated
  • 将“SchemaRegistry”鉴别器映射键添加到“connections/items/”响应属性
  • 已将 '#/components/schemas/StreamsSchemaRegistryConnection' 添加到响应的 'connections/items/' 响应属性'oneOf' 列表
  • 将新的 'SchemaRegistry'枚举值添加到 'connections/items/type' 响应属性

2025 年 12 月 15 日发布

PATCH /api/atlas/v2/groups/{groupId}/ 备份/exportBuckets/{exportBucketId}
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/ 备份/{cloudProvider}/privateEndpoints
已交
  • 已添加端点
帖子 /api/atlas/v2/groups/{groupId}/备份/{cloudProvider}/privateEndpoints
已交
  • 已添加端点
删除 /api/atlas/v2/groups/{groupId}/备份/{cloudProvider}/privateEndpoints/{endpointId}
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/ 备份/{cloudProvider}/privateEndpoints/{endpointId}
已交
  • 已添加端点

2025 年 12 月 11 日发布

GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 已从响应的“results/items/”响应属性“oneOf”列表中删除“#/components/schemas/SearchPlannerAuditView”
  • 已从响应的“results/items/oneOf[subschema #1: 任何其他事件]/eventTypeName”响应属性“oneOf”列表中删除“subschema #25: 搜索 Planner Atlas 审核 Types”
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 已从响应的响应正文“oneOf”列表中删除“#/components/schemas/SearchPlannerAuditView”
  • 已从响应的“/oneOf[subschema #1: 其他事件]/eventTypeName”响应属性“oneOf”列表中删除“subschema #25: 搜索 Planner Atlas 审核 类型”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 请求属性“cloudProvider”变为可选属性
  • 请求属性“区域”变为可选

2025 年 12 月 10 日发布

GET /api/atlas/v2/alertConfigs/matchers/fieldNames
Updated
  • 将“subschema #7：全局软件类型匹配器字段”添加到“/items/”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName”响应属性“oneOf”中添加了“subschema #6: Mongotune Event Types”、“subschema #15: Host Event Types”响应列表
  • 将新的“ALERT_HOST_SSH_SESSION_STARTED”枚举值添加到“results/items/oneOf[subschema #8: 托管警报配置]/eventTypeName”响应属性
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“subschema #6: Mongotune Event Types”、“subschema #15: Host Event Types”添加到“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName”请求属性“oneOf”列表
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName”响应属性“oneOf”列表中添加了“subschema #6: Mongotune 事件 Types”、“subschema #15: 托管 事件 Types”响应
  • 将新的“ALERT_HOST_SSH_SESSION_STARTED”枚举值添加到“/oneOf[subschema #8: 托管警报配置]/eventTypeName”响应属性
  • 已将新的“ALERT_HOST_SSH_SESSION_STARTED”枚举值添加到请求属性“/oneOf[subschema #8: 托管警报配置]/eventTypeName”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName”响应属性“oneOf”列表中添加了“subschema #6: Mongotune 事件 Types”、“subschema #15: 托管 事件 Types”响应
  • 将新的“ALERT_HOST_SSH_SESSION_STARTED”枚举值添加到“/oneOf[subschema #8: 托管警报配置]/eventTypeName”响应属性
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName”响应属性“oneOf”列表中添加了“subschema #6: Mongotune 事件 Types”、“subschema #15: 托管 事件 Types”响应
  • 将新的“ALERT_HOST_SSH_SESSION_STARTED”枚举值添加到“/oneOf[subschema #8: 托管警报配置]/eventTypeName”响应属性
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“subschema #6: Mongotune Event Types”、“subschema #15: Host Event Types”添加到“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName”请求属性“oneOf”列表
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName”响应属性“oneOf”列表中添加了“subschema #6: Mongotune 事件 Types”、“subschema #15: 托管 事件 Types”响应
  • 将新的“ALERT_HOST_SSH_SESSION_STARTED”枚举值添加到“/oneOf[subschema #8: 托管警报配置]/eventTypeName”响应属性
  • 已将新的“ALERT_HOST_SSH_SESSION_STARTED”枚举值添加到请求属性“/oneOf[subschema #8: 托管警报配置]/eventTypeName”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 将“subschema #6: Mongotune 事件 Types、subschema #19: 托管 事件 Types”添加到“results/items/oneOf[subschema #7: Any other 警报]/eventTypeName”响应属性“oneOf”列表对于响应
  • 已将新的“ALERT_HOST_SSH_SESSION_STARTED”枚举值添加到“results/items/oneOf[subschema #3: 托管警报]/eventTypeName”响应属性
  • 已将新的“ALERT_HOST_SSH_SESSION_STARTED”枚举添加到“results/items/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 将“subschema #6: Mongotune 事件 Types、subschema #19: 托管 事件 Types”添加到“results/items/oneOf[subschema #7: Any other 警报]/eventTypeName”响应属性“oneOf”列表对于响应
  • 已将新的“ALERT_HOST_SSH_SESSION_STARTED”枚举值添加到“results/items/oneOf[subschema #3: 托管警报]/eventTypeName”响应属性
  • 已将新的“ALERT_HOST_SSH_SESSION_STARTED”枚举添加到“results/items/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“subschema #6：Mongotune Event Types”、“subschema #19：Host Event Types”添加到“/oneOf[subschema #7：Any other Alerts]/eventTypeName”响应属性“oneOf”列表中
  • 已将新的“ALERT_HOST_SSH_SESSION_STARTED”枚举值添加到“/oneOf[subschema #3: 托管警报]/eventTypeName”响应属性
  • 已将新的“ALERT_HOST_SSH_SESSION_STARTED”枚举值添加到“/oneOf[subschema #6: 流处理器警报]/eventTypeName”响应属性
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“subschema #6：Mongotune Event Types”、“subschema #19：Host Event Types”添加到“/oneOf[subschema #7：Any other Alerts]/eventTypeName”响应属性“oneOf”列表中
  • 已将新的“ALERT_HOST_SSH_SESSION_STARTED”枚举值添加到“/oneOf[subschema #3: 托管警报]/eventTypeName”响应属性
  • 已将新的“ALERT_HOST_SSH_SESSION_STARTED”枚举值添加到“/oneOf[subschema #6: 流处理器警报]/eventTypeName”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 在“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName”响应属性“oneOf”中添加了“subschema #6: Mongotune Event Types”、“subschema #15: Host Event Types”响应列表
  • 将新的“ALERT_HOST_SSH_SESSION_STARTED”枚举值添加到“results/items/oneOf[subschema #8: 托管警报配置]/eventTypeName”响应属性
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes
Updated
  • 在响应中添加了可选属性“storedSource”
  • 添加了新的可选请求属性“storedSource”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{databaseName}/{collectionName}
Updated
  • 在响应中添加了可选属性“/items/storedSource”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • 在响应中添加了可选属性“storedSource”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • 在响应中添加了可选属性“storedSource”
  • 添加了新的可选请求属性“storedSource”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/queryShapes
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/集群/{clusterName}/queryShapes/{queryShapeHash}
已交
  • 已添加端点
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/queryShapes/{queryShapeHash}
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes
Updated
  • 在响应中添加了可选属性 '/items/latestDefinition/storedSource, /items/statusDetail/items/mainIndex/definition/storedSource, /items/statusDetail/items/stagedIndex/definition/storedSource'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes
Updated
  • 在响应中添加了可选属性 'latestDefinition/storedSource, statusDetail/items/mainIndex/definition/storedSource, statusDetail/items/stagedIndex/definition/storedSource'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}
Updated
  • 在响应中添加了可选属性 '/items/latestDefinition/storedSource, /items/statusDetail/items/mainIndex/definition/storedSource, /items/statusDetail/items/stagedIndex/definition/storedSource'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • 在响应中添加了可选属性 'latestDefinition/storedSource, statusDetail/items/mainIndex/definition/storedSource, statusDetail/items/stagedIndex/definition/storedSource'
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • 在响应中添加了可选属性 'latestDefinition/storedSource, statusDetail/items/mainIndex/definition/storedSource, statusDetail/items/stagedIndex/definition/storedSource'
  • 添加了新的可选请求属性“definition/oneOf[subschema #2: Vector Search Index Definition]/storedSource”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • 在响应中添加了可选属性 'latestDefinition/storedSource, statusDetail/items/mainIndex/definition/storedSource, statusDetail/items/stagedIndex/definition/storedSource'
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • 在响应中添加了可选属性 'latestDefinition/storedSource, statusDetail/items/mainIndex/definition/storedSource, statusDetail/items/stagedIndex/definition/storedSource'
  • 添加了新的可选请求属性“definition/oneOf[subschema #2: Vector Search Index Definition]/storedSource”
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 在响应中添加了可选属性“azureKeyVault/roleId”
PATCH /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 在响应中添加了可选属性“azureKeyVault/roleId”
  • 添加了新的可选请求属性“azureKeyVault/roleId”
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将“#/components/schemas/SearchPlannerAuditView”添加到响应的“results/items/”响应属性“oneOf”列表中
  • 将“subschema #25：Search Planner Atlas 审核类型、subschema #38：Mongotune 事件类型”添加到“results/items/oneOf[subschema #1：Any other 事件]/eventTypeName”响应属性“oneOf”响应列表
  • 已将新的“ALERT_HOST_SSH_SESSION_STARTED”枚举值添加到“results/items/oneOf[subschema #13: 托管事件]/eventTypeName”响应属性
  • 将新的“CLUSTER_SYSTEMD_OVERRIDES_CHANGED”枚举添加到“results/items/oneOf[subschema #15: NDS Audits]/eventTypeName”响应属性
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 将“#/components/schemas/SearchPlannerAuditView”添加到响应的响应正文“oneOf”列表中
  • 将“subschema #25：搜索 Planner Atlas 审核类型”、“subschema #38：Mongotune 事件类型”添加到“/oneOf[subschema #1：Any other Events]/eventTypeName”响应属性“oneOf”列表中，响应
  • 已将新的“ALERT_HOST_SSH_SESSION_STARTED”枚举值添加到“/oneOf[subschema #13: 托管事件]/eventTypeName”响应属性
  • 将新的 'CLUSTER_SYSTEMD_OVERRIDES_CHANGED' 枚举值添加到 '/oneOf[subschema #15: NDS Audits]/eventTypeName' 响应属性
GET /api/atlas/v2/groups/{groupId}/logIntegrations
已交
  • 已添加端点
帖子 /api/atlas/v2/groups/{groupId}/logIntegrations
已交
  • 已添加端点
删除 /api/atlas/v2/groups/{groupId}/logIntegrations/{id}
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/logIntegrations/{id}
已交
  • 已添加端点
PUT /api/atlas/v2/groups/{groupId}/logIntegrations/{id}
已交
  • 已添加端点
GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • Added the new 'ATLAS_AWS_BACKUP_EXPORT_PRIVATE_ENDPOINT, VOYAGE_EMBEDDING_2_CODE_API_FREE, VOYAGE_EMBEDDING_2_FINANCE_API_FREE, VOYAGE_EMBEDDING_2_LAW_API_FREE, VOYAGE_EMBEDDING_3_5_MULTIMODAL_PIXELS_API_FREE, VOYAGE_EMBEDDING_3_5_MULTIMODAL_TOKENS_API_FREE, VOYAGE_EMBEDDING_3_5_TEXT_API_FREE, VOYAGE_EMBEDDING_3_5_TEXT_LITE_API_FREE, VOYAGE_EMBEDDING_3_CODE_API_FREE, VOYAGE_EMBEDDING_3_MULTIMODAL_PIXELS_API_FREE, VOYAGE_EMBEDDING_3_MULTIMODAL_TOKENS_API_FREE, VOYAGE_EMBEDDING_3_TEXT_API_FREE, VOYAGE_EMBEDDING_3_TEXT_CONTEXT_API_FREE, VOYAGE_EMBEDDING_3_TEXT_LARGE_API_FREE, VOYAGE_EMBEDDING_3_TEXT_LITE_API_FREE, VOYAGE_EMBEDDING_4_TEXT_API_FREE, VOYAGE_EMBEDDING_4_TEXT_LARGE_API_FREE, VOYAGE_EMBEDDING_4_TEXT_LITE_API_FREE, VOYAGE_EMBEDDING_4_TEXT_NANO_API_FREE, VOYAGE_RERANK_2_5_API_FREE, VOYAGE_RERANK_2_5_LITE_API_FREE, VOYAGE_RERANK_2_API_FREE, VOYAGE_RERANK_2_LITE_API_FREE' enum values to the 'results/items/lineItems/items/sku' response property
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
Updated
  • Added the new 'ATLAS_AWS_BACKUP_EXPORT_PRIVATE_ENDPOINT, VOYAGE_EMBEDDING_2_CODE_API_FREE, VOYAGE_EMBEDDING_2_FINANCE_API_FREE, VOYAGE_EMBEDDING_2_LAW_API_FREE, VOYAGE_EMBEDDING_3_5_MULTIMODAL_PIXELS_API_FREE, VOYAGE_EMBEDDING_3_5_MULTIMODAL_TOKENS_API_FREE, VOYAGE_EMBEDDING_3_5_TEXT_API_FREE, VOYAGE_EMBEDDING_3_5_TEXT_LITE_API_FREE, VOYAGE_EMBEDDING_3_CODE_API_FREE, VOYAGE_EMBEDDING_3_MULTIMODAL_PIXELS_API_FREE, VOYAGE_EMBEDDING_3_MULTIMODAL_TOKENS_API_FREE, VOYAGE_EMBEDDING_3_TEXT_API_FREE, VOYAGE_EMBEDDING_3_TEXT_CONTEXT_API_FREE, VOYAGE_EMBEDDING_3_TEXT_LARGE_API_FREE, VOYAGE_EMBEDDING_3_TEXT_LITE_API_FREE, VOYAGE_EMBEDDING_4_TEXT_API_FREE, VOYAGE_EMBEDDING_4_TEXT_LARGE_API_FREE, VOYAGE_EMBEDDING_4_TEXT_LITE_API_FREE, VOYAGE_EMBEDDING_4_TEXT_NANO_API_FREE, VOYAGE_RERANK_2_5_API_FREE, VOYAGE_RERANK_2_5_LITE_API_FREE, VOYAGE_RERANK_2_API_FREE, VOYAGE_RERANK_2_LITE_API_FREE' enum values to the 'lineItems/items/sku' response property

2025 年 12 月 03 日发布

GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • Added the new 'VOYAGE_EMBEDDING_4_TEXT_API, VOYAGE_EMBEDDING_4_TEXT_AUTOEMBED, VOYAGE_EMBEDDING_4_TEXT_LARGE_API, VOYAGE_EMBEDDING_4_TEXT_LARGE_AUTOEMBED, VOYAGE_EMBEDDING_4_TEXT_LITE_API, VOYAGE_EMBEDDING_4_TEXT_LITE_AUTOEMBED, VOYAGE_EMBEDDING_4_TEXT_NANO_API, VOYAGE_EMBEDDING_4_TEXT_NANO_AUTOEMBED' enum values to the 'results/items/lineItems/items/sku' response property
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
Updated
  • Added the new 'VOYAGE_EMBEDDING_4_TEXT_API, VOYAGE_EMBEDDING_4_TEXT_AUTOEMBED, VOYAGE_EMBEDDING_4_TEXT_LARGE_API, VOYAGE_EMBEDDING_4_TEXT_LARGE_AUTOEMBED, VOYAGE_EMBEDDING_4_TEXT_LITE_API, VOYAGE_EMBEDDING_4_TEXT_LITE_AUTOEMBED, VOYAGE_EMBEDDING_4_TEXT_NANO_API, VOYAGE_EMBEDDING_4_TEXT_NANO_AUTOEMBED' enum values to the 'lineItems/items/sku' response property

2025 年 11 月 19 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“#/components/schemas/RawMetricThresholdView、#/components/schemas/DataMetricThresholdView、#/components/schemas/TimeMetricThresholdView”添加到“results/items/oneOf[subschema #3: 应用服务指标警报配置]/metricThreshold”响应的属性“oneOf”列表
  • 在“results/items/oneOf[subschema #8: 托管警报配置]/eventTypeName”响应属性中添加了新的“HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN、HOST_MONGOT_PAUSE_INITIAL_SYNC”枚举值
  • 将新的 'MAINTENANCE_COMPLETED' 枚举值添加到 'results/items/oneOf[subschema #1: Any other 警报配置]/eventTypeName/oneOf[subschema #7: NDS 维护窗口 Atlas 审核类型]/' 属性响应
  • 将新的“十亿像素，百万令牌”枚举值添加到“results/items/oneOf[subschema #11: 副本集警报 Configuration]/threshold/units”响应属性
  • 在“results/items/oneOf[subschema #12：副本集阈值警报配置]/threshold/units”响应属性中添加了新的“十亿像素，百万令牌”枚举值
  • 在“results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold/units”响应属性中添加了新的“十亿像素，百万令牌”枚举值
  • 在“results/items/oneOf[subschema #14: Flex 警报配置]/metricThreshold/units”属性中添加了新的“十亿像素，百万令牌”枚举值
  • 将新的“十亿像素，百万令牌”枚举值添加到“results/items/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold/units”响应属性
  • 将新的“十亿像素，百万令牌”枚举值添加到“results/items/oneOf[subschema #3: 应用 Services Metric Alert Configuration]/metricThreshold/units”响应属性
  • 将新的“十亿像素，百万令牌”枚举值添加到“results/items/oneOf[subschema #9: 托管 指标 警报 Configuration]/metricThreshold/units”响应属性
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将 '#/components/schemas/RawMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/components/schemas/TimeMetricThresholdView' 添加到 '/oneOf[subschema #3: 应用 Services Metric Alert Configuration]/metricThreshold' 请求 属性 ' oneOf' 列表
  • 将 '#/components/schemas/RawMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/components/schemas/TimeMetricThresholdView' 添加到 '/oneOf[subschema #3: App Services Metric Alert Configuration]/metricThreshold' 响应属性' oneOf' 响应列表
  • 在“/oneOf[subschema #8: 托管警报配置]/eventTypeName”响应属性中添加了新的“HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN、HOST_MONGOT_PAUSE_INITIAL_SYNC”枚举值
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #7: NDS 维护窗口 Atlas 审核 Types]/”响应属性中添加了新的“MAINTENANCE_COMPLETED”枚举值
  • 在“/oneOf[subschema #11: 副本集 警报 Configuration]/threshold/units”响应属性中添加了新的“十亿像素，百万令牌”枚举值
  • 将新的“十亿像素，百万令牌”枚举值添加到“/oneOf[subschema #12：副本集阈值警报配置]/threshold/units”响应属性
  • 在“/oneOf[subschema #13: 无服务器 警报 Configuration]/metricThreshold/units”响应属性中添加了新的“十亿像素，百万令牌”枚举值
  • 在“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold/units”响应属性中添加了新的“十亿像素，百万令牌”枚举值
  • 在“/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold/units”响应属性中添加了新的“十亿像素，百万令牌”枚举值
  • 在“/oneOf[subschema #3: App Services Metric Alert Configuration]/metricThreshold/units”响应属性中添加了新的“十亿像素，百万令牌”枚举值
  • 在“/oneOf[subschema #9: 托管 指标 警报 Configuration]/指标Threshold/units” 属性 中添加了新的“十亿像素，百万令牌”枚举值
  • 在请求属性“/oneOf[subschema #8: 托管警报配置]/eventTypeName”中添加了新的“HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN、HOST_MONGOT_PAUSE_INITIAL_SYNC”枚举值
  • 已将新的 'MAINTENANCE_COMPLETED'枚举值添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #7: NDS 维护窗口 Atlas 审核 Types]/'
  • 已将新的“十亿像素，百万令牌”枚举值添加到请求属性“/oneOf[subschema #11: Replica Set Alert Configuration]/threshold/units”
  • 将新的“十亿像素，百万令牌”枚举值添加到请求属性“/oneOf[subschema #12：副本集阈值警报配置]/threshold/units”
  • 在请求属性“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold/units”中添加了新的“十亿像素，百万令牌”枚举值
  • 在请求属性“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold/units”中添加了新的“十亿像素，百万令牌”枚举值
  • 在请求属性“/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold/units”中添加了新的“十亿像素，百万令牌”枚举值
  • 已将新的“十亿像素，百万令牌”枚举值添加到请求属性“/oneOf[subschema #3: 应用 Services Metric Alert Configuration]/metricThreshold/units”
  • 在请求属性“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold/units”中添加了新的“十亿像素，百万令牌”枚举值
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将 '#/components/schemas/RawMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/components/schemas/TimeMetricThresholdView' 添加到 '/oneOf[subschema #3: App Services Metric Alert Configuration]/metricThreshold' 响应属性' oneOf' 响应列表
  • 在“/oneOf[subschema #8: 托管警报配置]/eventTypeName”响应属性中添加了新的“HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN、HOST_MONGOT_PAUSE_INITIAL_SYNC”枚举值
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #7: NDS 维护窗口 Atlas 审核 Types]/”响应属性中添加了新的“MAINTENANCE_COMPLETED”枚举值
  • 在“/oneOf[subschema #11: 副本集 警报 Configuration]/threshold/units”响应属性中添加了新的“十亿像素，百万令牌”枚举值
  • 将新的“十亿像素，百万令牌”枚举值添加到“/oneOf[subschema #12：副本集阈值警报配置]/threshold/units”响应属性
  • 在“/oneOf[subschema #13: 无服务器 警报 Configuration]/metricThreshold/units”响应属性中添加了新的“十亿像素，百万令牌”枚举值
  • 在“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold/units”响应属性中添加了新的“十亿像素，百万令牌”枚举值
  • 在“/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold/units”响应属性中添加了新的“十亿像素，百万令牌”枚举值
  • 在“/oneOf[subschema #3: App Services Metric Alert Configuration]/metricThreshold/units”响应属性中添加了新的“十亿像素，百万令牌”枚举值
  • 在“/oneOf[subschema #9: 托管 指标 警报 Configuration]/指标Threshold/units” 属性 中添加了新的“十亿像素，百万令牌”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将 '#/components/schemas/RawMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/components/schemas/TimeMetricThresholdView' 添加到 '/oneOf[subschema #3: App Services Metric Alert Configuration]/metricThreshold' 响应属性' oneOf' 响应列表
  • 在“/oneOf[subschema #8: 托管警报配置]/eventTypeName”响应属性中添加了新的“HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN、HOST_MONGOT_PAUSE_INITIAL_SYNC”枚举值
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #7: NDS 维护窗口 Atlas 审核 Types]/”响应属性中添加了新的“MAINTENANCE_COMPLETED”枚举值
  • 在“/oneOf[subschema #11: 副本集 警报 Configuration]/threshold/units”响应属性中添加了新的“十亿像素，百万令牌”枚举值
  • 将新的“十亿像素，百万令牌”枚举值添加到“/oneOf[subschema #12：副本集阈值警报配置]/threshold/units”响应属性
  • 在“/oneOf[subschema #13: 无服务器 警报 Configuration]/metricThreshold/units”响应属性中添加了新的“十亿像素，百万令牌”枚举值
  • 在“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold/units”响应属性中添加了新的“十亿像素，百万令牌”枚举值
  • 在“/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold/units”响应属性中添加了新的“十亿像素，百万令牌”枚举值
  • 在“/oneOf[subschema #3: App Services Metric Alert Configuration]/metricThreshold/units”响应属性中添加了新的“十亿像素，百万令牌”枚举值
  • 在“/oneOf[subschema #9: 托管 指标 警报 Configuration]/指标Threshold/units” 属性 中添加了新的“十亿像素，百万令牌”枚举值
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将 '#/components/schemas/RawMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/components/schemas/TimeMetricThresholdView' 添加到 '/oneOf[subschema #3: 应用 Services Metric Alert Configuration]/metricThreshold' 请求 属性 ' oneOf' 列表
  • 将 '#/components/schemas/RawMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/components/schemas/TimeMetricThresholdView' 添加到 '/oneOf[subschema #3: App Services Metric Alert Configuration]/metricThreshold' 响应属性' oneOf' 响应列表
  • 在“/oneOf[subschema #8: 托管警报配置]/eventTypeName”响应属性中添加了新的“HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN、HOST_MONGOT_PAUSE_INITIAL_SYNC”枚举值
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #7: NDS 维护窗口 Atlas 审核 Types]/”响应属性中添加了新的“MAINTENANCE_COMPLETED”枚举值
  • 在“/oneOf[subschema #11: 副本集 警报 Configuration]/threshold/units”响应属性中添加了新的“十亿像素，百万令牌”枚举值
  • 将新的“十亿像素，百万令牌”枚举值添加到“/oneOf[subschema #12：副本集阈值警报配置]/threshold/units”响应属性
  • 在“/oneOf[subschema #13: 无服务器 警报 Configuration]/metricThreshold/units”响应属性中添加了新的“十亿像素，百万令牌”枚举值
  • 在“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold/units”响应属性中添加了新的“十亿像素，百万令牌”枚举值
  • 在“/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold/units”响应属性中添加了新的“十亿像素，百万令牌”枚举值
  • 在“/oneOf[subschema #3: App Services Metric Alert Configuration]/metricThreshold/units”响应属性中添加了新的“十亿像素，百万令牌”枚举值
  • 在“/oneOf[subschema #9: 托管 指标 警报 Configuration]/指标Threshold/units” 属性 中添加了新的“十亿像素，百万令牌”枚举值
  • 在请求属性“/oneOf[subschema #8: 托管警报配置]/eventTypeName”中添加了新的“HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN、HOST_MONGOT_PAUSE_INITIAL_SYNC”枚举值
  • 已将新的 'MAINTENANCE_COMPLETED'枚举值添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #7: NDS 维护窗口 Atlas 审核 Types]/'
  • 已将新的“十亿像素，百万令牌”枚举值添加到请求属性“/oneOf[subschema #11: Replica Set Alert Configuration]/threshold/units”
  • 将新的“十亿像素，百万令牌”枚举值添加到请求属性“/oneOf[subschema #12：副本集阈值警报配置]/threshold/units”
  • 在请求属性“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold/units”中添加了新的“十亿像素，百万令牌”枚举值
  • 在请求属性“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold/units”中添加了新的“十亿像素，百万令牌”枚举值
  • 在请求属性“/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold/units”中添加了新的“十亿像素，百万令牌”枚举值
  • 已将新的“十亿像素，百万令牌”枚举值添加到请求属性“/oneOf[subschema #3: 应用 Services Metric Alert Configuration]/metricThreshold/units”
  • 在请求属性“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold/units”中添加了新的“十亿像素，百万令牌”枚举值
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 在“results/items/oneOf[subschema #3: Host 警报]/eventTypeName”响应属性中添加了新的“HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN、HOST_MONGOT_PAUSE_INITIAL_SYNC”枚举值
  • 在“results/items/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName”响应属性中添加了新的“HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN、HOST_MONGOT_PAUSE_INITIAL_SYNC”枚举值
  • 将新的 'MAINTENANCE_COMPLETED' 枚举值添加到 'results/items/oneOf[subschema #7: 其他警报]/eventTypeName/oneOf[subschema #7: NDS 维护窗口 Atlas 审核类型]/' 属性响应
  • 将新的“十亿像素，百万令牌”枚举值添加到“results/items/oneOf[subschema #4: 托管指标警报]/currentValue/units”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 在“results/items/oneOf[subschema #3: Host 警报]/eventTypeName”响应属性中添加了新的“HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN、HOST_MONGOT_PAUSE_INITIAL_SYNC”枚举值
  • 在“results/items/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName”响应属性中添加了新的“HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN、HOST_MONGOT_PAUSE_INITIAL_SYNC”枚举值
  • 将新的 'MAINTENANCE_COMPLETED' 枚举值添加到 'results/items/oneOf[subschema #7: 其他警报]/eventTypeName/oneOf[subschema #7: NDS 维护窗口 Atlas 审核类型]/' 属性响应
  • 将新的“十亿像素，百万令牌”枚举值添加到“results/items/oneOf[subschema #4: 托管指标警报]/currentValue/units”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 在 '/oneOf[subschema #3: 托管 警报]/eventTypeName' 响应属性中添加了新的 'HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN、HOST_MONGOT_PAUSE_INITIAL_SYNC'枚举值
  • 在 '/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName' 属性中添加了新的 'HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN、HOST_MONGOT_PAUSE_INITIAL_SYNC' 枚举值
  • 在“/oneOf[subschema #7: 其他警报]/eventTypeName/oneOf[subschema #7: NDS 维护窗口 Atlas 审核类型]/”响应属性中添加了新的“MAINTENANCE_COMPLETED”枚举值
  • 在“/oneOf[subschema #4: 托管 指标 警报]/currentValue/units”响应属性中添加了新的“十亿像素，百万令牌”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 在 '/oneOf[subschema #3: 托管 警报]/eventTypeName' 响应属性中添加了新的 'HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN、HOST_MONGOT_PAUSE_INITIAL_SYNC'枚举值
  • 在 '/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName' 属性中添加了新的 'HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN、HOST_MONGOT_PAUSE_INITIAL_SYNC' 枚举值
  • 在“/oneOf[subschema #7: 其他警报]/eventTypeName/oneOf[subschema #7: NDS 维护窗口 Atlas 审核类型]/”响应属性中添加了新的“MAINTENANCE_COMPLETED”枚举值
  • 在“/oneOf[subschema #4: 托管 指标 警报]/currentValue/units”响应属性中添加了新的“十亿像素，百万令牌”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 将“#/components/schemas/RawMetricThresholdView、#/components/schemas/DataMetricThresholdView、#/components/schemas/TimeMetricThresholdView”添加到“results/items/oneOf[subschema #3: 应用服务指标警报配置]/metricThreshold”响应的属性“oneOf”列表
  • 在“results/items/oneOf[subschema #8: 托管警报配置]/eventTypeName”响应属性中添加了新的“HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN、HOST_MONGOT_PAUSE_INITIAL_SYNC”枚举值
  • 将新的 'MAINTENANCE_COMPLETED' 枚举值添加到 'results/items/oneOf[subschema #1: Any other 警报配置]/eventTypeName/oneOf[subschema #7: NDS 维护窗口 Atlas 审核类型]/' 属性响应
  • 将新的“十亿像素，百万令牌”枚举值添加到“results/items/oneOf[subschema #11: 副本集警报 Configuration]/threshold/units”响应属性
  • 在“results/items/oneOf[subschema #12：副本集阈值警报配置]/threshold/units”响应属性中添加了新的“十亿像素，百万令牌”枚举值
  • 在“results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold/units”响应属性中添加了新的“十亿像素，百万令牌”枚举值
  • 在“results/items/oneOf[subschema #14: Flex 警报配置]/metricThreshold/units”属性中添加了新的“十亿像素，百万令牌”枚举值
  • 将新的“十亿像素，百万令牌”枚举值添加到“results/items/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold/units”响应属性
  • 将新的“十亿像素，百万令牌”枚举值添加到“results/items/oneOf[subschema #3: 应用 Services Metric Alert Configuration]/metricThreshold/units”响应属性
  • 将新的“十亿像素，百万令牌”枚举值添加到“results/items/oneOf[subschema #9: 托管 指标 警报 Configuration]/metricThreshold/units”响应属性
GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 将新的“TLS1_3”枚举值添加到“results/items/advancedConfiguration/minimumEnabledTlsProtocol”响应属性
  • 在响应中添加了可选属性“results/items/advancedConfiguration/customOpensslCipherConfigTls13”
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 在“advancedConfiguration/minimumEnabledTlsProtocol”响应属性中添加了新的“TLS1_3”枚举值
  • 已将新的“TLS1_3”枚举值添加到请求属性“advancedConfiguration/minimumEnabledTlsProtocol”
  • 在响应中添加了可选属性“advancedConfiguration/customOpensslCipherConfigTls13”
  • 添加了新的可选请求属性“advancedConfiguration/customOpensslCipherConfigTls13”
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 在“advancedConfiguration/minimumEnabledTlsProtocol”响应属性中添加了新的“TLS1_3”枚举值
  • 已将新的“TLS1_3”枚举值添加到请求属性“advancedConfiguration/minimumEnabledTlsProtocol”
  • 在响应中添加了可选属性“advancedConfiguration/customOpensslCipherConfigTls13”
  • 添加了新的可选请求属性“advancedConfiguration/customOpensslCipherConfigTls13”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 在“advancedConfiguration/minimumEnabledTlsProtocol”响应属性中添加了新的“TLS1_3”枚举值
  • 在响应中添加了可选属性“advancedConfiguration/customOpensslCipherConfigTls13”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 在“advancedConfiguration/minimumEnabledTlsProtocol”响应属性中添加了新的“TLS1_3”枚举值
  • 已将新的“TLS1_3”枚举值添加到请求属性“advancedConfiguration/minimumEnabledTlsProtocol”
  • 在响应中添加了可选属性“advancedConfiguration/customOpensslCipherConfigTls13”
  • 添加了新的可选请求属性“advancedConfiguration/customOpensslCipherConfigTls13”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/outageSimulation
Updated
  • 在响应中添加了可选属性“expirationDate”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/outageSimulation
Updated
  • 在响应中添加了可选属性“expirationDate”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/outageSimulation
Updated
  • 在响应中添加了可选属性“expirationDate”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • 已将新的“TLS1_3”枚举值添加到“minimumEnabledTlsProtocol”响应属性
  • 在响应中添加了可选属性“customOpensslCipherConfigTls13”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • 已将新的“TLS1_3”枚举值添加到“minimumEnabledTlsProtocol”响应属性
  • 已将新的“TLS1_3”枚举值添加到请求属性“minimumEnabledTlsProtocol”
  • 在响应中添加了可选属性“customOpensslCipherConfigTls13”
  • 添加了新的可选请求属性“customOpensslCipherConfigTls13”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs
Updated
  • 在响应中添加了可选属性“results/items/deploymentJobId”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs
Updated
  • 在响应中添加了可选属性“results/items/deploymentJobId”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs/{jobId}
Updated
  • 在响应中添加了可选属性“deploymentJobId”
GET /api/atlas/v2/groups/{groupId}/containers
Updated
  • 将新的“CHILE_CENTRAL、INDONESIA_CENTRAL、MALAYSIA_WEST”枚举值添加到“results/items/oneOf[subschema #1: AZURE]/区域”响应属性
POST /api/atlas/v2/groups/{groupId}/containers
Updated
  • 将新的“CHILE_CENTRAL、INDONESIA_CENTRAL、MALAYSIA_WEST”枚举值添加到“/oneOf[subschema #1: AZURE]/区域”响应属性
  • 已将新的“CHILE_CENTRAL、INDONESIA_CENTRAL、MALAYSIA_WEST”枚举值添加到请求属性“/oneOf[subschema #1: AZURE]/区域”
GET /api/atlas/v2/groups/{groupId}/containers/all
Updated
  • 将新的“CHILE_CENTRAL、INDONESIA_CENTRAL、MALAYSIA_WEST”枚举值添加到“results/items/oneOf[subschema #1: AZURE]/区域”响应属性
GET /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 将新的“CHILE_CENTRAL、INDONESIA_CENTRAL、MALAYSIA_WEST”枚举值添加到“/oneOf[subschema #1: AZURE]/区域”响应属性
PATCH /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 将新的“CHILE_CENTRAL、INDONESIA_CENTRAL、MALAYSIA_WEST”枚举值添加到“/oneOf[subschema #1: AZURE]/区域”响应属性
  • 已将新的“CHILE_CENTRAL、INDONESIA_CENTRAL、MALAYSIA_WEST”枚举值添加到请求属性“/oneOf[subschema #1: AZURE]/区域”
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 在'results/items/oneOf[subspan 属性 ="15:
  • 在“results/items/oneOf[subschema #13: 托管事件]/eventTypeName”响应属性中添加了新的“HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN、HOST_EXTERNAL_LOG_SINK_EXPORT_RESUMED、HOST_MONGOT_PAUSE_INITIAL_SYNC、HOST_MONGOT_UNPAUSE_INITIAL_SYNC”枚举值
  • 将新的 'MAINTENANCE_COMPLETED'枚举值添加到 'results/items/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #17: NDS 维护窗口 Atlas 审核 Types]/' 响应属性
  • 将新的“十亿像素，百万令牌”枚举值添加到“results/items/oneOf[subschema #14: 托管指标事件]/currentValue/units”响应属性
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 在 '/oneOf[subschema #15: NDS 审核]/eventTypeName' 响应属性中添加了新的 'CLUSTER_INSTANCE_SWAPPED、CLUSTER_INSTANCE_SWAP_CLEARED、CLUSTER_INSTANCE_VM_REBOOT_CLEARED、MONITORING_AGENT_REBALANCE_FLAG、MONITORING_AGENT_REBALANCE_TRIGGERED、SHADOW_CLUSTER_REPLAY_STATUS_UPDATE' 枚举值
  • 在 '/oneOf[subschema #13: 托管事件]/eventTypeName' 响应属性中添加了新的 'HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN、HOST_EXTERNAL_LOG_SINK_EXPORT_RESUMED、HOST_MONGOT_PAUSE_INITIAL_SYNC、HOST_MONGOT_UNPAUSE_INITIAL_SYNC'枚举值
  • 将新的 'MAINTENANCE_COMPLETED'枚举值添加到 '/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #17: NDS 维护窗口Atlas 审核类型]/' 响应属性
  • 将新的“十亿像素，百万令牌”枚举值添加到“/oneOf[subschema #14: 托管 指标 事件]/currentValue/units”响应属性
POST /api/atlas/v2/groups/{groupId}/flexClusters:tenantUpgrade
Updated
  • 已将新的“TLS1_3”枚举值添加到请求属性“advancedConfiguration/minimumEnabledTlsProtocol”
  • 添加了新的可选请求属性“advancedConfiguration/customOpensslCipherConfigTls13”
GET /api/atlas/v2/groups/{groupId}/integrations
Updated
  • 将“S3_LOG_EXPORT”鉴别器映射键添加到“results/items/”响应属性
  • 将“#/components/schemas/S3LogExport”添加到了响应的“results/items/”响应属性“oneOf”列表
  • 已将新的“S3_LOG_EXPORT”枚举值添加到“results/items/type”响应属性中
DELETE /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 已将新的枚举值“S3_LOG_EXPORT”添加到“path”请求参数“integrationType”中
GET /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 已将“S3_LOG_EXPORT”映射键添加到响应状态“200”的响应鉴别器
  • 已将“#/components/模式/S3LogExport”添加到响应的响应正文“oneOf”列表中
  • 在“type”响应属性中添加了新的“S3_LOG_EXPORT”枚举值
  • 已将新的枚举值“S3_LOG_EXPORT”添加到“path”请求参数“integrationType”中
POST /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 已将“S3_LOG_EXPORT”映射键添加到请求鉴别器
  • 将“#/components/schemas/S3LogExport”添加到请求正文“oneOf”列表
  • 将“S3_LOG_EXPORT”鉴别器映射键添加到“results/items/”响应属性
  • 将“#/components/schemas/S3LogExport”添加到了响应的“results/items/”响应属性“oneOf”列表
  • 已将新的“S3_LOG_EXPORT”枚举值添加到“results/items/type”响应属性中
  • 已将新的枚举值“S3_LOG_EXPORT”添加到“path”请求参数“integrationType”中
  • 已将新的“S3_LOG_EXPORT”枚举值添加到请求属性“type”中
PUT /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 已将“S3_LOG_EXPORT”映射键添加到请求鉴别器
  • 将“#/components/schemas/S3LogExport”添加到请求正文“oneOf”列表
  • 将“S3_LOG_EXPORT”鉴别器映射键添加到“results/items/”响应属性
  • 将“#/components/schemas/S3LogExport”添加到了响应的“results/items/”响应属性“oneOf”列表
  • 已将新的“S3_LOG_EXPORT”枚举值添加到“results/items/type”响应属性中
  • 已将新的枚举值“S3_LOG_EXPORT”添加到“path”请求参数“integrationType”中
  • 已将新的“S3_LOG_EXPORT”枚举值添加到请求属性“type”中
GET /api/atlas/v2/groups/{groupId}/teams
Updated
  • 响应属性“results/items/roleNames、results/items/teamId”变为必填项
POST /api/atlas/v2/groups/{groupId}/teams
Updated
  • 响应属性“results/items/roleNames、results/items/teamId”变为必填项
GET / API/ Atlas/v2/groups/{groupId}/teams/{teamId}
Updated
  • 响应属性“roleNames, teamId”变为必填项
PATCH /api/atlas/v2/groups/{groupId}/teams/{teamId}
Updated
  • 响应属性“results/items/roleNames、results/items/teamId”变为必填项
POST /api/atlas/v2/orgs/{orgId}/billing/costExplorer/usage
Updated
  • 已将新的“AI模型、自动嵌入”枚举值添加到请求属性“services/items/”
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 在“results/items/oneOf[subschema #6: 计费事件]/eventTypeName”响应属性中添加了新的“ADMIN_OVERRIDE_PAYMENT_METHOD_DELETED, CREDIT_MOVED”枚举值
  • 在“results/items/oneOf[subschema #8: Org Events]/eventTypeName”响应属性中添加了新的“ORG_BANK_ACCOUNT_ADDED、ORG_BANK_ACCOUNT_UPDATED、ORG_WALLET_ADDED、ORG_WALLET_UPDATED”枚举值
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 在“/oneOf[subschema #6: 计费事件]/eventTypeName”响应属性中添加了新的“ADMIN_OVERRIDE_PAYMENT_METHOD_DELETED, CREDIT_MOVED”枚举值
  • 在“/oneOf[subschema #8: 组织事件]/eventTypeName”响应属性中添加了新的“ORG_BANK_ACCOUNT_ADDED、ORG_BANK_ACCOUNT_UPDATED、ORG_WALLET_ADDED、ORG_WALLET_UPDATED”枚举值
GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • Added the new 'VOYAGE_EMBEDDING_2_CODE_API, VOYAGE_EMBEDDING_2_CODE_AUTOEMBED, VOYAGE_EMBEDDING_2_FINANCE_API, VOYAGE_EMBEDDING_2_FINANCE_AUTOEMBED, VOYAGE_EMBEDDING_2_LAW_API, VOYAGE_EMBEDDING_2_LAW_AUTOEMBED, VOYAGE_EMBEDDING_3_5_MULTIMODAL_PIXELS_API, VOYAGE_EMBEDDING_3_5_MULTIMODAL_PIXELS_AUTOEMBED, VOYAGE_EMBEDDING_3_5_MULTIMODAL_TOKENS_API, VOYAGE_EMBEDDING_3_5_MULTIMODAL_TOKENS_AUTOEMBED, VOYAGE_EMBEDDING_3_5_TEXT_API, VOYAGE_EMBEDDING_3_5_TEXT_AUTOEMBED, VOYAGE_EMBEDDING_3_5_TEXT_LITE_API, VOYAGE_EMBEDDING_3_5_TEXT_LITE_AUTOEMBED, VOYAGE_EMBEDDING_3_CODE_API, VOYAGE_EMBEDDING_3_CODE_AUTOEMBED, VOYAGE_EMBEDDING_3_MULTIMODAL_PIXELS_API, VOYAGE_EMBEDDING_3_MULTIMODAL_PIXELS_AUTOEMBED, VOYAGE_EMBEDDING_3_MULTIMODAL_TOKENS_API, VOYAGE_EMBEDDING_3_MULTIMODAL_TOKENS_AUTOEMBED, VOYAGE_EMBEDDING_3_TEXT_API, VOYAGE_EMBEDDING_3_TEXT_AUTOEMBED, VOYAGE_EMBEDDING_3_TEXT_CONTEXT_API, VOYAGE_EMBEDDING_3_TEXT_CONTEXT_AUTOEMBED, VOYAGE_EMBEDDING_3_TEXT_LARGE_API, VOYAGE_EMBEDDING_3_TEXT_LARGE_AUTOEMBED, VOYAGE_EMBEDDING_3_TEXT_LITE_API, VOYAGE_EMBEDDING_3_TEXT_LITE_AUTOEMBED, VOYAGE_RERANK_2_5_API, VOYAGE_RERANK_2_5_LITE_API, VOYAGE_RERANK_2_API, VOYAGE_RERANK_2_LITE_API' enum values to the 'results/items/lineItems/items/sku' response property
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
Updated
  • Added the new 'VOYAGE_EMBEDDING_2_CODE_API, VOYAGE_EMBEDDING_2_CODE_AUTOEMBED, VOYAGE_EMBEDDING_2_FINANCE_API, VOYAGE_EMBEDDING_2_FINANCE_AUTOEMBED, VOYAGE_EMBEDDING_2_LAW_API, VOYAGE_EMBEDDING_2_LAW_AUTOEMBED, VOYAGE_EMBEDDING_3_5_MULTIMODAL_PIXELS_API, VOYAGE_EMBEDDING_3_5_MULTIMODAL_PIXELS_AUTOEMBED, VOYAGE_EMBEDDING_3_5_MULTIMODAL_TOKENS_API, VOYAGE_EMBEDDING_3_5_MULTIMODAL_TOKENS_AUTOEMBED, VOYAGE_EMBEDDING_3_5_TEXT_API, VOYAGE_EMBEDDING_3_5_TEXT_AUTOEMBED, VOYAGE_EMBEDDING_3_5_TEXT_LITE_API, VOYAGE_EMBEDDING_3_5_TEXT_LITE_AUTOEMBED, VOYAGE_EMBEDDING_3_CODE_API, VOYAGE_EMBEDDING_3_CODE_AUTOEMBED, VOYAGE_EMBEDDING_3_MULTIMODAL_PIXELS_API, VOYAGE_EMBEDDING_3_MULTIMODAL_PIXELS_AUTOEMBED, VOYAGE_EMBEDDING_3_MULTIMODAL_TOKENS_API, VOYAGE_EMBEDDING_3_MULTIMODAL_TOKENS_AUTOEMBED, VOYAGE_EMBEDDING_3_TEXT_API, VOYAGE_EMBEDDING_3_TEXT_AUTOEMBED, VOYAGE_EMBEDDING_3_TEXT_CONTEXT_API, VOYAGE_EMBEDDING_3_TEXT_CONTEXT_AUTOEMBED, VOYAGE_EMBEDDING_3_TEXT_LARGE_API, VOYAGE_EMBEDDING_3_TEXT_LARGE_AUTOEMBED, VOYAGE_EMBEDDING_3_TEXT_LITE_API, VOYAGE_EMBEDDING_3_TEXT_LITE_AUTOEMBED, VOYAGE_RERANK_2_5_API, VOYAGE_RERANK_2_5_LITE_API, VOYAGE_RERANK_2_API, VOYAGE_RERANK_2_LITE_API' enum values to the 'lineItems/items/sku' response property
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}/lineItems:search
Updated
  • 在请求属性“过滤器/skuServices/items/”中添加了新的“AI模型、自动嵌入”枚举值

2025 年 11 月 10 日发布

GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在“results/items/streamConfig/ 层级”响应属性中添加了新的“SP2、SP5、SP50”枚举值
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 已将新的“SP2、SP5、SP50”枚举值添加到“streamConfig/ 层级”响应属性
  • 已将新的“SP2、SP5、SP50”枚举值添加到请求属性“streamConfig/ 层级”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 已将新的“SP2、SP5、SP50”枚举值添加到“streamConfig/ 层级”响应属性
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 已将新的“SP2、SP5、SP50”枚举值添加到“streamConfig/ 层级”响应属性
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}
Updated
  • 在响应中添加了可选属性“层级”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}
Updated
  • 在响应中添加了可选属性“层级”
POST / API/ Atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}:startWith
Updated
  • 添加了状态为“400”的不成功响应
  • 添加了新的可选请求属性“层级”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processors
Updated
  • 在响应中添加了可选属性“results/items/ 层级”
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
Updated
  • 已将新的“SP2、SP5、SP50”枚举值添加到“streamConfig/ 层级”响应属性

2025 年 11 月 04 日发布

GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“results/items/复制规范/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 复制规范]/regionName/oneOf[subschema #1: AWS Regions]/' 响应属性
  • 将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 复制规格]/regionName/oneOf[subschema #1: AWS Regions]/”响应属性
  • 已将新的 'AP_EAST_2、AP_SOUTHEAST_6' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/regionName/oneOf[subschema #1: AWS 区域]/' 响应属性
  • 将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #4：租户区域复制规范]/regionName/oneOf[subschema” #1: AWS Regions]/' 响应属性
  • 将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“results/items/replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #1: AWS 区域]/”响应属性
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 已将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域 ReplicationSpecifications]/regionName/oneOf[subschema #1: AWS 区域]/”响应属性
  • 将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/regionName/oneOf[subschema #1： AWS 区域]/”响应属性
  • 已将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3/GCP区域复制规范]/regionName/oneOf[subschema #1/AWS Regions]/”响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/regionName/oneOf[subschema #1 中添加了新的 'AP_EAST_2、AP_SOUTHEAST_6'枚举值: AWS Regions]/' 响应属性
  • 将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #1: AWS 区域]/”响应属性
  • 已将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 复制规范]/regionName/oneOf[subschema #1: AWS 区域]/”
  • 已将新的 'AP_EAST_2、AP_SOUTHEAST_6' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 复制规范]/regionName/oneOf[subschema #1: AWS 区域]/'
  • 已将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/regionName/oneOf[subschema #1: AWS 区域]/'
  • 已将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #4”：租户区域复制规范]/regionName/oneOf[subschema #1: AWS 区域]/'
  • 已将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #1: AWS 区域]/”
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 在“providerSettings/oneOf[subschema #1: Cloud Service Provider Settings for a Cluster]/regionName”响应属性中添加了新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值
  • 在请求属性“providerSettings/oneOf[subschema #1: 云 Service 提供商 Settings for a 集群]/regionName”中添加了新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 已将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域 ReplicationSpecifications]/regionName/oneOf[subschema #1: AWS 区域]/”响应属性
  • 将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/regionName/oneOf[subschema #1： AWS 区域]/”响应属性
  • 已将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3/GCP区域复制规范]/regionName/oneOf[subschema #1/AWS Regions]/”响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/regionName/oneOf[subschema #1 中添加了新的 'AP_EAST_2、AP_SOUTHEAST_6'枚举值: AWS Regions]/' 响应属性
  • 将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #1: AWS 区域]/”响应属性
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 已将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 区域 ReplicationSpecifications]/regionName/oneOf[subschema #1: AWS 区域]/”响应属性
  • 将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/regionName/oneOf[subschema #1： AWS 区域]/”响应属性
  • 已将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3/GCP区域复制规范]/regionName/oneOf[subschema #1/AWS Regions]/”响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/regionName/oneOf[subschema #1 中添加了新的 'AP_EAST_2、AP_SOUTHEAST_6'枚举值: AWS Regions]/' 响应属性
  • 将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #1: AWS 区域]/”响应属性
  • 已将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 复制规范]/regionName/oneOf[subschema #1: AWS 区域]/”
  • 已将新的 'AP_EAST_2、AP_SOUTHEAST_6' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 复制规范]/regionName/oneOf[subschema #1: AWS 区域]/'
  • 已将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/regionName/oneOf[subschema #1: AWS 区域]/'
  • 已将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #4”：租户区域复制规范]/regionName/oneOf[subschema #1: AWS 区域]/'
  • 已将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #1: AWS 区域]/”
GET /api/atlas/v2/groups/{groupId}/containers
Updated
  • 将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“results/items/oneOf[subschema #3: AWS]/regionName”响应属性
POST /api/atlas/v2/groups/{groupId}/containers
Updated
  • 将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“/oneOf[subschema #3: AWS]/regionName”响应属性
  • 已将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到请求属性“/oneOf[subschema #3: AWS]/regionName”
GET /api/atlas/v2/groups/{groupId}/containers/all
Updated
  • 将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“results/items/oneOf[subschema #3: AWS]/regionName”响应属性
GET /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“/oneOf[subschema #3: AWS]/regionName”响应属性
PATCH /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“/oneOf[subschema #3: AWS]/regionName”响应属性
  • 已将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到请求属性“/oneOf[subschema #3: AWS]/regionName”
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“awsKms/区域”响应属性
PATCH /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“awsKms/区域”响应属性
  • 已将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到请求属性“awsKms/区域”
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
Updated
  • 将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“results/items/oneOf[subschema #1: Azure Key Vault EAR 私有端点]/regionName/oneOf[subschema #2: AWS Regions]/”属性响应中
  • 在“results/items/oneOf[subschema #2: AWS Key Management Service EAR Private Endpoint]/regionName/oneOf[subschema #2”中添加了新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值： AWS Regions]/' 响应属性
  • 将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“results/items/regionName/oneOf[subschema #2: AWS 区域]/”响应属性
POST /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
Updated
  • 将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“/oneOf[subschema #1: Azure Key Vault EAR 私有端点]/regionName/oneOf[subschema #2: AWS 区域]/”响应属性
  • 将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“/oneOf[subschema #2: AWS Key Management Service EAR 私有端点]/regionName/oneOf[subschema #2: AWS 区域]/”响应属性
  • 将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“regionName/oneOf[subschema #2: AWS 区域]/”响应属性
  • 已将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到请求属性“/oneOf[subschema #1: Azure Key Vault EAR 私有端点]/regionName/oneOf[subschema #2: AWS 区域]/”
  • 已将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举添加到请求属性“/oneOf[subschema #2: AWS Key Management Service EAR 私有端点]/regionName/oneOf[subschema #2: AWS 区域]/”
  • 已将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到请求属性“regionName/oneOf[subschema #2: AWS 区域]/”
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints/{endpointId}
Updated
  • 将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“/oneOf[subschema #1: Azure Key Vault EAR 私有端点]/regionName/oneOf[subschema #2: AWS 区域]/”响应属性
  • 将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“/oneOf[subschema #2: AWS Key Management Service EAR 私有端点]/regionName/oneOf[subschema #2: AWS 区域]/”响应属性
  • 将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到“regionName/oneOf[subschema #2: AWS 区域]/”响应属性
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将新的“STREAM_TENANT_OPERATIONAL_LOGS”枚举添加到“results/items/oneOf[subschema #15: NDS Audits]/eventTypeName”响应属性
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 将新的“STREAM_TENANT_OPERATIONAL_LOGS”枚举添加到“/oneOf[subschema #15: NDS Audits]/eventTypeName”属性响应中
POST /api/atlas/v2/groups/{groupId}/flexClusters:tenantUpgrade
Updated
  • 已将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 复制规范]/regionName/oneOf[subschema #1: AWS 区域]/”
  • 已将新的 'AP_EAST_2、AP_SOUTHEAST_6' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 复制规范]/regionName/oneOf[subschema #1: AWS 区域]/'
  • 已将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/regionName/oneOf[subschema #1: AWS 区域]/'
  • 已将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #4”：租户区域复制规范]/regionName/oneOf[subschema #1: AWS 区域]/'
  • 已将新的“AP_EAST_2、AP_SOUTHEAST_6”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #1: AWS 区域]/”

2025 年 10 月23 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在“results/items/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #12: NDS 自动伸缩 Atlas 审核 Types]/”响应属性中添加了新的“CLUSTER_AUTO_SHARDING_INITIATED”枚举值
  • 将新的“CPS_COLLECTION_RESTORE_CANCELED、CPS_COLLECTION_RESTORE_FAILED、CPS_COLLECTION_RESTORE_PARTIAL_SUCCESS、CPS_COLLECTION_RESTORE_SUCCESSFUL”枚举值添加到“results/items/oneOf[subschema #1: Any Other 警报 配置]/eventTypeName/oneOf[subschema #2: Cps 备份 事件 类型]”属性
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将新的 'CLUSTER_AUTO_SHARDING_INITIATED'枚举值添加到 '/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #12: NDS Auto Scaling Atlas 审核 Types]/' 响应属性
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #2: Cps 备份 事件 Types]/”响应中添加了新的“CPS_COLLECTION_RESTORE_CANCELED、CPS_COLLECTION_RESTORE_FAILED、CPS_COLLECTION_RESTORE_PARTIAL_SUCCESS、CPS_COLLECTION_RESTORE_SUCCESSFUL”枚举值属性
  • 已将新的 'CLUSTER_AUTO_SHARDING_INITIATED'枚举值添加到请求属性'/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #12: NDS 自动伸缩 Atlas 审核 Types]/'
  • 在请求属性'/oneOf[subschema #1: Any other 警报 配置]/eventTypeName/oneOf[subschema #2: Cps 备份 事件 类型]/ 中添加了新的 'CPS_COLLECTION_RESTORE_CANCELED、CPS_COLLECTION_RESTORE_FAILED、CPS_COLLECTION_RESTORE_PARTIAL_SUCCESS、CPS_COLLECTION_RESTORE_SUCCESSFUL'枚举值
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将新的 'CLUSTER_AUTO_SHARDING_INITIATED'枚举值添加到 '/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #12: NDS Auto Scaling Atlas 审核 Types]/' 响应属性
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #2: Cps 备份 事件 Types]/”响应中添加了新的“CPS_COLLECTION_RESTORE_CANCELED、CPS_COLLECTION_RESTORE_FAILED、CPS_COLLECTION_RESTORE_PARTIAL_SUCCESS、CPS_COLLECTION_RESTORE_SUCCESSFUL”枚举值属性
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将新的 'CLUSTER_AUTO_SHARDING_INITIATED'枚举值添加到 '/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #12: NDS Auto Scaling Atlas 审核 Types]/' 响应属性
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #2: Cps 备份 事件 Types]/”响应中添加了新的“CPS_COLLECTION_RESTORE_CANCELED、CPS_COLLECTION_RESTORE_FAILED、CPS_COLLECTION_RESTORE_PARTIAL_SUCCESS、CPS_COLLECTION_RESTORE_SUCCESSFUL”枚举值属性
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将新的 'CLUSTER_AUTO_SHARDING_INITIATED'枚举值添加到 '/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #12: NDS Auto Scaling Atlas 审核 Types]/' 响应属性
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #2: Cps 备份 事件 Types]/”响应中添加了新的“CPS_COLLECTION_RESTORE_CANCELED、CPS_COLLECTION_RESTORE_FAILED、CPS_COLLECTION_RESTORE_PARTIAL_SUCCESS、CPS_COLLECTION_RESTORE_SUCCESSFUL”枚举值属性
  • 已将新的 'CLUSTER_AUTO_SHARDING_INITIATED'枚举值添加到请求属性'/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #12: NDS 自动伸缩 Atlas 审核 Types]/'
  • 在请求属性'/oneOf[subschema #1: Any other 警报 配置]/eventTypeName/oneOf[subschema #2: Cps 备份 事件 类型]/ 中添加了新的 'CPS_COLLECTION_RESTORE_CANCELED、CPS_COLLECTION_RESTORE_FAILED、CPS_COLLECTION_RESTORE_PARTIAL_SUCCESS、CPS_COLLECTION_RESTORE_SUCCESSFUL'枚举值
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 将新的 'CLUSTER_AUTO_SHARDING_INITIATED'枚举添加到 'results/items/oneOf[subschema #7: Any other 警报]/eventTypeName/oneOf[subschema #15: NDS 自动伸缩 Atlas 审核 Types]/' 属性
  • 已将新的“CPS_COLLECTION_RESTORE_CANCELED、CPS_COLLECTION_RESTORE_FAILED、CPS_COLLECTION_RESTORE_PARTIAL_SUCCESS、CPS_COLLECTION_RESTORE_SUCCESSFUL”枚举值添加到“results/items/oneOf[subschema #7: 其他警报]/eventTypeName/oneOf[subschema #2: Cps 备份事件类型]/”属性
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 将新的 'CLUSTER_AUTO_SHARDING_INITIATED'枚举添加到 'results/items/oneOf[subschema #7: Any other 警报]/eventTypeName/oneOf[subschema #15: NDS 自动伸缩 Atlas 审核 Types]/' 属性
  • 已将新的“CPS_COLLECTION_RESTORE_CANCELED、CPS_COLLECTION_RESTORE_FAILED、CPS_COLLECTION_RESTORE_PARTIAL_SUCCESS、CPS_COLLECTION_RESTORE_SUCCESSFUL”枚举值添加到“results/items/oneOf[subschema #7: 其他警报]/eventTypeName/oneOf[subschema #2: Cps 备份事件类型]/”属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将新的 'CLUSTER_AUTO_SHARDING_INITIATED' 枚举值添加到 '/oneOf[subschema #7: 其他警报]/eventTypeName/oneOf[subschema #15: NDS 自动伸缩 Atlas 审核 类型]/' 响应属性
  • 在“/oneOf[subschema #7: 任何其他警报]/eventTypeName/oneOf[subschema #2: Cps 备份事件类型]/”响应属性中添加了新的“CPS_COLLECTION_RESTORE_CANCELED、CPS_COLLECTION_RESTORE_FAILED、CPS_COLLECTION_RESTORE_PARTIAL_SUCCESS、CPS_COLLECTION_RESTORE_SUCCESSFUL”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将新的 'CLUSTER_AUTO_SHARDING_INITIATED' 枚举值添加到 '/oneOf[subschema #7: 其他警报]/eventTypeName/oneOf[subschema #15: NDS 自动伸缩 Atlas 审核 类型]/' 响应属性
  • 在“/oneOf[subschema #7: 任何其他警报]/eventTypeName/oneOf[subschema #2: Cps 备份事件类型]/”响应属性中添加了新的“CPS_COLLECTION_RESTORE_CANCELED、CPS_COLLECTION_RESTORE_FAILED、CPS_COLLECTION_RESTORE_PARTIAL_SUCCESS、CPS_COLLECTION_RESTORE_SUCCESSFUL”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 在“results/items/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #12: NDS 自动伸缩 Atlas 审核 Types]/”响应属性中添加了新的“CLUSTER_AUTO_SHARDING_INITIATED”枚举值
  • 将新的“CPS_COLLECTION_RESTORE_CANCELED、CPS_COLLECTION_RESTORE_FAILED、CPS_COLLECTION_RESTORE_PARTIAL_SUCCESS、CPS_COLLECTION_RESTORE_SUCCESSFUL”枚举值添加到“results/items/oneOf[subschema #1: Any Other 警报 配置]/eventTypeName/oneOf[subschema #2: Cps 备份 事件 类型]”属性
GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 添加了新的可选“标头”请求参数“Use-Effective-Instance-Fields”
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 添加了新的可选“标头”请求参数“Use-Effective-Instance-Fields”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 添加了新的可选“标头”请求参数“Use-Effective-Instance-Fields”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 添加了新的可选“标头”请求参数“Use-Effective-Instance-Fields”
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将新的 'CLUSTER_AUTO_SHARDING_INITIATED' 枚举值添加到 'results/items/oneOf[subschema #16: NDS 自动伸缩 Audits]/eventTypeName' 响应属性
  • Added the new 'CLUSTER_IMPORT_FAILED, DEPUTY_SETTINGS_UPDATED, PLAN_APPROVED, PLAN_DECLINED, PREDICTIVE_AUTOSCALING_DISABLED, PREDICTIVE_AUTOSCALING_ENABLED, SHADOW_CLUSTER_CREATE_EXPOSURE, SHADOW_CLUSTER_DELETE_EXPOSURE, SHADOW_CLUSTER_RECORDING_STATUS_UPDATE' 枚举 values to the 'results/items/oneOf[subschema #15: NDS Audits]/eventTypeName' response 属性
  • 在'results/items/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #5: Cps Backup Event Types/ ' 响应属性
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 将新的 'CLUSTER_AUTO_SHARDING_INITIATED' 枚举值添加到 '/oneOf[subschema #16: NDS 自动伸缩审核]/eventTypeName' 响应属性
  • Added the new 'CLUSTER_IMPORT_FAILED, DEPUTY_SETTINGS_UPDATED, PLAN_APPROVED, PLAN_DECLINED, PREDICTIVE_AUTOSCALING_DISABLED, PREDICTIVE_AUTOSCALING_ENABLED, SHADOW_CLUSTER_CREATE_EXPOSURE, SHADOW_CLUSTER_DELETE_EXPOSURE, SHADOW_CLUSTER_RECORDING_STATUS_UPDATE' 枚举 values to the '/oneOf[subschema #15: NDS Audits]/eventTypeName' response 属性
  • 在“/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #5: Cps Backup Event Types]/”响应属性中添加了新的“CPS_COLLECTION_RESTORE_CANCELED、CPS_COLLECTION_RESTORE_FAILED、CPS_COLLECTION_RESTORE_PARTIAL_SUCCESS、CPS_COLLECTION_RESTORE_SUCCESSFUL”枚举值
GET /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections
Updated
  • 在响应中添加了可选属性“results/items/gcpConnectionIds”
POST /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections
Updated
  • 在响应中添加了可选属性“gcpConnectionIds”
  • 添加了新的可选请求属性“gcpConnectionIds”
GET /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections/{connectionId}
Updated
  • 在响应中添加了可选属性“gcpConnectionIds”
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 在“results/items/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #4: 合作事件类型]/”响应属性中添加了新的“AWS_PAYMENT_PAID”枚举值
  • 在“results/items/oneOf[subschema #8: Org Events]/eventTypeName”响应属性中添加了新的“ORGANIZATION_VOYAGE_SETTINGS_CREATED”、“ORGANIZATION_VOYAGE_SETTINGS_DELETED”枚举值
  • 在“results/items/oneOf[subschema #7: NDS Audits]/eventTypeName”响应属性中添加了新的“SHADOW_CLUSTER_ORG_OPT_IN、SHADOW_CLUSTER_ORG_OPT_OUT”枚举值
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 将新的 'AWS_PAYMENT_PAID'枚举值添加到 '/oneOf[subschema #1: 其他事件]/eventTypeName/oneOf[subschema #4: 合作事件类型]/' 响应属性
  • 将新的“ORGANIZATION_VOYAGE_SETTINGS_CREATED”、“ORGANIZATION_VOYAGE_SETTINGS_DELETED”枚举添加到“/oneOf[subschema #8: Org Events]/eventTypeName”响应属性中
  • 在 '/oneOf[subschema #7: NDS Audits]/eventTypeName' 响应属性中添加了新的 'SHADOW_CLUSTER_ORG_OPT_IN、SHADOW_CLUSTER_ORG_OPT_OUT' 枚举值
GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • Added the new 'ATLAS_AWS_STREAM_PROCESSING_DATA_TRANSFER_DIFFERENT_REGION, ATLAS_AWS_STREAM_PROCESSING_DATA_TRANSFER_INTERNET, ATLAS_AWS_STREAM_PROCESSING_DATA_TRANSFER_SAME_REGION, ATLAS_AWS_STREAM_PROCESSING_INSTANCE_SP2, ATLAS_AWS_STREAM_PROCESSING_INSTANCE_SP5, ATLAS_AZURE_STREAM_PROCESSING_DATA_TRANSFER_DIFFERENT_CONTINENT, ATLAS_AZURE_STREAM_PROCESSING_DATA_TRANSFER_INTERNET, ATLAS_AZURE_STREAM_PROCESSING_DATA_TRANSFER_SAME_CONTINENT, ATLAS_AZURE_STREAM_PROCESSING_INSTANCE_SP2, ATLAS_AZURE_STREAM_PROCESSING_INSTANCE_SP5, ATLAS_GCP_STREAM_PROCESSING_DATA_TRANSFER_DIFFERENT_REGION, ATLAS_GCP_STREAM_PROCESSING_DATA_TRANSFER_INTERNET, ATLAS_GCP_STREAM_PROCESSING_DATA_TRANSFER_SAME_REGION, ATLAS_GCP_STREAM_PROCESSING_INSTANCE_SP2, ATLAS_GCP_STREAM_PROCESSING_INSTANCE_SP5' enum values to the 'results/items/lineItems/items/sku' response property
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
Updated
  • Added the new 'ATLAS_AWS_STREAM_PROCESSING_DATA_TRANSFER_DIFFERENT_REGION, ATLAS_AWS_STREAM_PROCESSING_DATA_TRANSFER_INTERNET, ATLAS_AWS_STREAM_PROCESSING_DATA_TRANSFER_SAME_REGION, ATLAS_AWS_STREAM_PROCESSING_INSTANCE_SP2, ATLAS_AWS_STREAM_PROCESSING_INSTANCE_SP5, ATLAS_AZURE_STREAM_PROCESSING_DATA_TRANSFER_DIFFERENT_CONTINENT, ATLAS_AZURE_STREAM_PROCESSING_DATA_TRANSFER_INTERNET, ATLAS_AZURE_STREAM_PROCESSING_DATA_TRANSFER_SAME_CONTINENT, ATLAS_AZURE_STREAM_PROCESSING_INSTANCE_SP2, ATLAS_AZURE_STREAM_PROCESSING_INSTANCE_SP5, ATLAS_GCP_STREAM_PROCESSING_DATA_TRANSFER_DIFFERENT_REGION, ATLAS_GCP_STREAM_PROCESSING_DATA_TRANSFER_INTERNET, ATLAS_GCP_STREAM_PROCESSING_DATA_TRANSFER_SAME_REGION, ATLAS_GCP_STREAM_PROCESSING_INSTANCE_SP2, ATLAS_GCP_STREAM_PROCESSING_INSTANCE_SP5' enum values to the 'lineItems/items/sku' response property

2025 年 10 月21 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在“results/items/oneOf[subschema #11: Replica Set Alert Configuration]/threshold/units”响应属性中添加了新的“pixels, tokens”枚举值
  • 在“results/items/oneOf[subschema #12：副本集阈值警报配置]/threshold/units”响应属性中添加了新的“像素、令牌”枚举值
  • 在“results/items/oneOf[subschema #13: 无服务器 警报 Configuration]/metricThreshold/units”响应属性中添加了新的“像素、令牌”枚举值
  • 在“results/items/oneOf[subschema #14: Flex 警报 Configuration]/metricThreshold/units”响应属性中添加了新的“pixels, tokens”枚举值
  • 在“results/items/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold/units”响应属性中添加了新的“pixels, tokens”枚举值
  • 在“results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/metricThreshold/units”响应属性中添加了新的“像素、令牌”枚举值
  • 在“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold/units”响应属性中添加了新的“pixels, tokens”枚举值
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在 '/oneOf[subschema #11: 副本集 警报 Configuration]/threshold/units' 响应属性中添加了新的 'pixels, tokens'枚举值
  • 将新的“像素、令牌”枚举值添加到“/oneOf[subschema #12：副本集阈值警报配置]/threshold/units”响应属性
  • 将新的“像素、令牌”枚举值添加到“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold/units”响应属性
  • 将新的“像素、令牌”枚举值添加到“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold/units”响应属性
  • 将新的“像素、令牌”枚举值添加到“/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold/units”响应属性
  • 已将新的“pixels、tokens”枚举值添加到“/oneOf[subschema #3: 应用 Services Metric 警报 Configuration]/metricThreshold/units”响应属性
  • 将新的“像素、令牌”枚举值添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold/units”响应属性
  • 已将新的“像素、令牌”枚举值添加到请求属性“/oneOf[subschema #11: 副本集警报配置]/threshold/units”
  • 已将新的“像素、令牌”枚举值添加到请求属性“/oneOf[subschema #12: 副本集阈值警报配置]/threshold/units”
  • 已将新的“像素、令牌”枚举值添加到请求属性“/oneOf[subschema #13: 无服务器 警报 Configuration]/metricThreshold/units”
  • 已将新的“像素、令牌”枚举值添加到请求属性“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold/units”
  • 已将新的“像素、令牌”枚举值添加到请求属性“/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold/units”
  • 已将新的“像素、令牌”枚举值添加到请求属性“/oneOf[subschema #3: 应用 Services 指标 警报 Configuration]/metricThreshold/units”
  • 已将新的“像素、令牌”枚举值添加到请求属性“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold/units”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在 '/oneOf[subschema #11: 副本集 警报 Configuration]/threshold/units' 响应属性中添加了新的 'pixels, tokens'枚举值
  • 将新的“像素、令牌”枚举值添加到“/oneOf[subschema #12：副本集阈值警报配置]/threshold/units”响应属性
  • 将新的“像素、令牌”枚举值添加到“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold/units”响应属性
  • 将新的“像素、令牌”枚举值添加到“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold/units”响应属性
  • 将新的“像素、令牌”枚举值添加到“/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold/units”响应属性
  • 已将新的“pixels、tokens”枚举值添加到“/oneOf[subschema #3: 应用 Services Metric 警报 Configuration]/metricThreshold/units”响应属性
  • 将新的“像素、令牌”枚举值添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold/units”响应属性
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在 '/oneOf[subschema #11: 副本集 警报 Configuration]/threshold/units' 响应属性中添加了新的 'pixels, tokens'枚举值
  • 将新的“像素、令牌”枚举值添加到“/oneOf[subschema #12：副本集阈值警报配置]/threshold/units”响应属性
  • 将新的“像素、令牌”枚举值添加到“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold/units”响应属性
  • 将新的“像素、令牌”枚举值添加到“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold/units”响应属性
  • 将新的“像素、令牌”枚举值添加到“/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold/units”响应属性
  • 已将新的“pixels、tokens”枚举值添加到“/oneOf[subschema #3: 应用 Services Metric 警报 Configuration]/metricThreshold/units”响应属性
  • 将新的“像素、令牌”枚举值添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold/units”响应属性
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在 '/oneOf[subschema #11: 副本集 警报 Configuration]/threshold/units' 响应属性中添加了新的 'pixels, tokens'枚举值
  • 将新的“像素、令牌”枚举值添加到“/oneOf[subschema #12：副本集阈值警报配置]/threshold/units”响应属性
  • 将新的“像素、令牌”枚举值添加到“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold/units”响应属性
  • 将新的“像素、令牌”枚举值添加到“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold/units”响应属性
  • 将新的“像素、令牌”枚举值添加到“/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold/units”响应属性
  • 已将新的“pixels、tokens”枚举值添加到“/oneOf[subschema #3: 应用 Services Metric 警报 Configuration]/metricThreshold/units”响应属性
  • 将新的“像素、令牌”枚举值添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold/units”响应属性
  • 已将新的“像素、令牌”枚举值添加到请求属性“/oneOf[subschema #11: 副本集警报配置]/threshold/units”
  • 已将新的“像素、令牌”枚举值添加到请求属性“/oneOf[subschema #12: 副本集阈值警报配置]/threshold/units”
  • 已将新的“像素、令牌”枚举值添加到请求属性“/oneOf[subschema #13: 无服务器 警报 Configuration]/metricThreshold/units”
  • 已将新的“像素、令牌”枚举值添加到请求属性“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold/units”
  • 已将新的“像素、令牌”枚举值添加到请求属性“/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold/units”
  • 已将新的“像素、令牌”枚举值添加到请求属性“/oneOf[subschema #3: 应用 Services 指标 警报 Configuration]/metricThreshold/units”
  • 已将新的“像素、令牌”枚举值添加到请求属性“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold/units”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 在“results/items/oneOf[subschema #4: 托管指标警报]/currentValue/units”响应属性中添加了新的“像素、令牌”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 在“results/items/oneOf[subschema #4: 托管指标警报]/currentValue/units”响应属性中添加了新的“像素、令牌”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将新的“像素、令牌”枚举值添加到“/oneOf[subschema #4: 托管指标警报]/currentValue/units”响应属性
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将新的“像素、令牌”枚举值添加到“/oneOf[subschema #4: 托管指标警报]/currentValue/units”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 在“results/items/oneOf[subschema #11: Replica Set Alert Configuration]/threshold/units”响应属性中添加了新的“pixels, tokens”枚举值
  • 在“results/items/oneOf[subschema #12：副本集阈值警报配置]/threshold/units”响应属性中添加了新的“像素、令牌”枚举值
  • 在“results/items/oneOf[subschema #13: 无服务器 警报 Configuration]/metricThreshold/units”响应属性中添加了新的“像素、令牌”枚举值
  • 在“results/items/oneOf[subschema #14: Flex 警报 Configuration]/metricThreshold/units”响应属性中添加了新的“pixels, tokens”枚举值
  • 在“results/items/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold/units”响应属性中添加了新的“pixels, tokens”枚举值
  • 在“results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/metricThreshold/units”响应属性中添加了新的“像素、令牌”枚举值
  • 在“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold/units”响应属性中添加了新的“pixels, tokens”枚举值
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 在“results/items/oneOf[subschema #14: 托管指标事件]/currentValue/units”响应属性中添加了新的“像素、令牌”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 将新的“像素、令牌”枚举值添加到“/oneOf[subschema #14: 托管 Metric Events]/currentValue/units”响应属性

2025 年 10 月10 日发布

GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 在“results/items/oneOf[subschema #6: 计费事件]/eventTypeName”响应属性中添加了新的“BECAME_LINKED_ORG、CROSS_ORG_OPERATION_TICKET_TRACKING”枚举值
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 在“/oneOf[subschema #6: 计费事件]/eventTypeName”响应属性中添加了新的“BECAME_LINKED_ORG、CROSS_ORG_OPERATION_TICKET_TRACKING”枚举值

2025 年 10 月09 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在“results/items/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #4: FTS Index Atlas 审核 Types]/”响应属性中添加了新的“FTS_INDEX_STALE”枚举值
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #4: FTS Index Atlas 审核 Types]/”响应属性中添加了新的“FTS_INDEX_STALE”枚举值
  • 已将新的“FTS_INDEX_STALE”枚举值添加到请求属性“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #4: Full Text Search 索引 Atlas 审核类型]/”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #4: FTS Index Atlas 审核 Types]/”响应属性中添加了新的“FTS_INDEX_STALE”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #4: FTS Index Atlas 审核 Types]/”响应属性中添加了新的“FTS_INDEX_STALE”枚举值
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在“/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #4: FTS Index Atlas 审核 Types]/”响应属性中添加了新的“FTS_INDEX_STALE”枚举值
  • 已将新的“FTS_INDEX_STALE”枚举值添加到请求属性“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #4: Full Text Search 索引 Atlas 审核类型]/”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 在“results/items/oneOf[subschema #7: 其他警报]/eventTypeName/oneOf[subschema #4: Full Text Search 索引 Atlas 审核类型]/”响应属性中添加了新的“FTS_INDEX_STALE”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 在“results/items/oneOf[subschema #7: 其他警报]/eventTypeName/oneOf[subschema #4: Full Text Search 索引 Atlas 审核类型]/”响应属性中添加了新的“FTS_INDEX_STALE”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 在“/oneOf[subschema #7: 其他警报]/eventTypeName/oneOf[subschema #4: FTS 索引 Atlas 审核 类型]/”响应属性中添加了新的“FTS_INDEX_STALE”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 在“/oneOf[subschema #7: 其他警报]/eventTypeName/oneOf[subschema #4: FTS 索引 Atlas 审核 类型]/”响应属性中添加了新的“FTS_INDEX_STALE”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 在“results/items/oneOf[subschema #1: Any other 警报 Configurations]/eventTypeName/oneOf[subschema #4: FTS Index Atlas 审核 Types]/”响应属性中添加了新的“FTS_INDEX_STALE”枚举值
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将新的“FTS_INDEX_STALE”枚举值添加到“results/items/oneOf[subschema #12: Full Text Search 索引审核]/eventTypeName”响应属性
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 将新的“FTS_INDEX_STALE”枚举值添加到“/oneOf[subschema #12: Full Text Search 索引审核]/eventTypeName”响应属性

2025 年 10 月01 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将新的“HOST_SEARCH_NODE_INDEX_FAILED”枚举值添加到“results/items/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”响应属性
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将新的“HOST_SEARCH_NODE_INDEX_FAILED”枚举值添加到“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”响应属性
  • 已将新的“HOST_SEARCH_NODE_INDEX_FAILED”枚举值添加到请求属性“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将新的“HOST_SEARCH_NODE_INDEX_FAILED”枚举值添加到“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”响应属性
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将新的“HOST_SEARCH_NODE_INDEX_FAILED”枚举值添加到“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”响应属性
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将新的“HOST_SEARCH_NODE_INDEX_FAILED”枚举值添加到“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”响应属性
  • 已将新的“HOST_SEARCH_NODE_INDEX_FAILED”枚举值添加到请求属性“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 将新的“HOST_SEARCH_NODE_INDEX_FAILED”枚举值添加到“results/items/oneOf[subschema #3: Host Alerts]/eventTypeName”响应属性
  • 将新的“HOST_SEARCH_NODE_INDEX_FAILED”枚举值添加到“results/items/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 将新的“HOST_SEARCH_NODE_INDEX_FAILED”枚举值添加到“results/items/oneOf[subschema #3: Host Alerts]/eventTypeName”响应属性
  • 将新的“HOST_SEARCH_NODE_INDEX_FAILED”枚举值添加到“results/items/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将新的 'HOST_SEARCH_NODE_INDEX_FAILED'枚举值添加到 '/oneOf[subschema #3: Host Alerts]/eventTypeName' 响应属性
  • 将新的 'HOST_SEARCH_NODE_INDEX_FAILED'枚举值添加到 '/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName' 响应属性
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将新的 'HOST_SEARCH_NODE_INDEX_FAILED'枚举值添加到 '/oneOf[subschema #3: Host Alerts]/eventTypeName' 响应属性
  • 将新的 'HOST_SEARCH_NODE_INDEX_FAILED'枚举值添加到 '/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName' 响应属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 将新的“HOST_SEARCH_NODE_INDEX_FAILED”枚举值添加到“results/items/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”响应属性
GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 添加了可选属性 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema1 #: Amazon Web Services Regional ReplicationSpecifications]/forcedAnalyticsSpecs、results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema1 #: Amazon Web Services区域复制规范]/有效ElectableSpecs, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema1 #: Amazon Web Services区域复制规范]/有效ReadOnlySpecs, results/items/replicationSpecs /items/regionConfigs/items/oneOf[subschema2 #: Azure区域复制规范]/有效分析规范，results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema2 #: Azure区域复制规范]/有效ElectableSpecs , results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema2 #: Azure Regional ReplicationSpecifications]/forcedReadOnlySpecs, results/items/replicationSpecs/items/regionConf igs/items/oneOf[subschema #3 ： GCP区域复制规范]/有效分析规范 s，results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3 ： GCP区域复制规范]/有效ElectableSpecs，结果/GCP响应3
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsSpecs”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/readOnlySpecs”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsSpecs”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/readOnlySpecs”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/analyticsSpecs”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/readOnlySpecs”变为只读
  • 添加了可选属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/forcedAnalyticsSpecs、replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/有效ElectableSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/有效ReadOnlySpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/ validAnalyticsSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/有效ElectableSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/有效只读规范，replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/有效分析规范， replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/有效ElectableSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/heartOnlySpecs, useAwsTimeBasedSnapshotCopyForFastInitialSync'到响应
  • 添加了新的可选请求属性“useAwsTimeBasedSnapshotCopyForFastInitialSync”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 添加了可选属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/forcedAnalyticsSpecs、replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/有效ElectableSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/有效ReadOnlySpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/ validAnalyticsSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/有效ElectableSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/有效只读规范，replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/有效分析规范， replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/有效ElectableSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/heartOnlySpecs, useAwsTimeBasedSnapshotCopyForFastInitialSync'到响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsSpecs”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/readOnlySpecs”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsSpecs”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/readOnlySpecs”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/analyticsSpecs”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/readOnlySpecs”变为只读
  • 添加了可选属性 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/forcedAnalyticsSpecs、replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/有效ElectableSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/有效ReadOnlySpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/ validAnalyticsSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/有效ElectableSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/有效只读规范，replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/有效分析规范， replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/有效ElectableSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/heartOnlySpecs, useAwsTimeBasedSnapshotCopyForFastInitialSync'到响应
  • 添加了新的可选请求属性“useAwsTimeBasedSnapshotCopyForFastInitialSync”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 在响应中添加了可选的只写属性“deleteSnapshots”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 在响应中添加了可选的只写属性“deleteSnapshots”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 在响应中添加了可选的只写属性“deleteSnapshots”
  • 添加了新的可选请求属性“deleteSnapshots”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives
Updated
  • “dbName”请求属性的 maxLength 已设立为“64”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • “definition/oneOf[subschema #1: 文本搜索索引定义]/mappings/dynamic”请求属性类型/格式从“boolean”/“更改为”对象“/”
  • 添加了新的可选请求属性“definition/oneOf[subschema #1: Text Search Index Definition]/typeSets”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • “definition/oneOf[subschema #1: 文本搜索索引定义]/mappings/dynamic”请求属性类型/格式从“boolean”/“更改为”对象“/”
  • 添加了新的可选请求属性“definition/oneOf[subschema #1: Text Search Index Definition]/typeSets”
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 在“results/items/oneOf[subschema #15: NDS Audits]/eventTypeName”响应属性中添加了新的“CLUSTER_INSTANCE_VM_RESTART_CLEARED”枚举值
  • 在“results/items/oneOf[subschema #13: Host Events]/eventTypeName”响应属性中添加了新的“HOST_SEARCH_NODE_INDEX_FAILED、HOST_SEARCH_NODE_UNBLOCKED”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 已将新的 'CLUSTER_INSTANCE_VM_RESTART_CLEARED'枚举值添加到 '/oneOf[subschema #15: NDS Audits]/eventTypeName' 响应属性
  • 已将新的 'HOST_SEARCH_NODE_INDEX_FAILED、HOST_SEARCH_NODE_UNBLOCKED'枚举值添加到 '/oneOf[subschema #13: Host Events]/eventTypeName' 响应属性
POST /api/atlas/v2/groups/{groupId}/flexClusters:tenantUpgrade
Updated
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsSpecs”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/readOnlySpecs”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsSpecs”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/readOnlySpecs”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/analyticsSpecs”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/readOnlySpecs”变为只读
  • 添加了新的可选请求属性“useAwsTimeBasedSnapshotCopyForFastInitialSync”
GET /api/atlas/v2/groups/{groupId}/integrations
Updated
  • 添加了 '#/components/schemas/PagerDuty, #/components/schemas/ Slack, #/components/schemas/DataDog, #/components/schemas/NewRelic, #/components/schemas/OpsGenie, #/components/schemas/VictorOps, #/components/schemas/Webhook, #/components/schemas/Prometheus, #/components/schemas/MicrosoftTeams' 到该响应的 'results/items/' 响应属性'oneOf' 列表
GET /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 添加了 '#/components/schemas/PagerDuty, #/components/schemas/ Slack, #/components/schemas/DataDog, #/components/schemas/NewRelic, #/components/schemas/OpsGenie, #/components/schemas/VictorOps, #/components/schemas/Webhook, #/components/schemas/Prometheus, #/components/schemas/MicrosoftTeams' 到响应的响应正文“oneOf”列表
POST /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 添加了 '#/components/schemas/PagerDuty, #/components/schemas/ Slack, #/components/schemas/DataDog, #/components/schemas/NewRelic, #/components/schemas/OpsGenie, #/components/schemas/VictorOps, #/components/schemas/Webhook, #/components/schemas/Prometheus, #/components/schemas/MicrosoftTeams' 到请求正文 'oneOf' 列表
  • 添加了 '#/components/schemas/PagerDuty, #/components/schemas/ Slack, #/components/schemas/DataDog, #/components/schemas/NewRelic, #/components/schemas/OpsGenie, #/components/schemas/VictorOps, #/components/schemas/Webhook, #/components/schemas/Prometheus, #/components/schemas/MicrosoftTeams' 到该响应的 'results/items/' 响应属性'oneOf' 列表
PUT /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 添加了 '#/components/schemas/PagerDuty, #/components/schemas/ Slack, #/components/schemas/DataDog, #/components/schemas/NewRelic, #/components/schemas/OpsGenie, #/components/schemas/VictorOps, #/components/schemas/Webhook, #/components/schemas/Prometheus, #/components/schemas/MicrosoftTeams' 到请求正文 'oneOf' 列表
  • 添加了 '#/components/schemas/PagerDuty, #/components/schemas/ Slack, #/components/schemas/DataDog, #/components/schemas/NewRelic, #/components/schemas/OpsGenie, #/components/schemas/VictorOps, #/components/schemas/Webhook, #/components/schemas/Prometheus, #/components/schemas/MicrosoftTeams' 到该响应的 'results/items/' 响应属性'oneOf' 列表
GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在响应中添加了可选属性“results/items/streamConfig/maxTierSize”
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在响应中添加了可选属性“streamConfig/maxTierSize”
  • 添加了新的可选请求属性“streamConfig/maxTierSize”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在响应中添加了可选属性“streamConfig/maxTierSize”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在响应中添加了可选属性“streamConfig/maxTierSize”
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
Updated
  • 在响应中添加了可选属性“streamConfig/maxTierSize”
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 在“results/items/oneOf[subschema #8: Org Events]/eventTypeName”响应属性中添加了新的“ORG_BAAS_EOL_EXTENSION_ACCEPTED、ORG_BAAS_EOL_EXTENSION_CANCELED、ORG_BAAS_EOL_EXTENSION_PENDING、SANDBOX_CONFIG_DELETED、SANDBOX_TEMPLATE_UPDATED”枚举值
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 在“/oneOf[subschema #8: Org Events]/eventTypeName”响应属性中添加了新的“ORG_BAAS_EOL_EXTENSION_ACCEPTED、ORG_BAAS_EOL_EXTENSION_CANCELED、ORG_BAAS_EOL_EXTENSION_PENDING、SANDBOX_CONFIG_DELETED、SANDBOX_TEMPLATE_UPDATED”枚举值
GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • Added the new 'ATLAS_AWS_TIME_BASED_SNAPSHOT_COPY_LEVEL_1, ATLAS_AWS_TIME_BASED_SNAPSHOT_COPY_LEVEL_2, ATLAS_AWS_TIME_BASED_SNAPSHOT_COPY_LEVEL_3, ATLAS_AWS_TIME_BASED_SNAPSHOT_COPY_LEVEL_4, ATLAS_AWS_TIME_BASED_SNAPSHOT_COPY_LEVEL_5, ATLAS_AWS_TIME_BASED_SNAPSHOT_COPY_LEVEL_6, ATLAS_AWS_TIME_BASED_SNAPSHOT_COPY_LEVEL_7' 枚举 values to the 'results/items/lineItems/ items/sku' 响应属性
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
Updated
  • Added the new 'ATLAS_AWS_TIME_BASED_SNAPSHOT_COPY_LEVEL_1, ATLAS_AWS_TIME_BASED_SNAPSHOT_COPY_LEVEL_2, ATLAS_AWS_TIME_BASED_SNAPSHOT_COPY_LEVEL_3, ATLAS_AWS_TIME_BASED_SNAPSHOT_COPY_LEVEL_4, ATLAS_AWS_TIME_BASED_SNAPSHOT_COPY_LEVEL_5, ATLAS_AWS_TIME_BASED_SNAPSHOT_COPY_LEVEL_6, ATLAS_AWS_TIME_BASED_SNAPSHOT_COPY_LEVEL_7' 枚举 values to the 'lineItems/items/sku'响应属性

2025 年 9 月 30 日发布

GET /api/atlas/v2/groups/{groupId}/pipelines
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2025-09-30”
POST /api/atlas/v2/groups/{groupId}/pipelines
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2025-09-30”
DELETE /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2025-09-30”
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2025-09-30”
PATCH /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2025-09-30”
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/availableSchedules
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2025-09-30”
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/availableSnapshots
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2025-09-30”
POST /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/pause
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2025-09-30”
POST /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/resume
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2025-09-30”
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/runs
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2025-09-30”
DELETE /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/runs/{pipelineRunId}
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2025-09-30”
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/runs/{pipelineRunId}
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2025-09-30”
POST /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/trigger
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2025-09-30”

2025 年 9 月 23 日发布

GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将“subschema #36：查询形状事件类型”添加到“results/items/oneOf[subschema #1: Any other Events]/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 将“subschema #36：查询形状事件类型”添加到“/oneOf[subschema #1：任何其他事件]/eventTypeName”响应属性“oneOf”列表中

2025 年 9 月 22 日发布

GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在响应中添加了可选属性“results/items/connections/items/ 身份验证/method”
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在响应中添加了可选属性“connections/items/ 身份验证/method”
  • 添加了新的可选请求属性“connections/items/ 身份验证/method”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在响应中添加了可选属性“connections/items/ 身份验证/method”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在响应中添加了可选属性“connections/items/ 身份验证/method”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 在响应中添加了可选属性“results/items/ 身份验证/method”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 在响应中添加了可选属性“/ 身份验证/method”
  • 添加了新的可选请求属性“/ 身份验证/method”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 在响应中添加了可选属性“/ 身份验证/method”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 在响应中添加了可选属性“/ 身份验证/method”
  • 添加了新的可选请求属性“/ 身份验证/method”
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
Updated
  • 在响应中添加了可选属性“connections/items/ 身份验证/method”

2025 年 9 月 17 日发布

GET /api/atlas/v2/orgs/{orgId}/settings
Updated
  • 在响应中添加了可选属性“customSessionTimeups”
PATCH /api/atlas/v2/orgs/{orgId}/settings
Updated
  • 在响应中添加了可选属性“customSessionTimeups”
  • 添加了新的可选请求属性“customSessionTimeups”

2025 年 9 月 11 日发布

GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 在响应中添加了可选属性“results/items/internalClusterRole”
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 在响应中添加了可选属性“internalClusterRole”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 在响应中添加了可选属性“internalClusterRole”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 在响应中添加了可选属性“internalClusterRole”
GET / API/ Atlas/v2/groups/{groupId}/clusters/{clusterName}/queryShapeInsights/summaries
Updated
  • 在响应中添加了可选属性“summaries/items/systemQuery”
GET / API/ Atlas/v2/groups/{groupId}/clusters/{clusterName}/queryShapeInsights/{queryShapeHash}/details
Updated
  • 在响应中添加了可选属性“queryStats/systemQuery”
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将新的 'CLUSTER_CONNECTION_GET_NAMESPACES_AND_PROJECT_SQL_SCHEMA_DATA'枚举值添加到 'results/items/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #4: Cluster Connection Audit Types]/' 响应属性
  • 将新的“SSH_KEY_NDS_HOST_ACCESS_LEVEL_CHANGED”枚举值添加到“results/items/oneOf[subschema #13: Host Events]/eventTypeName”响应属性
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 将新的 'CLUSTER_CONNECTION_GET_NAMESPACES_AND_PROJECT_SQL_SCHEMA_DATA'枚举值添加到 '/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #4: Cluster Connection Audit Types]/' 响应属性
  • 将新的“SSH_KEY_NDS_HOST_ACCESS_LEVEL_CHANGED”枚举值添加到“/oneOf[subschema #13: Host Events]/eventTypeName”响应属性中
GET /api/atlas/v2/groups/{groupId}/streams/accountDetails
Updated
  • 已将“GCP”映射键添加到响应状态“200”的响应鉴别器
  • 将“#/components/schemas/GCPAccountDetails”添加到响应的响应正文“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections
Updated
  • 在响应中添加了可选属性“results/items/gcpServiceAttachmentUris”
POST /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections
Updated
  • 在响应中添加了可选属性“gcpServiceAttachmentUris”
  • 添加了新的可选请求属性“gcpServiceAttachmentUris”
GET /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections/{connectionId}
Updated
  • 在响应中添加了可选属性“gcpServiceAttachmentUris”

2025 年 8 月 29 日发布

POST /api/atlas/v2/groups/{groupId}/cloudProviderAccess
Updated
  • 将 '#/components/schemas/CloudProviderAccessAWSIAMRole, #/components/schemas/CloudProviderAccessAzureServicePrincipal, #/components/schemas/CloudProviderAccessGCPServiceAccount' 添加到响应的响应正文“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/cloudProviderAccess/{roleId}
Updated
  • 将 '#/components/schemas/CloudProviderAccessAWSIAMRole, #/components/schemas/CloudProviderAccessAzureServicePrincipal, #/components/schemas/CloudProviderAccessGCPServiceAccount' 添加到响应的响应正文“oneOf”列表中
PATCH /api/atlas/v2/groups/{groupId}/cloudProviderAccess/{roleId}
Updated
  • 将 '#/components/schemas/CloudProviderAccessAWSIAMRole, #/components/schemas/CloudProviderAccessAzureServicePrincipal, #/components/schemas/CloudProviderAccessGCPServiceAccount' 添加到响应的响应正文“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在响应中添加了可选的只写属性“results/items/connections/items/ 身份验证/clientSecret”
  • 添加了可选属性 'results/items/connections/items/ 身份验证/clientId、results/items/connections/items/ 身份验证/httpsCaPem、results/items/connections/items/ 身份验证/saslOauthbearerExtensions、results/items/connections/items/ 身份验证/scope, results/items/connections/items/ 身份验证/tokenEndpointUrl' 到响应
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在响应中添加了可选的只写属性“connections/items/ 身份验证/clientSecret”
  • 在响应中添加了可选属性“connections/items/ 身份验证/clientId,connections/items/ 身份验证 /httpsCaPem,connections/items/ 身份验证 /saslOauthbearerExtensions,connections/items/ 身份验证 /scope,connections/items/ 身份验证/tokenEndpointUrl”
  • 添加了新的可选请求属性 'connections/items/ 身份验证/clientId,connections/items/ 身份验证/clientSecret,connections/items/ 身份验证/httpsCaPem,connections/items/ 身份验证/saslOauthbearerExtensions,connections/items/ 身份验证/scope,connections/items / 身份验证/tokenEndpointUrl'
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在响应中添加了可选的只写属性“connections/items/ 身份验证/clientSecret”
  • 在响应中添加了可选属性“connections/items/ 身份验证/clientId,connections/items/ 身份验证 /httpsCaPem,connections/items/ 身份验证 /saslOauthbearerExtensions,connections/items/ 身份验证 /scope,connections/items/ 身份验证/tokenEndpointUrl”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在响应中添加了可选的只写属性“connections/items/ 身份验证/clientSecret”
  • 在响应中添加了可选属性“connections/items/ 身份验证/clientId,connections/items/ 身份验证 /httpsCaPem,connections/items/ 身份验证 /saslOauthbearerExtensions,connections/items/ 身份验证 /scope,connections/items/ 身份验证/tokenEndpointUrl”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 在响应中添加了可选的只写属性“results/items/ 身份验证/clientSecret”
  • 在响应中添加了可选属性“results/items/ 身份验证/clientId,results/items/ 身份验证 /httpsCaPem,results/items/ 身份验证 /saslOauthbearerExtensions,results/items/authentication/scope,results / items/ 身份验证/tokenEndpointUrl”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 在响应中添加了可选的只写属性“/ 身份验证/clientSecret”
  • 在响应中添加了可选属性 '/ 身份验证/clientId, / 身份验证/httpsCaPem, / 身份验证/saslOauthbearerExtensions, / 身份验证/scope, / 身份验证/tokenEndpointUrl' 到响应
  • 添加了新的可选请求属性 '/ 身份验证/clientId, / 身份验证/clientSecret, / 身份验证/httpsCaPem, / 身份验证/saslOauthbearerExtensions, / 身份验证/scope, / 身份验证/tokenEndpointUrl'
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 在响应中添加了可选的只写属性“/ 身份验证/clientSecret”
  • 在响应中添加了可选属性 '/ 身份验证/clientId, / 身份验证/httpsCaPem, / 身份验证/saslOauthbearerExtensions, / 身份验证/scope, / 身份验证/tokenEndpointUrl' 到响应
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 在响应中添加了可选的只写属性“/ 身份验证/clientSecret”
  • 在响应中添加了可选属性 '/ 身份验证/clientId, / 身份验证/httpsCaPem, / 身份验证/saslOauthbearerExtensions, / 身份验证/scope, / 身份验证/tokenEndpointUrl' 到响应
  • 添加了新的可选请求属性 '/ 身份验证/clientId, / 身份验证/clientSecret, / 身份验证/httpsCaPem, / 身份验证/saslOauthbearerExtensions, / 身份验证/scope, / 身份验证/tokenEndpointUrl'
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
Updated
  • 在响应中添加了可选的只写属性“connections/items/ 身份验证/clientSecret”
  • 在响应中添加了可选属性“connections/items/ 身份验证/clientId,connections/items/ 身份验证 /httpsCaPem,connections/items/ 身份验证 /saslOauthbearerExtensions,connections/items/ 身份验证 /scope,connections/items/ 身份验证/tokenEndpointUrl”

2025 年 8 月 28 日发布

POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在请求属性“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/”中添加了新的“GROUP_SERVICE_ACCOUNT_SECRETS_EXPIRED、GROUP_SERVICE_ACCOUNT_SECRETS_EXPIRING”枚举值
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在请求属性“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/”中添加了新的“GROUP_SERVICE_ACCOUNT_SECRETS_EXPIRED、GROUP_SERVICE_ACCOUNT_SECRETS_EXPIRING”枚举值
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将新的“ONLINE_ARCHIVE_DELETE_AFTER_DATE_UPDATED”枚举值添加到“results/items/oneOf[subschema #15: NDS Audits]/eventTypeName”响应属性
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 将新的“ONLINE_ARCHIVE_DELETE_AFTER_DATE_UPDATED”枚举值添加到“/oneOf[subschema #15: NDS Audits]/eventTypeName”响应属性
GET /api/atlas/v2/groups/{groupId}/limits
Updated
  • 删除了 'atlas.项目。部署.salesSoldM0s'鉴别器映射来自 '/items/' 响应属性的键
GET /api/atlas/v2/groups/{groupId}/limits/{limitName}
Updated
  • 删除了 'atlas.项目。部署.salesSoldM0s'将来自响应鉴别器的键映射到响应状态“200”
PATCH /api/atlas/v2/groups/{groupId}/limits/{limitName}
Updated
  • 删除了 'atlas.项目。部署.salesSoldM0s'从请求鉴别器映射键
  • 删除了 'atlas.项目。部署.salesSoldM0s'将来自响应鉴别器的键映射到响应状态“200”

2025 年 8 月 20 日发布

GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将新的“MONITORING_AGENT_OVERRIDES”枚举值添加到“results/items/oneOf[subschema #15: NDS Audits]/eventTypeName”响应属性
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 将新的“MONITORING_AGENT_OVERRIDES”枚举值添加到“/oneOf[subschema #15: NDS Audits]/eventTypeName”响应属性

2025 年 8 月 08 日发布

GET /api/atlas/v2/groups/{groupId}/cloudProviderAccess
Updated
  • 在响应中添加了可选属性“gcpServiceAccounts”

2025 年 8 月 06 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将新的 'HOST_MOGOT_APPROACHING_STOP_REPLICATION'枚举值添加到 'results/items/oneOf[subschema #8: Host Alert Configuration]/eventTypeName' 响应属性
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将新的 'HOST_MOGOT_APPROACHING_STOP_REPLICATION'枚举值添加到 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName' 响应属性
  • 已将新的“HOST_MOGOT_APPROACHING_STOP_REPLICATION”枚举值添加到请求属性“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将新的 'HOST_MOGOT_APPROACHING_STOP_REPLICATION'枚举值添加到 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName' 响应属性
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将新的 'HOST_MOGOT_APPROACHING_STOP_REPLICATION'枚举值添加到 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName' 响应属性
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将新的 'HOST_MOGOT_APPROACHING_STOP_REPLICATION'枚举值添加到 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName' 响应属性
  • 已将新的“HOST_MOGOT_APPROACHING_STOP_REPLICATION”枚举值添加到请求属性“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 将新的 'HOST_MOGOT_APPROACHING_STOP_REPLICATION'枚举值添加到 'results/items/oneOf[subschema #3: Host Alerts]/eventTypeName' 响应属性
  • 将新的 'HOST_MOGOT_APPROACHING_STOP_REPLICATION'枚举值添加到 'results/items/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName' 响应属性
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 将新的 'HOST_MOGOT_APPROACHING_STOP_REPLICATION'枚举值添加到 'results/items/oneOf[subschema #3: Host Alerts]/eventTypeName' 响应属性
  • 将新的 'HOST_MOGOT_APPROACHING_STOP_REPLICATION'枚举值添加到 'results/items/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName' 响应属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将新的 'HOST_MOGOT_APPROACHING_STOP_REPLICATION'枚举值添加到 '/oneOf[subschema #3: Host Alerts]/eventTypeName' 响应属性
  • 将新的 'HOST_MOGOT_APPROACHING_STOP_REPLICATION'枚举值添加到 '/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName' 响应属性
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将新的 'HOST_MOGOT_APPROACHING_STOP_REPLICATION'枚举值添加到 '/oneOf[subschema #3: Host Alerts]/eventTypeName' 响应属性
  • 将新的 'HOST_MOGOT_APPROACHING_STOP_REPLICATION'枚举值添加到 '/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName' 响应属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 将新的 'HOST_MOGOT_APPROACHING_STOP_REPLICATION'枚举值添加到 'results/items/oneOf[subschema #8: Host Alert Configuration]/eventTypeName' 响应属性
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将新的“ATLAS_MAINTENANCE_RESET_BY_ADMIN”枚举值添加到“results/items/oneOf[subschema #15: NDS Audits]/eventTypeName”响应属性
  • 将新的 'CLUSTER_CONNECTION_GET_AGGREGATED_VIEW_INFOS'枚举值添加到 'results/items/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #4: Cluster Connection Audit Types]/' 响应属性
  • 在“results/items/oneOf[subschema #13: Host Events]/eventTypeName”响应属性中添加了新的“HOST_MOGOT_APPROACHING_STOP_REPLICATION、HOST_MONGOT_SUFFICIENT_DISK_SPACE”枚举值
  • 从“results/items/oneOf[subschema #15: NDS Audits]/eventTypeName”响应属性中删除了“AUTO_HEALING_CANNOT_REPAIR_INTERNAL、AUTO_HEALING_CANNOT_RESYNC_INTERNAL”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 已将新的“ATLAS_MAINTENANCE_RESET_BY_ADMIN”枚举值添加到“/oneOf[subschema #15: NDS Audits]/eventTypeName”响应属性
  • 在“/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #4: Cluster Connection Audit Types]/”响应属性中添加了新的“CLUSTER_CONNECTION_GET_AGGREGATED_VIEW_INFOS”枚举值
  • 在 '/oneOf[subschema #13: Host Events]/eventTypeName' 响应属性中添加了新的 'HOST_MOGOT_APPROACHING_STOP_REPLICATION、HOST_MONGOT_SUFFICIENT_DISK_SPACE'枚举值
  • 已从“/oneOf[subschema #15: NDS Audits]/eventTypeName”响应属性中删除“AUTO_HEALING_CANNOT_REPAIR_INTERNAL、AUTO_HEALING_CANNOT_RESYNC_INTERNAL、MONGOTUNE_ENABLED”枚举值
POST /api/atlas/v2/groups/{groupId}/users/{userId}:addRole
Updated
  • 键“ACTIVE”的映射值从响应状态“200”的响应鉴别器的“#/components/schemas/OrgActiveUserResponse”更改为“#/components/schemas/GroupActiveUserResponse”
  • 对于响应状态为“200”的响应鉴别器，键“PENDING”的映射值从“#/components/schemas/OrgPendingUserResponse”更改为“#/components/schemas/GroupPendingUserResponse”
  • 将“#/components/schemas/GroupPendingUserResponse, #/components/schemas/GroupActiveUserResponse”添加到响应的响应正文“oneOf”列表中
  • 已从响应的响应正文“oneOf”列表中删除“#/components/schemas/OrgPendingUserResponse, #/components/schemas/OrgActiveUserResponse”
POST /api/atlas/v2/groups/{groupId}/users/{userId}:removeRole
Updated
  • 键“ACTIVE”的映射值从响应状态“200”的响应鉴别器的“#/components/schemas/OrgActiveUserResponse”更改为“#/components/schemas/GroupActiveUserResponse”
  • 对于响应状态为“200”的响应鉴别器，键“PENDING”的映射值从“#/components/schemas/OrgPendingUserResponse”更改为“#/components/schemas/GroupPendingUserResponse”
  • 将“#/components/schemas/GroupPendingUserResponse, #/components/schemas/GroupActiveUserResponse”添加到响应的响应正文“oneOf”列表中
  • 已从响应的响应正文“oneOf”列表中删除“#/components/schemas/OrgPendingUserResponse, #/components/schemas/OrgActiveUserResponse”
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 已将新的“VERCEL_USAGE_REPORTED”枚举值添加到“results/items/oneOf[subschema #6: Car Events]/eventTypeName”响应属性
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 已将新的“VERCEL_USAGE_REPORTED”枚举值添加到“/oneOf[subschema #6: 电信事件]/eventTypeName”响应属性
GET /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users
Updated
  • 添加了新的可选“查询”请求参数“userId”

2025 年 7 月 31 日发布

GET /api/atlas/v2
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“apiKey/roles/items/roleName”响应属性中
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“results/items/postAuthRoleGrants/items/”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“results/items/roleMappings/items/roleAssignments/items/ 角色”响应属性
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
Updated
  • 已将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“postAuthRoleGrants/items/”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roleMappings/items/roleAssignments/items/ 角色”响应属性
PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
Updated
  • 已将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“postAuthRoleGrants/items/”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roleMappings/items/roleAssignments/items/ 角色”响应属性
  • 已将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到请求属性“postAuthRoleGrants/items/”
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到请求属性“roleMappings/items/roleAssignments/items/ 角色”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“results/items/roleAssignments/items/ 角色”响应属性
POST /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roleAssignments/items/ 角色”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到请求属性“roleAssignments/items/ 角色”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings/{id}
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roleAssignments/items/ 角色”响应属性中
PUT /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings/{id}
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roleAssignments/items/ 角色”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到请求属性“roleAssignments/items/ 角色”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders
Updated
  • 已将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“results/items/ associatedOrgs/items/postAuthRoleGrants/items/”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“results/items/关联Orgs/items/roleMappings/items/roleAssignments/items/ 角色”响应属性
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“results/items/oneOf[subschema #1: SAML]/关联Orgs/items/postAuthRoleGrants/items/”响应属性
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“results/items/oneOf[subschema #1: SAML]/关联Orgs/items/roleMappings/items/roleAssignments/items/ 角色”响应属性
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“results/items/oneOf[subschema #2: OIDC WORKFORCE]/关联Orgs/items/postAuthRoleGrants/items/”响应属性
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“results/items/oneOf[subschema #2: OIDC WORKFORCE]/关联Orgs/items/roleMappings/items/roleAssignments/items/ 角色”响应属性
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“results/items/oneOf[subschema #3: OIDC WORKLOAD]/关联Orgs/items/postAuthRoleGrants/items/”响应属性
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“results/items/oneOf[subschema #3: OIDC WORKLOAD]/关联Orgs/items/roleMappings/items/roleAssignments/items/ 角色”响应属性
POST /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“/oneOf[subschema #1: OIDC WORKFORCE]/关联Orgs/items/postAuthRoleGrants/items/”响应属性
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“/oneOf[subschema #1: OIDC WORKFORCE]/关联Orgs/items/roleMappings/items/roleAssignments/items/ 角色”响应属性
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“/oneOf[subschema #2: OIDC WORKLOAD]/关联Orgs/items/postAuthRoleGrants/items/”响应属性
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“/oneOf[subschema #2: OIDC WORKLOAD]/关联Orgs/items/roleMappings/items/roleAssignments/items/ 角色”响应属性
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“关联Orgs/items/postAuthRoleGrants/items/”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“关联Orgs/items/roleMappings/items/roleAssignments/items/ 角色”响应属性
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“/oneOf[subschema #1: SAML]/关联Orgs/items/postAuthRoleGrants/items/”响应属性
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“/oneOf[subschema #1: SAML]/关联Orgs/items/roleMappings/items/roleAssignments/items/ 角色”响应属性
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“/oneOf[subschema #2: OIDC WORKFORCE]/关联Orgs/items/postAuthRoleGrants/items/”响应属性
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“/oneOf[subschema #2: OIDC WORKFORCE]/关联Orgs/items/roleMappings/items/roleAssignments/items/ 角色”响应属性
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“/oneOf[subschema #3: OIDC WORKLOAD]/关联Orgs/items/postAuthRoleGrants/items/”响应属性
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“/oneOf[subschema #3: OIDC WORKLOAD]/关联Orgs/items/roleMappings/items/roleAssignments/items/ 角色”响应属性
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“关联Orgs/items/postAuthRoleGrants/items/”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“关联Orgs/items/roleMappings/items/roleAssignments/items/ 角色”响应属性
PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“/oneOf[subschema #1: SAML]/关联Orgs/items/postAuthRoleGrants/items/”响应属性
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“/oneOf[subschema #1: SAML]/关联Orgs/items/roleMappings/items/roleAssignments/items/ 角色”响应属性
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“/oneOf[subschema #2: OIDC WORKFORCE]/关联Orgs/items/postAuthRoleGrants/items/”响应属性
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“/oneOf[subschema #2: OIDC WORKFORCE]/关联Orgs/items/roleMappings/items/roleAssignments/items/ 角色”响应属性
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“/oneOf[subschema #3: OIDC WORKLOAD]/关联Orgs/items/postAuthRoleGrants/items/”响应属性
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“/oneOf[subschema #3: OIDC WORKLOAD]/关联Orgs/items/roleMappings/items/roleAssignments/items/ 角色”响应属性
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“关联Orgs/items/postAuthRoleGrants/items/”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“关联Orgs/items/roleMappings/items/roleAssignments/items/ 角色”响应属性
POST /api/atlas/v2/groups/{groupId}/access
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roles/items/”响应属性中
GET /api/atlas/v2/groups/{groupId}/apiKeys
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“results/items/roles/items/roleName”响应属性
POST /api/atlas/v2/groups/{groupId}/apiKeys
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roles/items/roleName”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到请求属性“roles/items/”
PATCH /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roles/items/roleName”响应属性中
POST /api/atlas/v2/groups/{groupId}/users/{userId}:addRole
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“/roles/orgRoles/items/”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roles/orgRoles/items/”响应属性中
POST /api/atlas/v2/groups/{groupId}/users/{userId}:removeRole
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“/roles/orgRoles/items/”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roles/orgRoles/items/”响应属性中
POST /api/atlas/v2/orgs
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“apiKey/roles/items/roleName”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“serviceAccount/roles/items/”响应属性中
  • 已将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到请求属性“apiKey/roles/items/”
  • 已将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到请求属性“serviceAccount/roles/items/”
GET /api/atlas/v2/orgs/{orgId}/apiKeys
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“results/items/roles/items/roleName”响应属性
POST /api/atlas/v2/orgs/{orgId}/apiKeys
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roles/items/roleName”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到请求属性“roles/items/”
GET /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roles/items/roleName”响应属性中
PATCH /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roles/items/roleName”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到请求属性“roles/items/”
GET /api/atlas/v2/orgs/{orgId}/invites
Updated
  • 在 '/items/roles/items/' 响应属性中添加了新的 'ORG_STREAM_PROCESSING_ADMIN'枚举值
PATCH /api/atlas/v2/orgs/{orgId}/invites
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roles/items/”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到请求属性“roles/items/”
POST /api/atlas/v2/orgs/{orgId}/invites
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roles/items/”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到请求属性“roles/items/”
GET /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roles/items/”响应属性中
PATCH /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roles/items/”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到请求属性“roles/items/”
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“results/items/roles/items/”响应属性中
POST /api/atlas/v2/orgs/{orgId}/serviceAccounts
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roles/items/”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到请求属性“roles/items/”
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roles/items/”响应属性中
PATCH /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roles/items/”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到请求属性“roles/items/”
GET /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“results/items/roles/orgRoles/items/”响应属性
POST /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“results/items/roles/items/roleName”响应属性
POST /api/atlas/v2/orgs/{orgId}/teams/{teamId}:addUser
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“/roles/orgRoles/items/”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roles/orgRoles/items/”响应属性中
POST /api/atlas/v2/orgs/{orgId}/teams/{teamId}:removeUser
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“/roles/orgRoles/items/”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roles/orgRoles/items/”响应属性中
GET /api/atlas/v2/orgs/{orgId}/users
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“results/items/roles/orgRoles/items/”响应属性
POST /api/atlas/v2/orgs/{orgId}/users
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“/roles/orgRoles/items/”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roles/orgRoles/items/”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到请求属性“roles/orgRoles/items/”
GET /api/atlas/v2/orgs/{orgId}/users/{userId}
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“/roles/orgRoles/items/”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roles/orgRoles/items/”响应属性中
PATCH /api/atlas/v2/orgs/{orgId}/users/{userId}
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“/roles/orgRoles/items/”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roles/orgRoles/items/”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到请求属性“roles/orgRoles/items/”
PUT /api/atlas/v2/orgs/{orgId}/users/{userId}/roles
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“orgRoles/items/”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到请求属性“orgRoles/items/”
POST /api/atlas/v2/orgs/{orgId}/users/{userId}:addRole
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“/roles/orgRoles/items/”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roles/orgRoles/items/”响应属性中
  • 已将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到请求属性“orgRole”
POST /api/atlas/v2/orgs/{orgId}/users/{userId}:removeRole
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“/roles/orgRoles/items/”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roles/orgRoles/items/”响应属性中
  • 已将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到请求属性“orgRole”
POST /api/atlas/v2/users
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roles/items/roleName”响应属性中
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到请求属性“roles/items/roleName”
GET /api/atlas/v2/users/byName/{userName}
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roles/items/roleName”响应属性中
GET /api/atlas/v2/users/{userId}
Updated
  • 将新的“ORG_STREAM_PROCESSING_ADMIN”枚举值添加到“roles/items/roleName”响应属性中

2025 年 7 月 29 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“ASSERT_MSG”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/AssertMsgRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“ASSERT_REGULAR”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/AssertRegularRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“ASSERT_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/AssertUserRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“ASSERT_WARNING”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/AssertWarningRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“AVG_COMMAND_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/AvgCommandExecutionTimeTimeMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“AVG_READ_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/AvgReadExecutionTimeTimeMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“AVG_WRITE_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/AvgWriteExecutionTimeTimeMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“CACHE_BYTES_READ_INTO”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/CacheBytesReadIntoDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“CACHE_BYTES_WRITTEN_FROM”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/CacheBytesWrittenFromDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“CACHE_USAGE_DIRTY”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/CacheUsageDirtyDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“CACHE_USAGE_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/CacheUsageUsedDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“COMPUTED_MEMORY”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/ComputedMemoryDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“CONNECTIONS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ConnectionsRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“CONNECTIONS_MAX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ConnectionsMaxRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“CONNECTIONS_PERCENT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ConnectionsPercentRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“CURSORS_TOTAL_CLIENT_CURSORS_SIZE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“CURSORS_TOTAL_OPEN”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/CursorsTotalOpenRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“CURSORS_TOTAL_TIMED_OUT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/CursorsTotalTimedOutRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DB_DATA_SIZE_TOTAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/DbDataSizeTotalDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DB_DATA_SIZE_TOTAL_WO_SYSTEM”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DB_INDEX_SIZE_TOTAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/DbIndexSizeTotalDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DB_STORAGE_TOTAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/DbStorageTotalDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_QUEUE_DEPTH_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_QUEUE_DEPTH_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_QUEUE_DEPTH_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_READ_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_READ_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold，鉴别器键“DISK_PARTITION_READ_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_READ_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_READ_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_READ_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_SPACE_USED_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_SPACE_USED_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9：主机指标警报配置]/metricThreshold，鉴别器键“DISK_PARTITION_SPACE_USED_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionSpaceUsedJournalRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_WRITE_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_WRITE_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold，鉴别器键 'DISK_PARTITION_WRITE_IOPS_JOURNAL' 的映射值从 '#/components/schemas/RawMetricThresholdView' 更改为 '#/components/schemas/DiskPartitionWriteIopsJournalRawMetricThresholdView' ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_WRITE_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_WRITE_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_WRITE_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DOCUMENT_DELETED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DocumentDeletedRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DOCUMENT_INSERTED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DocumentInsertedRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DOCUMENT_RETURNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DocumentReturnedRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DOCUMENT_UPDATED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DocumentUpdatedRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“EXTRA_INFO_PAGE_FAULTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“FTS_DISK_UTILIZATION”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FtsDiskUtilizationDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“FTS_JVM_CURRENT_MEMORY”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“FTS_JVM_MAX_MEMORY”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“FTS_MEMORY_MAPPED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FtsMemoryMappedDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“FTS_MEMORY_RESIDENT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FtsMemoryResidentDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“FTS_MEMORY_VIRTUAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FtsMemoryVirtualDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“FTS_PROCESS_CPU_KERNEL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FtsProcessCpuKernelRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“FTS_PROCESS_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FtsProcessCpuUserRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“GLOBAL_ACCESSES_NOT_IN_MEMORY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalAccessesNotInMemoryRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“GLOBAL_LOCK_CURRENT_QUEUE_READERS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“GLOBAL_LOCK_CURRENT_QUEUE_TOTAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“GLOBAL_LOCK_CURRENT_QUEUE_WRITERS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“GLOBAL_LOCK_PERCENTAGE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockPercentageRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“GLOBAL_PAGE_FAULT_EXCEPTIONS_THROWN”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalPageFaultExceptionsThrownRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“INDEX_COUNTERS_BTREE_ACCESSES”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“INDEX_COUNTERS_BTREE_HITS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeHitsRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“INDEX_COUNTERS_BTREE_MISSES”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeMissesRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold，鉴别器键“INDEX_COUNTERS_BTREE_MISS_RATIO”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeMissRatioRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“JOURNALING_COMMITS_IN_WRITE_LOCK”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“JOURNALING_MB”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/JournalingMbDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“JOURNALING_WRITE_DATA_FILES_MB”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“LOGICAL_SIZE”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/LogicalSizeDataMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold，鉴别器键“MAX_DISK_PARTITION_QUEUE_DEPTH_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionQueueDepthDataRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold，鉴别器键“MAX_DISK_PARTITION_QUEUE_DEPTH_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_DISK_PARTITION_QUEUE_DEPTH_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_DISK_PARTITION_READ_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold，鉴别器键“MAX_DISK_PARTITION_READ_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_DISK_PARTITION_READ_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_DISK_PARTITION_READ_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_DISK_PARTITION_READ_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_DISK_PARTITION_READ_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_DISK_PARTITION_SPACE_USED_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionSpaceUsedDataRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold，鉴别器键“MAX_DISK_PARTITION_SPACE_USED_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionSpaceUsedIndexRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_DISK_PARTITION_SPACE_USED_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionSpaceUsedJournalRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_DISK_PARTITION_WRITE_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold，鉴别器键“MAX_DISK_PARTITION_WRITE_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_DISK_PARTITION_WRITE_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold，鉴别器键“MAX_DISK_PARTITION_WRITE_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold，鉴别器键“MAX_DISK_PARTITION_WRITE_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_DISK_PARTITION_WRITE_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView” ' 响应属性
  • 针对 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold，鉴别器键 'MAX_NORMALIZED_SYSTEM_CPU_STEAL' 的映射值从 '#/components/schemas/RawMetricThresholdView' 更改为 '#/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView' ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_NORMALIZED_SYSTEM_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_SWAP_USAGE_FREE”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSwapUsageFreeDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_SWAP_USAGE_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSwapUsageUsedDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_SYSTEM_MEMORY_AVAILABLE”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9：主机指标警报配置]/metricThreshold，鉴别器键“MAX_SYSTEM_MEMORY_PERCENT_USED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_SYSTEM_MEMORY_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_SYSTEM_NETWORK_IN”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSystemNetworkInDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_SYSTEM_NETWORK_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSystemNetworkOutDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MEMORY_MAPPED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MemoryMappedDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MEMORY_RESIDENT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MemoryResidentDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MEMORY_VIRTUAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MemoryVirtualDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MUNIN_CPU_IOWAIT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MuninCpuIowawaitRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MUNIN_CPU_IRQ”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MuninCpuIrqRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MUNIN_CPU_NICE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MuninCpuNiceRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MUNIN_CPU_SOFTIRQ”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MuninCpuSoftirqRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MUNIN_CPU_STEAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MuninCpuStealRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MUNIN_CPU_SYSTEM”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MuninCpuSystemRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MUNIN_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MuninCpuUserRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“NETWORK_BYTES_IN”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/NetworkBytesInDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“NETWORK_BYTES_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/NetworkBytesOutDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“NETWORK_NUM_REQUESTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NetworkNumRequestsRawMetricThresholdView” ' 响应属性
  • 针对 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold，鉴别器键 'NORMALIZED_FTS_PROCESS_CPU_KERNEL' 的映射值从 '#/components/schemas/RawMetricThresholdView' 更改为 '#/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView' ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“NORMALIZED_FTS_PROCESS_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“NORMALIZED_SYSTEM_CPU_STEAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“NORMALIZED_SYSTEM_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPCOUNTER_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterCmdRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterDeleteRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterGetMoreRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterInsertRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPCOUNTER_QUERY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterQueryRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPCOUNTER_REPL_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterReplCmdRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPCOUNTER_REPL_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterReplDeleteRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPCOUNTER_REPL_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterReplInsertRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPCOUNTER_REPL_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterReplUpdateRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPCOUNTER_TTL_DELETED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterTtlDeletedRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterUpdateRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPERATIONS_QUERIES_KILLED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OperationsQueriesKilledRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPERATIONS_SCAN_AND_ORDER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OperationsScanAndOrderRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPERATION_THROTTLING_REJECTED_OPERATIONS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OperationThrotdlingRejectedOperationsRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPLOG_MASTER_LAG_TIME_DIFF”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView” ' 响应属性
  • 对于 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold，鉴别器键 'OPLOG_MASTER_TIME' 的映射值从 '#/components/schemas/TimeMetricThresholdView' 更改为 '#/components/schemas/OplogMasterTimeTimeMetricThresholdView' ' 响应属性
  • 针对“results/items/oneOf[subschema #9：主机指标警报配置]/metricThreshold，鉴别器键“OPLOG_MASTER_TIME_ESTIMATED_TTL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPLOG_RATE_GB_PER_HOUR”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/OplogRateGbPerHourDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPLOG_SLAVE_LAG_MASTER_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogSlaveLagMasterTimeTimeMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“QUERY_EXECUTOR_SCANNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QueryExecutorScannedRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“QUERY_EXECUTOR_SCANNED_OBJECTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView” ' 响应属性
  • 鉴别器键“QUERY_SPILL_TO_DISK_DURING_SORT”的映射值从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView”（针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold） ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“QUERY_TARGETING_SCANNED_OBJECTS_PER_RETURNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“QUERY_TARGETING_SCANNED_PER_RETURNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“RESTARTS_IN_LAST_HOUR”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/RestartsInLastHourRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SEARCH_INDEX_SIZE”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SearchIndexSizeDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SEARCH_NUMBER_OF_FIELDS_IN_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfFieldsInIndexRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SEARCH_NUMBER_OF_QUERIES_ERROR”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SEARCH_NUMBER_OF_QUERIES_SUCCESS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9：主机指标警报配置]/metricThreshold，鉴别器键“SEARCH_NUMBER_OF_QUERIES_TOTAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SEARCH_OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterDeleteRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SEARCH_OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SEARCH_OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterInsertRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SEARCH_OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterUpdateRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SEARCH_REPLICATION_LAG”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/SearchReplicationLagTimeMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SWAP_USAGE_FREE”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SwapUsageFreeDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SWAP_USAGE_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SwapUsageUsedDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SYSTEM_MEMORY_AVAILABLE”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SystemMemoryAvailableDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SYSTEM_MEMORY_PERCENT_USED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SYSTEM_MEMORY_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SystemMemoryUsedDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SYSTEM_NETWORK_IN”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SystemNetworkInDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SYSTEM_NETWORK_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SystemNetworkOutDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“TICKETS_AVAILABLE_READS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/TicketsAvailableReadsRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“TICKETS_AVAILABLE_WRITES”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/TicketsAvailableWritesRawMetricThresholdView” ' 响应属性
  • 添加 '#/components/schemas/AssertRegularRawMetricThresholdView, #/components/schemas/AssertWarningRawMetricThresholdView, #/components/schemas/AssertMsgRawMetricThresholdView, #/components/schemas/AssertUserRawMetricThresholdView, #/components/schemas/OpCounterCmdRawMetricThresholdView, #/components/schemas/OpCounterCmdRawMetricThresholdView, #/components/schemas/OpCounterRawMetricThresholdView, #/components/schemas/OpCounterCmdRawMetricThresholdView, #/components/schemas/OpCounterUpdateRawMetricThresholdView, #/components/schemas/OpCounterDeleteRawMetricThresholdView, #/components/schemas/OpCounterTtlDeletedRawMetricThresholdView, #/components/schemas/OpCounterInsertRawMetricThresholdView, #/components/schemas/OpCounterGetMoreRawMetricThresholdView, #/components/schemas/OpCounterGetMoreRawMetricReplas/OpCounterMetricReplas/schemeView components/schemas/OpCounterReplUpdateRawMetricThresholdView, #/components/schemas/OpCounterReplDeleteRawMetricThresholdView, #/components/schemas/OpCounterReplInsertRawMetricThresholdView, #/components/schemas/FtsMemoryResidentDataMetricThresholdView, #/components/schemas/FtsMemoryV irtualDataMetricThresholdView, #/components/schemas/FtsMemoryMappedDataMetricThresholdView, #/components/schemas/FtsProcessCpuUserRawMetricThresholdView, #/components/schemas/FtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MemoryResidentDataMetricThresholdView, #/components/schemas/MemoryVirtualDataMetricThresholdView, #/components/schemas/MemoryMappedDataMetricThresholdView, #/components/schemas/ComputedMemoryDataMetricThresholdView, #/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdView, #/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdViewHitsMetric components/schemas/IndexCountersBtreeMissesRawMetricThresholdView, #/components/schemas/IndexCountersBtreeMissRatioRawMetricThresholdView, #/components/schemas/GlobalLockPercentageRawMetricTh resholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/ConnectionsRawMetricThresholdView, #/components/schemas/ConnectionsMaxRawMetricThresholdView, #/components/schemas/ConnectionsPercentRawMetricThresholdView, #/components/schemas/GlobalAccessesNotInMemoryRawMetricThresholdView, #/components/schemas/GlobalPageFaultRawMetricThrownMetricThrownView #/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView, #/components/schemas/CursorsTotalOpenRawMetricThresholdView, #/components/schemas/CursorsTotalTimedOutRawMetricThresholdView, #/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView, #/ components/schemas/NetworkBytesInDataMetricThresholdView, #/components/schemas/NetworkBytesOutDataMetricThresholdView, #/components/schemas/NetworkNumRequestsRawMetricThresholdView, #/components/ schemas/OplogMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView, #/components/schemas/OplogSlaveLagMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView, #/components/schemas/OplogRateGbPerHourDataMetricThresholdView, #/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView, #/components/schemas/ DbStorageTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView, #/components/schemas/DbIndexSizeTotalDataMetricThresholdView, #/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView, #/components/schemas/JournalingMbDataMetricThresholdView, #/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView, #/components/schemas/TicketsAvailableReadsRawMetricThresholdView, #/components/schemas/TicketsAvailableWritesRawMetricThresholdView, #/components/schemas/Cache UsageDirtyDataMetricThresholdView, #/components/schemas/CacheUsageUsedDataMetricThresholdView, #/components/schemas/CacheBytesReadIntoDataMetricThresholdView, #/components/schemas/CacheBytesWrittenFromDataMetricThresholdView, #/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView, #/ components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsJournalRawMetricThre sholdView, #/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/FtsDiskUtilizationDataMetricThresholdView, #/components/schemas/MuninCpuUserRawMetricThresholdView, #/components/schemas/MuninCpuNiceRawMetricThresholdView, #/ components/schemas/MuninCpuSystemRawMetricThresholdView, #/components/schemas/MuninCpuIowaitRawMetricThresholdView, #/components/schem as/MuninCpuIrqRawMetricThresholdView, #/components/schemas/MuninCpuSoftirqRawMetricThresholdView, #/components/schemas/MuninCpuStealRawMetricThresholdView, #/components/schemas/DocumentReturnedRawMetricThresholdView, #/components/schemas/DocumentInsertedRawMetricThresholdView, #/components/schemas/MuninCpuStealRawMetricThresholdView, #/components/schemas/DocumentInsertedRawMetricThresholdView, #/components/schemas/componentsRawMetricThresholdView DocumentDeletedRawMetricThresholdView, #/components/schemas/OperationsScanAndOrderRawMetricThresholdView, #/components/schemas/QueryExecutorScannedRawMetricThresholdView, #/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView, #/components/schemas/OperationThrottlingRejectedOperationsRawMetricThresholdView, #/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView, #/components/schemas/OperationsQueriesKilledRawMetricThresholdView, #/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView, #/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView, #/components/sch emas/AvgReadExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgWriteExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgCommandExecutionTimeTimeMetricThresholdView, #/components/schemas/LogicalSizeDataMetricThresholdView, #/components/schemas/RestartsInLastHourRawMetricThresholdView, #/components/schemas/SystemMemtricThoryschem SystemMemoryAvailableDataMetricThresholdView, #/components/schemas/SwapUsageUsedDataMetricThresholdView, #/components/schemas/SwapUsageFreeDataMetricThresholdView, #/components/schemas/SystemNetworkInDataMetricThresholdView, #/components/schemas/SystemNetworkOutDataMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/MaxDiskPartitionSpaceUsedDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionSpaceUsedIndexRawMetricThresholdView, #/components/schemas/MaxDiskPart itionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/ components/schemas/MaxDiskParti tionQueueDepthDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView, #/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView, #/components/schemas/MaxSwapUsageUsedDataMetricThresholdView, #/components/schemas/MaxSwapUsageFreeDataMetricThresholdView, #/components/schemas/MaxSystemNetworkInDataMetricThresholdView, #/components/schemas/MaxSystemNetworkOutDataMetricThresholdView, #/components/schemas/SearchIndexSizeDataMetricThresholdView, #/components/schemas/SearchNumberOfFieldsInIndexRawMetricThresholdView, #/components/schemas/SearchRealThresholdView, #/components/schemas/SearchRealThresholdView, components/schemas/NumberMetricThresholdView, #/components/schemas/SearchOpCounterInsertRawMetricThresholdView, #/components/schemas/SearchOpCou nterDeleteRawMetricThresholdView, #/components/schemas/SearchOpCounterUpdateRawMetricThresholdView, #/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView, #/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView, #/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView”添加到该响应的“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性“oneOf”列表
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“ASSERT_MSG”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/AssertMsgRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“ASSERT_REGULAR”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/AssertRegularRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“ASSERT_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/AssertUserRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“ASSERT_WARNING”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/AssertWarningRawMetricThresholdView”更改为“#/components/schemas/AssertWarningRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“AVG_COMMAND_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/AvgCommandExecutionTimeTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“AVG_READ_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/AvgReadExecutionTimeTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“AVG_WRITE_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/AvgWriteExecutionTimeTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“CACHE_BYTES_READ_INTO”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/CacheBytesReadIntoDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“CACHE_BYTES_WRITTEN_FROM”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/CacheBytesWrittenFromDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“CACHE_USAGE_DIRTY”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/CacheUsageDirtyDataMetricThresholdView”更改为“#/components/schemas/CacheUsageDirtyDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“CACHE_USAGE_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/CacheUsageUsedDataMetricThresholdView”更改为“#/components/schemas/CacheUsageUsedDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“COMPUTED_MEMORY”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/ComputedMemoryDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“CONNECTIONS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ConnectionsRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“CONNECTIONS_MAX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ConnectionsMaxRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“CONNECTIONS_PERCENT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ConnectionsPercentRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“CURSORS_TOTAL_CLIENT_CURSORS_SIZE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“CURSORS_TOTAL_OPEN”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/CursorsTotalOpenRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“CURSORS_TOTAL_TIMED_OUT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/CursorsTotalTimedOutRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DB_DATA_SIZE_TOTAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DbDataSizeTotalDataMetricThresholdView”更改为“#/components/schemas/DbDataSizeTotalDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DB_DATA_SIZE_TOTAL_WO_SYSTEM”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DB_INDEX_SIZE_TOTAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DbIndexSizeTotalDataMetricThresholdView”更改为“#/components/schemas/DbIndexSizeTotalDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DB_STORAGE_TOTAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DbStorageTotalDataMetricThresholdView”更改为“#/components/schemas/DbStorageTotalDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_QUEUE_DEPTH_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_QUEUE_DEPTH_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_QUEUE_DEPTH_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_READ_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_READ_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_READ_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_READ_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_READ_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_READ_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_SPACE_USED_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_SPACE_USED_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_SPACE_USED_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionSpaceUsedJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_WRITE_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_WRITE_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_WRITE_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteIopsJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_WRITE_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_WRITE_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_WRITE_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DOCUMENT_DELETED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DocumentDeletedRawMetricThresholdView”更改为“#/components/schemas/DocumentDeletedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DOCUMENT_INSERTED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DocumentInsertedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DOCUMENT_RETURNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DocumentReturnedRawMetricThresholdView”更改为“#/components/schemas/DocumentReturnedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DOCUMENT_UPDATED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DocumentUpdatedRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“EXTRA_INFO_PAGE_FAULTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“FTS_DISK_UTILIZATION”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FtsDiskUtilizationDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“FTS_JVM_CURRENT_MEMORY”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“FTS_JVM_MAX_MEMORY”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView”更改为“#/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“FTS_MEMORY_MAPPED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FtsMemoryMappedDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“FTS_MEMORY_RESIDENT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/FtsMemoryResidentDataMetricThresholdView”更改为“#/components/schemas/FtsMemoryResidentDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“FTS_MEMORY_VIRTUAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/FtsMemoryVirtualDataMetricThresholdView”更改为“#/components/schemas/FtsMemoryVirtualDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“FTS_PROCESS_CPU_KERNEL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FtsProcessCpuKernelRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“FTS_PROCESS_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FtsProcessCpuUserRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“GLOBAL_ACCESSES_NOT_IN_MEMORY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalAccessesNotInMemoryRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“GLOBAL_LOCK_CURRENT_QUEUE_READERS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“GLOBAL_LOCK_CURRENT_QUEUE_TOTAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“GLOBAL_LOCK_CURRENT_QUEUE_WRITERS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“GLOBAL_LOCK_PERCENTAGE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockPercentageRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“GLOBAL_PAGE_FAULT_EXCEPTIONS_THROWN”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalPageFaultExceptionsThrownRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“INDEX_COUNTERS_BTREE_ACCESSES”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“INDEX_COUNTERS_BTREE_HITS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeHitsRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“INDEX_COUNTERS_BTREE_MISSES”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeMissesRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“INDEX_COUNTERS_BTREE_MISS_RATIO”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeMissRatioRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“JOURNALING_COMMITS_IN_WRITE_LOCK”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“JOURNALING_MB”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/JournalingMbDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“JOURNALING_WRITE_DATA_FILES_MB”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView”更改为“#/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性的鉴别器键“LOGICAL_SIZE”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/LogicalSizeDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_QUEUE_DEPTH_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionQueueDepthDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_QUEUE_DEPTH_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_QUEUE_DEPTH_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_READ_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_READ_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_READ_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_READ_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_READ_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_READ_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_SPACE_USED_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MaxDiskPartitionSpaceUsedDataRawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionSpaceUsedDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_SPACE_USED_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionSpaceUsedIndexRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_SPACE_USED_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionSpaceUsedJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_WRITE_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_WRITE_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_WRITE_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_WRITE_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_WRITE_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_WRITE_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_NORMALIZED_SYSTEM_CPU_STEAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_NORMALIZED_SYSTEM_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_SWAP_USAGE_FREE”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/MaxSwapUsageFreeDataMetricThresholdView”更改为“#/components/schemas/MaxSwapUsageFreeDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_SWAP_USAGE_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/MaxSwapUsageUsedDataMetricThresholdView”更改为“#/components/schemas/MaxSwapUsageUsedDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_SYSTEM_MEMORY_AVAILABLE”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_SYSTEM_MEMORY_PERCENT_USED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_SYSTEM_MEMORY_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView”更改为“#/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_SYSTEM_NETWORK_IN”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSystemNetworkInDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_SYSTEM_NETWORK_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSystemNetworkOutDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MEMORY_MAPPED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/MemoryMappedDataMetricThresholdView”更改为“#/components/schemas/MemoryMappedDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MEMORY_RESIDENT”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MemoryResidentDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MEMORY_VIRTUAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/MemoryVirtualDataMetricThresholdView”更改为“#/components/schemas/MemoryVirtualDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MUNIN_CPU_IOWAIT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MuninCpuIowawaitRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MUNIN_CPU_IRQ”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MuninCpuIrqRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MUNIN_CPU_NICE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuNiceRawMetricThresholdView”更改为“#/components/schemas/MuninCpuNiceRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MUNIN_CPU_SOFTIRQ”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MuninCpuSoftirqRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MUNIN_CPU_STEAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuStealRawMetricThresholdView”更改为“#/components/schemas/MuninCpuStealRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MUNIN_CPU_SYSTEM”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuSystemRawMetricThresholdView”更改为“#/components/schemas/MuninCpuSystemRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MUNIN_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuUserRawMetricThresholdView”更改为“#/components/schemas/MuninCpuUserRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“NETWORK_BYTES_IN”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/NetworkBytesInDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“NETWORK_BYTES_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/NetworkBytesOutDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“NETWORK_NUM_REQUESTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NetworkNumRequestsRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“NORMALIZED_FTS_PROCESS_CPU_KERNEL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“NORMALIZED_FTS_PROCESS_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“NORMALIZED_SYSTEM_CPU_STEAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“NORMALIZED_SYSTEM_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPCOUNTER_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterCmdRawMetricThresholdView”更改为“#/components/schemas/OpCounterCmdRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterDeleteRawMetricThresholdView”更改为“#/components/schemas/OpCounterDeleteRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterGetMoreRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterInsertRawMetricThresholdView”更改为“#/components/schemas/OpCounterInsertRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPCOUNTER_QUERY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterQueryRawMetricThresholdView”更改为“#/components/schemas/OpCounterQueryRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPCOUNTER_REPL_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterReplCmdRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPCOUNTER_REPL_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterReplDeleteRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPCOUNTER_REPL_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterReplInsertRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPCOUNTER_REPL_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterReplUpdateRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPCOUNTER_TTL_DELETED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterTtlDeletedRawMetricThresholdView”更改为“#/components/schemas/OpCounterTtlDeletedRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterUpdateRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPERATIONS_QUERIES_KILLED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OperationsQueriesKilledRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPERATIONS_SCAN_AND_ORDER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OperationsScanAndOrderRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPERATION_THROTTLING_REJECTED_OPERATIONS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OperationThrotdlingRejectedOperationsRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPLOG_MASTER_LAG_TIME_DIFF”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPLOG_MASTER_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogMasterTimeTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPLOG_MASTER_TIME_ESTIMATED_TTL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPLOG_RATE_GB_PER_HOUR”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/OplogRateGbPerHourDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPLOG_SLAVE_LAG_MASTER_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogSlaveLagMasterTimeTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“QUERY_EXECUTOR_SCANNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QueryExecutorScannedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“QUERY_EXECUTOR_SCANNED_OBJECTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“QUERY_SPILL_TO_DISK_DURING_SORT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“QUERY_TARGETING_SCANNED_OBJECTS_PER_RETURNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“QUERY_TARGETING_SCANNED_PER_RETURNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“RESTARTS_IN_LAST_HOUR”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/RestartsInLastHourRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SEARCH_INDEX_SIZE”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SearchIndexSizeDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SEARCH_NUMBER_OF_FIELDS_IN_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfFieldsInIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SEARCH_NUMBER_OF_QUERIES_ERROR”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SEARCH_NUMBER_OF_QUERIES_SUCCESS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SEARCH_NUMBER_OF_QUERIES_TOTAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SEARCH_OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterDeleteRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SEARCH_OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SEARCH_OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterInsertRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SEARCH_OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterUpdateRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SEARCH_REPLICATION_LAG”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/SearchReplicationLagTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SWAP_USAGE_FREE”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SwapUsageFreeDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SWAP_USAGE_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/SwapUsageUsedDataMetricThresholdView”更改为“#/components/schemas/SwapUsageUsedDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SYSTEM_MEMORY_AVAILABLE”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/SystemMemoryAvailableDataMetricThresholdView”更改为“#/components/schemas/SystemMemoryAvailableDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SYSTEM_MEMORY_PERCENT_USED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SYSTEM_MEMORY_USED”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SystemMemoryUsedDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SYSTEM_NETWORK_IN”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SystemNetworkInDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SYSTEM_NETWORK_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/SystemNetworkOutDataMetricThresholdView”更改为“#/components/schemas/SystemNetworkOutDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“TICKETS_AVAILABLE_READS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/TicketsAvailableReadsRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“TICKETS_AVAILABLE_WRITES”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/TicketsAvailableWritesRawMetricThresholdView”
  • 添加 '#/components/schemas/AssertRegularRawMetricThresholdView, #/components/schemas/AssertWarningRawMetricThresholdView, #/components/schemas/AssertMsgRawMetricThresholdView, #/components/schemas/AssertUserRawMetricThresholdView, #/components/schemas/OpCounterCmdRawMetricThresholdView, #/components/schemas/OpCounterCmdRawMetricThresholdView, #/components/schemas/OpCounterRawMetricThresholdView, #/components/schemas/OpCounterCmdRawMetricThresholdView, #/components/schemas/OpCounterUpdateRawMetricThresholdView, #/components/schemas/OpCounterDeleteRawMetricThresholdView, #/components/schemas/OpCounterTtlDeletedRawMetricThresholdView, #/components/schemas/OpCounterInsertRawMetricThresholdView, #/components/schemas/OpCounterGetMoreRawMetricThresholdView, #/components/schemas/OpCounterGetMoreRawMetricReplas/OpCounterMetricReplas/schemeView components/schemas/OpCounterReplUpdateRawMetricThresholdView, #/components/schemas/OpCounterReplDeleteRawMetricThresholdView, #/components/schemas/OpCounterReplInsertRawMetricThresholdView, #/components/schemas/FtsMemoryResidentDataMetricThresholdView, #/components/schemas/FtsMemoryV irtualDataMetricThresholdView, #/components/schemas/FtsMemoryMappedDataMetricThresholdView, #/components/schemas/FtsProcessCpuUserRawMetricThresholdView, #/components/schemas/FtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MemoryResidentDataMetricThresholdView, #/components/schemas/MemoryVirtualDataMetricThresholdView, #/components/schemas/MemoryMappedDataMetricThresholdView, #/components/schemas/ComputedMemoryDataMetricThresholdView, #/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdView, #/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdViewHitsMetric components/schemas/IndexCountersBtreeMissesRawMetricThresholdView, #/components/schemas/IndexCountersBtreeMissRatioRawMetricThresholdView, #/components/schemas/GlobalLockPercentageRawMetricTh resholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/ConnectionsRawMetricThresholdView, #/components/schemas/ConnectionsMaxRawMetricThresholdView, #/components/schemas/ConnectionsPercentRawMetricThresholdView, #/components/schemas/GlobalAccessesNotInMemoryRawMetricThresholdView, #/components/schemas/GlobalPageFaultRawMetricThrownMetricThrownView #/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView, #/components/schemas/CursorsTotalOpenRawMetricThresholdView, #/components/schemas/CursorsTotalTimedOutRawMetricThresholdView, #/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView, #/ components/schemas/NetworkBytesInDataMetricThresholdView, #/components/schemas/NetworkBytesOutDataMetricThresholdView, #/components/schemas/NetworkNumRequestsRawMetricThresholdView, #/components/ schemas/OplogMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView, #/components/schemas/OplogSlaveLagMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView, #/components/schemas/OplogRateGbPerHourDataMetricThresholdView, #/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView, #/components/schemas/ DbStorageTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView, #/components/schemas/DbIndexSizeTotalDataMetricThresholdView, #/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView, #/components/schemas/JournalingMbDataMetricThresholdView, #/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView, #/components/schemas/TicketsAvailableReadsRawMetricThresholdView, #/components/schemas/TicketsAvailableWritesRawMetricThresholdView, #/components/schemas/Cache UsageDirtyDataMetricThresholdView, #/components/schemas/CacheUsageUsedDataMetricThresholdView, #/components/schemas/CacheBytesReadIntoDataMetricThresholdView, #/components/schemas/CacheBytesWrittenFromDataMetricThresholdView, #/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView, #/ components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsJournalRawMetricThre sholdView, #/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/FtsDiskUtilizationDataMetricThresholdView, #/components/schemas/MuninCpuUserRawMetricThresholdView, #/components/schemas/MuninCpuNiceRawMetricThresholdView, #/ components/schemas/MuninCpuSystemRawMetricThresholdView, #/components/schemas/MuninCpuIowaitRawMetricThresholdView, #/components/schem as/MuninCpuIrqRawMetricThresholdView, #/components/schemas/MuninCpuSoftirqRawMetricThresholdView, #/components/schemas/MuninCpuStealRawMetricThresholdView, #/components/schemas/DocumentReturnedRawMetricThresholdView, #/components/schemas/DocumentInsertedRawMetricThresholdView, #/components/schemas/MuninCpuStealRawMetricThresholdView, #/components/schemas/DocumentInsertedRawMetricThresholdView, #/components/schemas/componentsRawMetricThresholdView DocumentDeletedRawMetricThresholdView, #/components/schemas/OperationsScanAndOrderRawMetricThresholdView, #/components/schemas/QueryExecutorScannedRawMetricThresholdView, #/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView, #/components/schemas/OperationThrottlingRejectedOperationsRawMetricThresholdView, #/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView, #/components/schemas/OperationsQueriesKilledRawMetricThresholdView, #/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView, #/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView, #/components/sch emas/AvgReadExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgWriteExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgCommandExecutionTimeTimeMetricThresholdView, #/components/schemas/LogicalSizeDataMetricThresholdView, #/components/schemas/RestartsInLastHourRawMetricThresholdView, #/components/schemas/SystemMemtricThoryschem SystemMemoryAvailableDataMetricThresholdView, #/components/schemas/SwapUsageUsedDataMetricThresholdView, #/components/schemas/SwapUsageFreeDataMetricThresholdView, #/components/schemas/SystemNetworkInDataMetricThresholdView, #/components/schemas/SystemNetworkOutDataMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/MaxDiskPartitionSpaceUsedDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionSpaceUsedIndexRawMetricThresholdView, #/components/schemas/MaxDiskPart itionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/ components/schemas/MaxDiskParti tionQueueDepthDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView, #/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView, #/components/schemas/MaxSwapUsageUsedDataMetricThresholdView, #/components/schemas/MaxSwapUsageFreeDataMetricThresholdView, #/components/schemas/MaxSystemNetworkInDataMetricThresholdView, #/components/schemas/MaxSystemNetworkOutDataMetricThresholdView, #/components/schemas/SearchIndexSizeDataMetricThresholdView, #/components/schemas/SearchNumberOfFieldsInIndexRawMetricThresholdView, #/components/schemas/SearchRealThresholdView, #/components/schemas/SearchRealThresholdView, components/schemas/NumberMetricThresholdView, #/components/schemas/SearchOpCounterInsertRawMetricThresholdView, #/components/schemas/SearchOpCou nterDeleteRawMetricThresholdView, #/components/schemas/SearchOpCounterUpdateRawMetricThresholdView, #/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView, #/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView, #/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView”添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性“oneOf”列表
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“ASSERT_MSG”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/AssertMsgRawMetricThresholdView”更改为“#/components/schemas/AssertMsgRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“ASSERT_REGULAR”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/AssertRegularRawMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“ASSERT_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/AssertUserRawMetricThresholdView”更改为“#/components/schemas/AssertUserRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“ASSERT_WARNING”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/AssertWarningRawMetricThresholdView”更改为“#/components/schemas/AssertWarningRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“AVG_COMMAND_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/AvgCommandExecutionTimeTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“AVG_READ_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/AvgReadExecutionTimeTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“AVG_WRITE_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/AvgWriteExecutionTimeTimeMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“CACHE_BYTES_READ_INTO”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/CacheBytesReadIntoDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CACHE_BYTES_WRITTEN_FROM”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/CacheBytesWrittenFromDataMetricThresholdView”更改为“#/components/schemas/CacheBytesWrittenFromDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CACHE_USAGE_DIRTY”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/CacheUsageDirtyDataMetricThresholdView”更改为“#/components/schemas/CacheUsageDirtyDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CACHE_USAGE_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/CacheUsageUsedDataMetricThresholdView”更改为“#/components/schemas/CacheUsageUsedDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“COMPUTED_MEMORY”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/ComputedMemoryDataMetricThresholdView”更改
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CONNECTIONS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ConnectionsRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CONNECTIONS_MAX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ConnectionsMaxRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CONNECTIONS_PERCENT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/ConnectionsPercentRawMetricThresholdView”更改为“#/components/schemas/ConnectionsPercentRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CURSORS_TOTAL_CLIENT_CURSORS_SIZE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CURSORS_TOTAL_OPEN”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/CursorsTotalOpenRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CURSORS_TOTAL_TIMED_OUT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/CursorsTotalTimedOutRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DB_DATA_SIZE_TOTAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DbDataSizeTotalDataMetricThresholdView”更改为“#/components/schemas/DbDataSizeTotalDataMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“DB_DATA_SIZE_TOTAL_WO_SYSTEM”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DB_INDEX_SIZE_TOTAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DbIndexSizeTotalDataMetricThresholdView”更改为“#/components/schemas/DbIndexSizeTotalDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DB_STORAGE_TOTAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DbStorageTotalDataMetricThresholdView”更改为“#/components/schemas/DbStorageTotalDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_QUEUE_DEPTH_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_QUEUE_DEPTH_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_QUEUE_DEPTH_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_READ_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_READ_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_READ_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_READ_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_READ_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_READ_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_SPACE_USED_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_SPACE_USED_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_SPACE_USED_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionSpaceUsedJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_WRITE_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_WRITE_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_WRITE_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteIopsJournalRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_WRITE_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_WRITE_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_WRITE_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DOCUMENT_DELETED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DocumentDeletedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DOCUMENT_INSERTED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DocumentInsertedRawMetricThresholdView”更改为“#/components/schemas/DocumentInsertedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DOCUMENT_RETURNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DocumentReturnedRawMetricThresholdView”更改为“#/components/schemas/DocumentReturnedRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DOCUMENT_UPDATED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DocumentUpdatedRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“EXTRA_INFO_PAGE_FAULTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“FTS_DISK_UTILIZATION”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FtsDiskUtilizationDataMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“FTS_JVM_CURRENT_MEMORY”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“FTS_JVM_MAX_MEMORY”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView”更改为“#/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“FTS_MEMORY_MAPPED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/FtsMemoryMappedDataMetricThresholdView”更改为“#/components/schemas/FtsMemoryMappedDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“FTS_MEMORY_RESIDENT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/FtsMemoryResidentDataMetricThresholdView”更改为“#/components/schemas/FtsMemoryResidentDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“FTS_MEMORY_VIRTUAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/FtsMemoryVirtualDataMetricThresholdView”更改为“#/components/schemas/FtsMemoryVirtualDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“FTS_PROCESS_CPU_KERNEL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FtsProcessCpuKernelRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“FTS_PROCESS_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FtsProcessCpuUserRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“GLOBAL_ACCESSES_NOT_IN_MEMORY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalAccessesNotInMemoryRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“GLOBAL_LOCK_CURRENT_QUEUE_READERS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“GLOBAL_LOCK_CURRENT_QUEUE_TOTAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“GLOBAL_LOCK_CURRENT_QUEUE_WRITERS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“GLOBAL_LOCK_PERCENTAGE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockPercentageRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“GLOBAL_PAGE_FAULT_EXCEPTIONS_THROWN”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalPageFaultExceptionsThrownRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“INDEX_COUNTERS_BTREE_ACCESSES”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“INDEX_COUNTERS_BTREE_HITS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeHitsRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“INDEX_COUNTERS_BTREE_MISSES”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeMissesRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“INDEX_COUNTERS_BTREE_MISS_RATIO”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeMissRatioRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“JOURNALING_COMMITS_IN_WRITE_LOCK”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“JOURNALING_MB”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/JournalingMbDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“JOURNALING_WRITE_DATA_FILES_MB”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView”更改为“#/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“LOGICAL_SIZE”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/LogicalSizeDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_QUEUE_DEPTH_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionQueueDepthDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_QUEUE_DEPTH_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_QUEUE_DEPTH_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_READ_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_READ_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_READ_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_READ_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_READ_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_READ_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_SPACE_USED_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MaxDiskPartitionSpaceUsedDataRawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionSpaceUsedDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_SPACE_USED_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionSpaceUsedIndexRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_SPACE_USED_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionSpaceUsedJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_WRITE_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_WRITE_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_WRITE_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_WRITE_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_WRITE_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_WRITE_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_NORMALIZED_SYSTEM_CPU_STEAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_NORMALIZED_SYSTEM_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“MAX_SWAP_USAGE_FREE”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSwapUsageFreeDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_SWAP_USAGE_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/MaxSwapUsageUsedDataMetricThresholdView”更改为“#/components/schemas/MaxSwapUsageUsedDataMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“MAX_SYSTEM_MEMORY_AVAILABLE”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_SYSTEM_MEMORY_PERCENT_USED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_SYSTEM_MEMORY_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView”更改为“#/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_SYSTEM_NETWORK_IN”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSystemNetworkInDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_SYSTEM_NETWORK_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/MaxSystemNetworkOutDataMetricThresholdView”更改为“#/components/schemas/MaxSystemNetworkOutDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MEMORY_MAPPED”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MemoryMappedDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MEMORY_RESIDENT”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MemoryResidentDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MEMORY_VIRTUAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/MemoryVirtualDataMetricThresholdView”更改为“#/components/schemas/MemoryVirtualDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MUNIN_CPU_IOWAIT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuIowaitRawMetricThresholdView”更改为“#/components/schemas/MuninCpuIowawaitRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MUNIN_CPU_IRQ”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuIrqRawMetricThresholdView”更改为“#/components/schemas/MuninCpuIrqRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MUNIN_CPU_NICE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuNiceRawMetricThresholdView”更改为“#/components/schemas/MuninCpuNiceRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MUNIN_CPU_SOFTIRQ”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MuninCpuSoftirqRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MUNIN_CPU_STEAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuStealRawMetricThresholdView”更改为“#/components/schemas/MuninCpuStealRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MUNIN_CPU_SYSTEM”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuSystemRawMetricThresholdView”更改为“#/components/schemas/MuninCpuSystemRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MUNIN_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuUserRawMetricThresholdView”更改为“#/components/schemas/MuninCpuUserRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“NETWORK_BYTES_IN”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/NetworkBytesInDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“NETWORK_BYTES_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/NetworkBytesOutDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“NETWORK_NUM_REQUESTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NetworkNumRequestsRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“NORMALIZED_FTS_PROCESS_CPU_KERNEL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“NORMALIZED_FTS_PROCESS_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“NORMALIZED_SYSTEM_CPU_STEAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView”更改为“#/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“NORMALIZED_SYSTEM_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView”更改为“#/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterCmdRawMetricThresholdView”更改为“#/components/schemas/OpCounterCmdRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterDeleteRawMetricThresholdView”更改为“#/components/schemas/OpCounterDeleteRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterGetMoreRawMetricThresholdView”更改为“#/components/schemas/OpCounterGetMoreRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterInsertRawMetricThresholdView”更改为“#/components/schemas/OpCounterInsertRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_QUERY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterQueryRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_REPL_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterReplCmdRawMetricThresholdView”更改为“#/components/schemas/OpCounterReplCmdRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_REPL_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterReplDeleteRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_REPL_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterReplInsertRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_REPL_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterReplUpdateRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_TTL_DELETED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterTtlDeletedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterUpdateRawMetricThresholdView”更改为“#/components/schemas/OpCounterUpdateRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPERATIONS_QUERIES_KILLED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OperationsQueriesKilledRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPERATIONS_SCAN_AND_ORDER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OperationsScanAndOrderRawMetricThresholdView”
  • 已针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPERATION_THROTTLING_REJECTED_OPERATIONS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OperationThrotdlingRejectedOperationsRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPLOG_MASTER_LAG_TIME_DIFF”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPLOG_MASTER_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogMasterTimeTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPLOG_MASTER_TIME_ESTIMATED_TTL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“OPLOG_RATE_GB_PER_HOUR”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/OplogRateGbPerHourDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPLOG_SLAVE_LAG_MASTER_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogSlaveLagMasterTimeTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“QUERY_EXECUTOR_SCANNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/QueryExecutorScannedRawMetricThresholdView”更改为“#/components/schemas/QueryExecutorScannedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“QUERY_EXECUTOR_SCANNED_OBJECTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“QUERY_SPILL_TO_DISK_DURING_SORT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“QUERY_TARGETING_SCANNED_OBJECTS_PER_RETURNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“QUERY_TARGETING_SCANNED_PER_RETURNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“RESTARTS_IN_LAST_HOUR”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/RestartsInLastHourRawMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“SEARCH_INDEX_SIZE”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SearchIndexSizeDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_NUMBER_OF_FIELDS_IN_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfFieldsInIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_NUMBER_OF_QUERIES_ERROR”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_NUMBER_OF_QUERIES_SUCCESS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_NUMBER_OF_QUERIES_TOTAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterDeleteRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterInsertRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterUpdateRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_REPLICATION_LAG”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/SearchReplicationLagTimeMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“SWAP_USAGE_FREE”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SwapUsageFreeDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SWAP_USAGE_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/SwapUsageUsedDataMetricThresholdView”更改为“#/components/schemas/SwapUsageUsedDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SYSTEM_MEMORY_AVAILABLE”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/SystemMemoryAvailableDataMetricThresholdView”更改为“#/components/schemas/SystemMemoryAvailableDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SYSTEM_MEMORY_PERCENT_USED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView”更改为“#/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SYSTEM_MEMORY_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/SystemMemoryUsedDataMetricThresholdView”更改为“#/components/schemas/SystemMemoryUsedDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SYSTEM_NETWORK_IN”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SystemNetworkInDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SYSTEM_NETWORK_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SystemNetworkOutDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“TICKETS_AVAILABLE_READS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/TicketsAvailableReadsRawMetricThresholdView”更改为“#/components/schemas/TicketsAvailableReadsRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“TICKETS_AVAILABLE_WRITES”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/TicketsAvailableWritesRawMetricThresholdView”
  • 添加 '#/components/schemas/AssertRegularRawMetricThresholdView, #/components/schemas/AssertWarningRawMetricThresholdView, #/components/schemas/AssertMsgRawMetricThresholdView, #/components/schemas/AssertUserRawMetricThresholdView, #/components/schemas/OpCounterCmdRawMetricThresholdView, #/components/schemas/OpCounterCmdRawMetricThresholdView, #/components/schemas/OpCounterRawMetricThresholdView, #/components/schemas/OpCounterCmdRawMetricThresholdView, #/components/schemas/OpCounterUpdateRawMetricThresholdView, #/components/schemas/OpCounterDeleteRawMetricThresholdView, #/components/schemas/OpCounterTtlDeletedRawMetricThresholdView, #/components/schemas/OpCounterInsertRawMetricThresholdView, #/components/schemas/OpCounterGetMoreRawMetricThresholdView, #/components/schemas/OpCounterGetMoreRawMetricReplas/OpCounterMetricReplas/schemeView components/schemas/OpCounterReplUpdateRawMetricThresholdView, #/components/schemas/OpCounterReplDeleteRawMetricThresholdView, #/components/schemas/OpCounterReplInsertRawMetricThresholdView, #/components/schemas/FtsMemoryResidentDataMetricThresholdView, #/components/schemas/FtsMemoryV irtualDataMetricThresholdView, #/components/schemas/FtsMemoryMappedDataMetricThresholdView, #/components/schemas/FtsProcessCpuUserRawMetricThresholdView, #/components/schemas/FtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MemoryResidentDataMetricThresholdView, #/components/schemas/MemoryVirtualDataMetricThresholdView, #/components/schemas/MemoryMappedDataMetricThresholdView, #/components/schemas/ComputedMemoryDataMetricThresholdView, #/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdView, #/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdViewHitsMetric components/schemas/IndexCountersBtreeMissesRawMetricThresholdView, #/components/schemas/IndexCountersBtreeMissRatioRawMetricThresholdView, #/components/schemas/GlobalLockPercentageRawMetricTh resholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/ConnectionsRawMetricThresholdView, #/components/schemas/ConnectionsMaxRawMetricThresholdView, #/components/schemas/ConnectionsPercentRawMetricThresholdView, #/components/schemas/GlobalAccessesNotInMemoryRawMetricThresholdView, #/components/schemas/GlobalPageFaultRawMetricThrownMetricThrownView #/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView, #/components/schemas/CursorsTotalOpenRawMetricThresholdView, #/components/schemas/CursorsTotalTimedOutRawMetricThresholdView, #/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView, #/ components/schemas/NetworkBytesInDataMetricThresholdView, #/components/schemas/NetworkBytesOutDataMetricThresholdView, #/components/schemas/NetworkNumRequestsRawMetricThresholdView, #/components/ schemas/OplogMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView, #/components/schemas/OplogSlaveLagMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView, #/components/schemas/OplogRateGbPerHourDataMetricThresholdView, #/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView, #/components/schemas/ DbStorageTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView, #/components/schemas/DbIndexSizeTotalDataMetricThresholdView, #/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView, #/components/schemas/JournalingMbDataMetricThresholdView, #/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView, #/components/schemas/TicketsAvailableReadsRawMetricThresholdView, #/components/schemas/TicketsAvailableWritesRawMetricThresholdView, #/components/schemas/Cache UsageDirtyDataMetricThresholdView, #/components/schemas/CacheUsageUsedDataMetricThresholdView, #/components/schemas/CacheBytesReadIntoDataMetricThresholdView, #/components/schemas/CacheBytesWrittenFromDataMetricThresholdView, #/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView, #/ components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsJournalRawMetricThre sholdView, #/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/FtsDiskUtilizationDataMetricThresholdView, #/components/schemas/MuninCpuUserRawMetricThresholdView, #/components/schemas/MuninCpuNiceRawMetricThresholdView, #/ components/schemas/MuninCpuSystemRawMetricThresholdView, #/components/schemas/MuninCpuIowaitRawMetricThresholdView, #/components/schem as/MuninCpuIrqRawMetricThresholdView, #/components/schemas/MuninCpuSoftirqRawMetricThresholdView, #/components/schemas/MuninCpuStealRawMetricThresholdView, #/components/schemas/DocumentReturnedRawMetricThresholdView, #/components/schemas/DocumentInsertedRawMetricThresholdView, #/components/schemas/MuninCpuStealRawMetricThresholdView, #/components/schemas/DocumentInsertedRawMetricThresholdView, #/components/schemas/componentsRawMetricThresholdView DocumentDeletedRawMetricThresholdView, #/components/schemas/OperationsScanAndOrderRawMetricThresholdView, #/components/schemas/QueryExecutorScannedRawMetricThresholdView, #/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView, #/components/schemas/OperationThrottlingRejectedOperationsRawMetricThresholdView, #/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView, #/components/schemas/OperationsQueriesKilledRawMetricThresholdView, #/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView, #/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView, #/components/sch emas/AvgReadExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgWriteExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgCommandExecutionTimeTimeMetricThresholdView, #/components/schemas/LogicalSizeDataMetricThresholdView, #/components/schemas/RestartsInLastHourRawMetricThresholdView, #/components/schemas/SystemMemtricThoryschem SystemMemoryAvailableDataMetricThresholdView, #/components/schemas/SwapUsageUsedDataMetricThresholdView, #/components/schemas/SwapUsageFreeDataMetricThresholdView, #/components/schemas/SystemNetworkInDataMetricThresholdView, #/components/schemas/SystemNetworkOutDataMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/MaxDiskPartitionSpaceUsedDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionSpaceUsedIndexRawMetricThresholdView, #/components/schemas/MaxDiskPart itionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/ components/schemas/MaxDiskParti tionQueueDepthDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView, #/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView, #/components/schemas/MaxSwapUsageUsedDataMetricThresholdView, #/components/schemas/MaxSwapUsageFreeDataMetricThresholdView, #/components/schemas/MaxSystemNetworkInDataMetricThresholdView, #/components/schemas/MaxSystemNetworkOutDataMetricThresholdView, #/components/schemas/SearchIndexSizeDataMetricThresholdView, #/components/schemas/SearchNumberOfFieldsInIndexRawMetricThresholdView, #/components/schemas/SearchRealThresholdView, #/components/schemas/SearchRealThresholdView, components/schemas/NumberMetricThresholdView, #/components/schemas/SearchOpCounterInsertRawMetricThresholdView, #/components/schemas/SearchOpCou nterDeleteRawMetricThresholdView, #/components/schemas/SearchOpCounterUpdateRawMetricThresholdView, #/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView, #/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView, #/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView' 到该响应的 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 响应属性'oneOf' 列表
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“ASSERT_MSG”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/AssertMsgRawMetricThresholdView”更改为“#/components/schemas/AssertMsgRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“ASSERT_REGULAR”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/AssertRegularRawMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“ASSERT_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/AssertUserRawMetricThresholdView”更改为“#/components/schemas/AssertUserRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“ASSERT_WARNING”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/AssertWarningRawMetricThresholdView”更改为“#/components/schemas/AssertWarningRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“AVG_COMMAND_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/AvgCommandExecutionTimeTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“AVG_READ_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/AvgReadExecutionTimeTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“AVG_WRITE_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/AvgWriteExecutionTimeTimeMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“CACHE_BYTES_READ_INTO”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/CacheBytesReadIntoDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CACHE_BYTES_WRITTEN_FROM”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/CacheBytesWrittenFromDataMetricThresholdView”更改为“#/components/schemas/CacheBytesWrittenFromDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CACHE_USAGE_DIRTY”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/CacheUsageDirtyDataMetricThresholdView”更改为“#/components/schemas/CacheUsageDirtyDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CACHE_USAGE_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/CacheUsageUsedDataMetricThresholdView”更改为“#/components/schemas/CacheUsageUsedDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“COMPUTED_MEMORY”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/ComputedMemoryDataMetricThresholdView”更改
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CONNECTIONS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ConnectionsRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CONNECTIONS_MAX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ConnectionsMaxRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CONNECTIONS_PERCENT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/ConnectionsPercentRawMetricThresholdView”更改为“#/components/schemas/ConnectionsPercentRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CURSORS_TOTAL_CLIENT_CURSORS_SIZE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CURSORS_TOTAL_OPEN”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/CursorsTotalOpenRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CURSORS_TOTAL_TIMED_OUT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/CursorsTotalTimedOutRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DB_DATA_SIZE_TOTAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DbDataSizeTotalDataMetricThresholdView”更改为“#/components/schemas/DbDataSizeTotalDataMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“DB_DATA_SIZE_TOTAL_WO_SYSTEM”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DB_INDEX_SIZE_TOTAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DbIndexSizeTotalDataMetricThresholdView”更改为“#/components/schemas/DbIndexSizeTotalDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DB_STORAGE_TOTAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DbStorageTotalDataMetricThresholdView”更改为“#/components/schemas/DbStorageTotalDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_QUEUE_DEPTH_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_QUEUE_DEPTH_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_QUEUE_DEPTH_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_READ_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_READ_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_READ_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_READ_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_READ_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_READ_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_SPACE_USED_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_SPACE_USED_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_SPACE_USED_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionSpaceUsedJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_WRITE_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_WRITE_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_WRITE_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteIopsJournalRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_WRITE_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_WRITE_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_WRITE_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DOCUMENT_DELETED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DocumentDeletedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DOCUMENT_INSERTED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DocumentInsertedRawMetricThresholdView”更改为“#/components/schemas/DocumentInsertedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DOCUMENT_RETURNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DocumentReturnedRawMetricThresholdView”更改为“#/components/schemas/DocumentReturnedRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DOCUMENT_UPDATED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DocumentUpdatedRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“EXTRA_INFO_PAGE_FAULTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“FTS_DISK_UTILIZATION”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FtsDiskUtilizationDataMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“FTS_JVM_CURRENT_MEMORY”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“FTS_JVM_MAX_MEMORY”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView”更改为“#/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“FTS_MEMORY_MAPPED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/FtsMemoryMappedDataMetricThresholdView”更改为“#/components/schemas/FtsMemoryMappedDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“FTS_MEMORY_RESIDENT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/FtsMemoryResidentDataMetricThresholdView”更改为“#/components/schemas/FtsMemoryResidentDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“FTS_MEMORY_VIRTUAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/FtsMemoryVirtualDataMetricThresholdView”更改为“#/components/schemas/FtsMemoryVirtualDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“FTS_PROCESS_CPU_KERNEL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FtsProcessCpuKernelRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“FTS_PROCESS_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FtsProcessCpuUserRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“GLOBAL_ACCESSES_NOT_IN_MEMORY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalAccessesNotInMemoryRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“GLOBAL_LOCK_CURRENT_QUEUE_READERS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“GLOBAL_LOCK_CURRENT_QUEUE_TOTAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“GLOBAL_LOCK_CURRENT_QUEUE_WRITERS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“GLOBAL_LOCK_PERCENTAGE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockPercentageRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“GLOBAL_PAGE_FAULT_EXCEPTIONS_THROWN”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalPageFaultExceptionsThrownRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“INDEX_COUNTERS_BTREE_ACCESSES”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“INDEX_COUNTERS_BTREE_HITS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeHitsRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“INDEX_COUNTERS_BTREE_MISSES”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeMissesRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“INDEX_COUNTERS_BTREE_MISS_RATIO”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeMissRatioRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“JOURNALING_COMMITS_IN_WRITE_LOCK”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“JOURNALING_MB”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/JournalingMbDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“JOURNALING_WRITE_DATA_FILES_MB”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView”更改为“#/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“LOGICAL_SIZE”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/LogicalSizeDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_QUEUE_DEPTH_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionQueueDepthDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_QUEUE_DEPTH_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_QUEUE_DEPTH_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_READ_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_READ_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_READ_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_READ_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_READ_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_READ_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_SPACE_USED_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MaxDiskPartitionSpaceUsedDataRawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionSpaceUsedDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_SPACE_USED_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionSpaceUsedIndexRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_SPACE_USED_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionSpaceUsedJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_WRITE_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_WRITE_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_WRITE_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_WRITE_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_WRITE_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_WRITE_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_NORMALIZED_SYSTEM_CPU_STEAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_NORMALIZED_SYSTEM_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“MAX_SWAP_USAGE_FREE”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSwapUsageFreeDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_SWAP_USAGE_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/MaxSwapUsageUsedDataMetricThresholdView”更改为“#/components/schemas/MaxSwapUsageUsedDataMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“MAX_SYSTEM_MEMORY_AVAILABLE”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_SYSTEM_MEMORY_PERCENT_USED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_SYSTEM_MEMORY_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView”更改为“#/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_SYSTEM_NETWORK_IN”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSystemNetworkInDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_SYSTEM_NETWORK_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/MaxSystemNetworkOutDataMetricThresholdView”更改为“#/components/schemas/MaxSystemNetworkOutDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MEMORY_MAPPED”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MemoryMappedDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MEMORY_RESIDENT”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MemoryResidentDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MEMORY_VIRTUAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/MemoryVirtualDataMetricThresholdView”更改为“#/components/schemas/MemoryVirtualDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MUNIN_CPU_IOWAIT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuIowaitRawMetricThresholdView”更改为“#/components/schemas/MuninCpuIowawaitRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MUNIN_CPU_IRQ”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuIrqRawMetricThresholdView”更改为“#/components/schemas/MuninCpuIrqRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MUNIN_CPU_NICE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuNiceRawMetricThresholdView”更改为“#/components/schemas/MuninCpuNiceRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MUNIN_CPU_SOFTIRQ”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MuninCpuSoftirqRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MUNIN_CPU_STEAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuStealRawMetricThresholdView”更改为“#/components/schemas/MuninCpuStealRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MUNIN_CPU_SYSTEM”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuSystemRawMetricThresholdView”更改为“#/components/schemas/MuninCpuSystemRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MUNIN_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuUserRawMetricThresholdView”更改为“#/components/schemas/MuninCpuUserRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“NETWORK_BYTES_IN”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/NetworkBytesInDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“NETWORK_BYTES_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/NetworkBytesOutDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“NETWORK_NUM_REQUESTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NetworkNumRequestsRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“NORMALIZED_FTS_PROCESS_CPU_KERNEL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“NORMALIZED_FTS_PROCESS_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“NORMALIZED_SYSTEM_CPU_STEAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView”更改为“#/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“NORMALIZED_SYSTEM_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView”更改为“#/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterCmdRawMetricThresholdView”更改为“#/components/schemas/OpCounterCmdRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterDeleteRawMetricThresholdView”更改为“#/components/schemas/OpCounterDeleteRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterGetMoreRawMetricThresholdView”更改为“#/components/schemas/OpCounterGetMoreRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterInsertRawMetricThresholdView”更改为“#/components/schemas/OpCounterInsertRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_QUERY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterQueryRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_REPL_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterReplCmdRawMetricThresholdView”更改为“#/components/schemas/OpCounterReplCmdRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_REPL_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterReplDeleteRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_REPL_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterReplInsertRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_REPL_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterReplUpdateRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_TTL_DELETED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterTtlDeletedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterUpdateRawMetricThresholdView”更改为“#/components/schemas/OpCounterUpdateRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPERATIONS_QUERIES_KILLED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OperationsQueriesKilledRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPERATIONS_SCAN_AND_ORDER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OperationsScanAndOrderRawMetricThresholdView”
  • 已针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPERATION_THROTTLING_REJECTED_OPERATIONS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OperationThrotdlingRejectedOperationsRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPLOG_MASTER_LAG_TIME_DIFF”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPLOG_MASTER_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogMasterTimeTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPLOG_MASTER_TIME_ESTIMATED_TTL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“OPLOG_RATE_GB_PER_HOUR”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/OplogRateGbPerHourDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPLOG_SLAVE_LAG_MASTER_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogSlaveLagMasterTimeTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“QUERY_EXECUTOR_SCANNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/QueryExecutorScannedRawMetricThresholdView”更改为“#/components/schemas/QueryExecutorScannedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“QUERY_EXECUTOR_SCANNED_OBJECTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“QUERY_SPILL_TO_DISK_DURING_SORT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“QUERY_TARGETING_SCANNED_OBJECTS_PER_RETURNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“QUERY_TARGETING_SCANNED_PER_RETURNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“RESTARTS_IN_LAST_HOUR”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/RestartsInLastHourRawMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“SEARCH_INDEX_SIZE”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SearchIndexSizeDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_NUMBER_OF_FIELDS_IN_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfFieldsInIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_NUMBER_OF_QUERIES_ERROR”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_NUMBER_OF_QUERIES_SUCCESS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_NUMBER_OF_QUERIES_TOTAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterDeleteRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterInsertRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterUpdateRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_REPLICATION_LAG”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/SearchReplicationLagTimeMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“SWAP_USAGE_FREE”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SwapUsageFreeDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SWAP_USAGE_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/SwapUsageUsedDataMetricThresholdView”更改为“#/components/schemas/SwapUsageUsedDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SYSTEM_MEMORY_AVAILABLE”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/SystemMemoryAvailableDataMetricThresholdView”更改为“#/components/schemas/SystemMemoryAvailableDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SYSTEM_MEMORY_PERCENT_USED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView”更改为“#/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SYSTEM_MEMORY_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/SystemMemoryUsedDataMetricThresholdView”更改为“#/components/schemas/SystemMemoryUsedDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SYSTEM_NETWORK_IN”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SystemNetworkInDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SYSTEM_NETWORK_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SystemNetworkOutDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“TICKETS_AVAILABLE_READS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/TicketsAvailableReadsRawMetricThresholdView”更改为“#/components/schemas/TicketsAvailableReadsRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“TICKETS_AVAILABLE_WRITES”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/TicketsAvailableWritesRawMetricThresholdView”
  • 添加 '#/components/schemas/AssertRegularRawMetricThresholdView, #/components/schemas/AssertWarningRawMetricThresholdView, #/components/schemas/AssertMsgRawMetricThresholdView, #/components/schemas/AssertUserRawMetricThresholdView, #/components/schemas/OpCounterCmdRawMetricThresholdView, #/components/schemas/OpCounterCmdRawMetricThresholdView, #/components/schemas/OpCounterRawMetricThresholdView, #/components/schemas/OpCounterCmdRawMetricThresholdView, #/components/schemas/OpCounterUpdateRawMetricThresholdView, #/components/schemas/OpCounterDeleteRawMetricThresholdView, #/components/schemas/OpCounterTtlDeletedRawMetricThresholdView, #/components/schemas/OpCounterInsertRawMetricThresholdView, #/components/schemas/OpCounterGetMoreRawMetricThresholdView, #/components/schemas/OpCounterGetMoreRawMetricReplas/OpCounterMetricReplas/schemeView components/schemas/OpCounterReplUpdateRawMetricThresholdView, #/components/schemas/OpCounterReplDeleteRawMetricThresholdView, #/components/schemas/OpCounterReplInsertRawMetricThresholdView, #/components/schemas/FtsMemoryResidentDataMetricThresholdView, #/components/schemas/FtsMemoryV irtualDataMetricThresholdView, #/components/schemas/FtsMemoryMappedDataMetricThresholdView, #/components/schemas/FtsProcessCpuUserRawMetricThresholdView, #/components/schemas/FtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MemoryResidentDataMetricThresholdView, #/components/schemas/MemoryVirtualDataMetricThresholdView, #/components/schemas/MemoryMappedDataMetricThresholdView, #/components/schemas/ComputedMemoryDataMetricThresholdView, #/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdView, #/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdViewHitsMetric components/schemas/IndexCountersBtreeMissesRawMetricThresholdView, #/components/schemas/IndexCountersBtreeMissRatioRawMetricThresholdView, #/components/schemas/GlobalLockPercentageRawMetricTh resholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/ConnectionsRawMetricThresholdView, #/components/schemas/ConnectionsMaxRawMetricThresholdView, #/components/schemas/ConnectionsPercentRawMetricThresholdView, #/components/schemas/GlobalAccessesNotInMemoryRawMetricThresholdView, #/components/schemas/GlobalPageFaultRawMetricThrownMetricThrownView #/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView, #/components/schemas/CursorsTotalOpenRawMetricThresholdView, #/components/schemas/CursorsTotalTimedOutRawMetricThresholdView, #/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView, #/ components/schemas/NetworkBytesInDataMetricThresholdView, #/components/schemas/NetworkBytesOutDataMetricThresholdView, #/components/schemas/NetworkNumRequestsRawMetricThresholdView, #/components/ schemas/OplogMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView, #/components/schemas/OplogSlaveLagMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView, #/components/schemas/OplogRateGbPerHourDataMetricThresholdView, #/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView, #/components/schemas/ DbStorageTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView, #/components/schemas/DbIndexSizeTotalDataMetricThresholdView, #/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView, #/components/schemas/JournalingMbDataMetricThresholdView, #/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView, #/components/schemas/TicketsAvailableReadsRawMetricThresholdView, #/components/schemas/TicketsAvailableWritesRawMetricThresholdView, #/components/schemas/Cache UsageDirtyDataMetricThresholdView, #/components/schemas/CacheUsageUsedDataMetricThresholdView, #/components/schemas/CacheBytesReadIntoDataMetricThresholdView, #/components/schemas/CacheBytesWrittenFromDataMetricThresholdView, #/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView, #/ components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsJournalRawMetricThre sholdView, #/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/FtsDiskUtilizationDataMetricThresholdView, #/components/schemas/MuninCpuUserRawMetricThresholdView, #/components/schemas/MuninCpuNiceRawMetricThresholdView, #/ components/schemas/MuninCpuSystemRawMetricThresholdView, #/components/schemas/MuninCpuIowaitRawMetricThresholdView, #/components/schem as/MuninCpuIrqRawMetricThresholdView, #/components/schemas/MuninCpuSoftirqRawMetricThresholdView, #/components/schemas/MuninCpuStealRawMetricThresholdView, #/components/schemas/DocumentReturnedRawMetricThresholdView, #/components/schemas/DocumentInsertedRawMetricThresholdView, #/components/schemas/MuninCpuStealRawMetricThresholdView, #/components/schemas/DocumentInsertedRawMetricThresholdView, #/components/schemas/componentsRawMetricThresholdView DocumentDeletedRawMetricThresholdView, #/components/schemas/OperationsScanAndOrderRawMetricThresholdView, #/components/schemas/QueryExecutorScannedRawMetricThresholdView, #/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView, #/components/schemas/OperationThrottlingRejectedOperationsRawMetricThresholdView, #/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView, #/components/schemas/OperationsQueriesKilledRawMetricThresholdView, #/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView, #/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView, #/components/sch emas/AvgReadExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgWriteExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgCommandExecutionTimeTimeMetricThresholdView, #/components/schemas/LogicalSizeDataMetricThresholdView, #/components/schemas/RestartsInLastHourRawMetricThresholdView, #/components/schemas/SystemMemtricThoryschem SystemMemoryAvailableDataMetricThresholdView, #/components/schemas/SwapUsageUsedDataMetricThresholdView, #/components/schemas/SwapUsageFreeDataMetricThresholdView, #/components/schemas/SystemNetworkInDataMetricThresholdView, #/components/schemas/SystemNetworkOutDataMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/MaxDiskPartitionSpaceUsedDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionSpaceUsedIndexRawMetricThresholdView, #/components/schemas/MaxDiskPart itionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/ components/schemas/MaxDiskParti tionQueueDepthDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView, #/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView, #/components/schemas/MaxSwapUsageUsedDataMetricThresholdView, #/components/schemas/MaxSwapUsageFreeDataMetricThresholdView, #/components/schemas/MaxSystemNetworkInDataMetricThresholdView, #/components/schemas/MaxSystemNetworkOutDataMetricThresholdView, #/components/schemas/SearchIndexSizeDataMetricThresholdView, #/components/schemas/SearchNumberOfFieldsInIndexRawMetricThresholdView, #/components/schemas/SearchRealThresholdView, #/components/schemas/SearchRealThresholdView, components/schemas/NumberMetricThresholdView, #/components/schemas/SearchOpCounterInsertRawMetricThresholdView, #/components/schemas/SearchOpCou nterDeleteRawMetricThresholdView, #/components/schemas/SearchOpCounterUpdateRawMetricThresholdView, #/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView, #/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView, #/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView' 到该响应的 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 响应属性'oneOf' 列表
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“ASSERT_MSG”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/AssertMsgRawMetricThresholdView”更改为“#/components/schemas/AssertMsgRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“ASSERT_REGULAR”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/AssertRegularRawMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“ASSERT_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/AssertUserRawMetricThresholdView”更改为“#/components/schemas/AssertUserRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“ASSERT_WARNING”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/AssertWarningRawMetricThresholdView”更改为“#/components/schemas/AssertWarningRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“AVG_COMMAND_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/AvgCommandExecutionTimeTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“AVG_READ_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/AvgReadExecutionTimeTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“AVG_WRITE_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/AvgWriteExecutionTimeTimeMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“CACHE_BYTES_READ_INTO”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/CacheBytesReadIntoDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CACHE_BYTES_WRITTEN_FROM”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/CacheBytesWrittenFromDataMetricThresholdView”更改为“#/components/schemas/CacheBytesWrittenFromDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CACHE_USAGE_DIRTY”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/CacheUsageDirtyDataMetricThresholdView”更改为“#/components/schemas/CacheUsageDirtyDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CACHE_USAGE_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/CacheUsageUsedDataMetricThresholdView”更改为“#/components/schemas/CacheUsageUsedDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“COMPUTED_MEMORY”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/ComputedMemoryDataMetricThresholdView”更改
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CONNECTIONS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ConnectionsRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CONNECTIONS_MAX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ConnectionsMaxRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CONNECTIONS_PERCENT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/ConnectionsPercentRawMetricThresholdView”更改为“#/components/schemas/ConnectionsPercentRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CURSORS_TOTAL_CLIENT_CURSORS_SIZE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CURSORS_TOTAL_OPEN”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/CursorsTotalOpenRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CURSORS_TOTAL_TIMED_OUT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/CursorsTotalTimedOutRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DB_DATA_SIZE_TOTAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DbDataSizeTotalDataMetricThresholdView”更改为“#/components/schemas/DbDataSizeTotalDataMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“DB_DATA_SIZE_TOTAL_WO_SYSTEM”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DB_INDEX_SIZE_TOTAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DbIndexSizeTotalDataMetricThresholdView”更改为“#/components/schemas/DbIndexSizeTotalDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DB_STORAGE_TOTAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DbStorageTotalDataMetricThresholdView”更改为“#/components/schemas/DbStorageTotalDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_QUEUE_DEPTH_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_QUEUE_DEPTH_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_QUEUE_DEPTH_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_READ_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_READ_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_READ_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_READ_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_READ_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_READ_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_SPACE_USED_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_SPACE_USED_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_SPACE_USED_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionSpaceUsedJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_WRITE_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_WRITE_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_WRITE_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteIopsJournalRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_WRITE_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_WRITE_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_WRITE_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DOCUMENT_DELETED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DocumentDeletedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DOCUMENT_INSERTED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DocumentInsertedRawMetricThresholdView”更改为“#/components/schemas/DocumentInsertedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DOCUMENT_RETURNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DocumentReturnedRawMetricThresholdView”更改为“#/components/schemas/DocumentReturnedRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DOCUMENT_UPDATED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DocumentUpdatedRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“EXTRA_INFO_PAGE_FAULTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“FTS_DISK_UTILIZATION”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FtsDiskUtilizationDataMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“FTS_JVM_CURRENT_MEMORY”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“FTS_JVM_MAX_MEMORY”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView”更改为“#/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“FTS_MEMORY_MAPPED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/FtsMemoryMappedDataMetricThresholdView”更改为“#/components/schemas/FtsMemoryMappedDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“FTS_MEMORY_RESIDENT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/FtsMemoryResidentDataMetricThresholdView”更改为“#/components/schemas/FtsMemoryResidentDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“FTS_MEMORY_VIRTUAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/FtsMemoryVirtualDataMetricThresholdView”更改为“#/components/schemas/FtsMemoryVirtualDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“FTS_PROCESS_CPU_KERNEL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FtsProcessCpuKernelRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“FTS_PROCESS_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FtsProcessCpuUserRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“GLOBAL_ACCESSES_NOT_IN_MEMORY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalAccessesNotInMemoryRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“GLOBAL_LOCK_CURRENT_QUEUE_READERS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“GLOBAL_LOCK_CURRENT_QUEUE_TOTAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“GLOBAL_LOCK_CURRENT_QUEUE_WRITERS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“GLOBAL_LOCK_PERCENTAGE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockPercentageRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“GLOBAL_PAGE_FAULT_EXCEPTIONS_THROWN”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalPageFaultExceptionsThrownRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“INDEX_COUNTERS_BTREE_ACCESSES”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“INDEX_COUNTERS_BTREE_HITS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeHitsRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“INDEX_COUNTERS_BTREE_MISSES”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeMissesRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“INDEX_COUNTERS_BTREE_MISS_RATIO”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeMissRatioRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“JOURNALING_COMMITS_IN_WRITE_LOCK”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“JOURNALING_MB”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/JournalingMbDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“JOURNALING_WRITE_DATA_FILES_MB”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView”更改为“#/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“LOGICAL_SIZE”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/LogicalSizeDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_QUEUE_DEPTH_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionQueueDepthDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_QUEUE_DEPTH_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_QUEUE_DEPTH_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_READ_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_READ_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_READ_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_READ_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_READ_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_READ_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_SPACE_USED_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MaxDiskPartitionSpaceUsedDataRawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionSpaceUsedDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_SPACE_USED_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionSpaceUsedIndexRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_SPACE_USED_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionSpaceUsedJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_WRITE_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_WRITE_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_WRITE_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_WRITE_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_WRITE_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_WRITE_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_NORMALIZED_SYSTEM_CPU_STEAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_NORMALIZED_SYSTEM_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“MAX_SWAP_USAGE_FREE”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSwapUsageFreeDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_SWAP_USAGE_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/MaxSwapUsageUsedDataMetricThresholdView”更改为“#/components/schemas/MaxSwapUsageUsedDataMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“MAX_SYSTEM_MEMORY_AVAILABLE”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_SYSTEM_MEMORY_PERCENT_USED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_SYSTEM_MEMORY_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView”更改为“#/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_SYSTEM_NETWORK_IN”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSystemNetworkInDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_SYSTEM_NETWORK_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/MaxSystemNetworkOutDataMetricThresholdView”更改为“#/components/schemas/MaxSystemNetworkOutDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MEMORY_MAPPED”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MemoryMappedDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MEMORY_RESIDENT”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MemoryResidentDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MEMORY_VIRTUAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/MemoryVirtualDataMetricThresholdView”更改为“#/components/schemas/MemoryVirtualDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MUNIN_CPU_IOWAIT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuIowaitRawMetricThresholdView”更改为“#/components/schemas/MuninCpuIowawaitRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MUNIN_CPU_IRQ”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuIrqRawMetricThresholdView”更改为“#/components/schemas/MuninCpuIrqRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MUNIN_CPU_NICE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuNiceRawMetricThresholdView”更改为“#/components/schemas/MuninCpuNiceRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MUNIN_CPU_SOFTIRQ”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MuninCpuSoftirqRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MUNIN_CPU_STEAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuStealRawMetricThresholdView”更改为“#/components/schemas/MuninCpuStealRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MUNIN_CPU_SYSTEM”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuSystemRawMetricThresholdView”更改为“#/components/schemas/MuninCpuSystemRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MUNIN_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuUserRawMetricThresholdView”更改为“#/components/schemas/MuninCpuUserRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“NETWORK_BYTES_IN”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/NetworkBytesInDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“NETWORK_BYTES_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/NetworkBytesOutDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“NETWORK_NUM_REQUESTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NetworkNumRequestsRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“NORMALIZED_FTS_PROCESS_CPU_KERNEL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“NORMALIZED_FTS_PROCESS_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“NORMALIZED_SYSTEM_CPU_STEAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView”更改为“#/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“NORMALIZED_SYSTEM_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView”更改为“#/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterCmdRawMetricThresholdView”更改为“#/components/schemas/OpCounterCmdRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterDeleteRawMetricThresholdView”更改为“#/components/schemas/OpCounterDeleteRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterGetMoreRawMetricThresholdView”更改为“#/components/schemas/OpCounterGetMoreRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterInsertRawMetricThresholdView”更改为“#/components/schemas/OpCounterInsertRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_QUERY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterQueryRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_REPL_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterReplCmdRawMetricThresholdView”更改为“#/components/schemas/OpCounterReplCmdRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_REPL_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterReplDeleteRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_REPL_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterReplInsertRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_REPL_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterReplUpdateRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_TTL_DELETED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterTtlDeletedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterUpdateRawMetricThresholdView”更改为“#/components/schemas/OpCounterUpdateRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPERATIONS_QUERIES_KILLED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OperationsQueriesKilledRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPERATIONS_SCAN_AND_ORDER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OperationsScanAndOrderRawMetricThresholdView”
  • 已针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPERATION_THROTTLING_REJECTED_OPERATIONS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OperationThrotdlingRejectedOperationsRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPLOG_MASTER_LAG_TIME_DIFF”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPLOG_MASTER_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogMasterTimeTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPLOG_MASTER_TIME_ESTIMATED_TTL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“OPLOG_RATE_GB_PER_HOUR”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/OplogRateGbPerHourDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPLOG_SLAVE_LAG_MASTER_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogSlaveLagMasterTimeTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“QUERY_EXECUTOR_SCANNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/QueryExecutorScannedRawMetricThresholdView”更改为“#/components/schemas/QueryExecutorScannedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“QUERY_EXECUTOR_SCANNED_OBJECTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“QUERY_SPILL_TO_DISK_DURING_SORT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“QUERY_TARGETING_SCANNED_OBJECTS_PER_RETURNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“QUERY_TARGETING_SCANNED_PER_RETURNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“RESTARTS_IN_LAST_HOUR”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/RestartsInLastHourRawMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“SEARCH_INDEX_SIZE”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SearchIndexSizeDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_NUMBER_OF_FIELDS_IN_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfFieldsInIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_NUMBER_OF_QUERIES_ERROR”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_NUMBER_OF_QUERIES_SUCCESS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_NUMBER_OF_QUERIES_TOTAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterDeleteRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterInsertRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterUpdateRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_REPLICATION_LAG”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/SearchReplicationLagTimeMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“SWAP_USAGE_FREE”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SwapUsageFreeDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SWAP_USAGE_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/SwapUsageUsedDataMetricThresholdView”更改为“#/components/schemas/SwapUsageUsedDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SYSTEM_MEMORY_AVAILABLE”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/SystemMemoryAvailableDataMetricThresholdView”更改为“#/components/schemas/SystemMemoryAvailableDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SYSTEM_MEMORY_PERCENT_USED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView”更改为“#/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SYSTEM_MEMORY_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/SystemMemoryUsedDataMetricThresholdView”更改为“#/components/schemas/SystemMemoryUsedDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SYSTEM_NETWORK_IN”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SystemNetworkInDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SYSTEM_NETWORK_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SystemNetworkOutDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“TICKETS_AVAILABLE_READS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/TicketsAvailableReadsRawMetricThresholdView”更改为“#/components/schemas/TicketsAvailableReadsRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“TICKETS_AVAILABLE_WRITES”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/TicketsAvailableWritesRawMetricThresholdView”
  • 添加 '#/components/schemas/AssertRegularRawMetricThresholdView, #/components/schemas/AssertWarningRawMetricThresholdView, #/components/schemas/AssertMsgRawMetricThresholdView, #/components/schemas/AssertUserRawMetricThresholdView, #/components/schemas/OpCounterCmdRawMetricThresholdView, #/components/schemas/OpCounterCmdRawMetricThresholdView, #/components/schemas/OpCounterRawMetricThresholdView, #/components/schemas/OpCounterCmdRawMetricThresholdView, #/components/schemas/OpCounterUpdateRawMetricThresholdView, #/components/schemas/OpCounterDeleteRawMetricThresholdView, #/components/schemas/OpCounterTtlDeletedRawMetricThresholdView, #/components/schemas/OpCounterInsertRawMetricThresholdView, #/components/schemas/OpCounterGetMoreRawMetricThresholdView, #/components/schemas/OpCounterGetMoreRawMetricReplas/OpCounterMetricReplas/schemeView components/schemas/OpCounterReplUpdateRawMetricThresholdView, #/components/schemas/OpCounterReplDeleteRawMetricThresholdView, #/components/schemas/OpCounterReplInsertRawMetricThresholdView, #/components/schemas/FtsMemoryResidentDataMetricThresholdView, #/components/schemas/FtsMemoryV irtualDataMetricThresholdView, #/components/schemas/FtsMemoryMappedDataMetricThresholdView, #/components/schemas/FtsProcessCpuUserRawMetricThresholdView, #/components/schemas/FtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MemoryResidentDataMetricThresholdView, #/components/schemas/MemoryVirtualDataMetricThresholdView, #/components/schemas/MemoryMappedDataMetricThresholdView, #/components/schemas/ComputedMemoryDataMetricThresholdView, #/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdView, #/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdViewHitsMetric components/schemas/IndexCountersBtreeMissesRawMetricThresholdView, #/components/schemas/IndexCountersBtreeMissRatioRawMetricThresholdView, #/components/schemas/GlobalLockPercentageRawMetricTh resholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/ConnectionsRawMetricThresholdView, #/components/schemas/ConnectionsMaxRawMetricThresholdView, #/components/schemas/ConnectionsPercentRawMetricThresholdView, #/components/schemas/GlobalAccessesNotInMemoryRawMetricThresholdView, #/components/schemas/GlobalPageFaultRawMetricThrownMetricThrownView #/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView, #/components/schemas/CursorsTotalOpenRawMetricThresholdView, #/components/schemas/CursorsTotalTimedOutRawMetricThresholdView, #/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView, #/ components/schemas/NetworkBytesInDataMetricThresholdView, #/components/schemas/NetworkBytesOutDataMetricThresholdView, #/components/schemas/NetworkNumRequestsRawMetricThresholdView, #/components/ schemas/OplogMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView, #/components/schemas/OplogSlaveLagMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView, #/components/schemas/OplogRateGbPerHourDataMetricThresholdView, #/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView, #/components/schemas/ DbStorageTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView, #/components/schemas/DbIndexSizeTotalDataMetricThresholdView, #/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView, #/components/schemas/JournalingMbDataMetricThresholdView, #/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView, #/components/schemas/TicketsAvailableReadsRawMetricThresholdView, #/components/schemas/TicketsAvailableWritesRawMetricThresholdView, #/components/schemas/Cache UsageDirtyDataMetricThresholdView, #/components/schemas/CacheUsageUsedDataMetricThresholdView, #/components/schemas/CacheBytesReadIntoDataMetricThresholdView, #/components/schemas/CacheBytesWrittenFromDataMetricThresholdView, #/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView, #/ components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsJournalRawMetricThre sholdView, #/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/FtsDiskUtilizationDataMetricThresholdView, #/components/schemas/MuninCpuUserRawMetricThresholdView, #/components/schemas/MuninCpuNiceRawMetricThresholdView, #/ components/schemas/MuninCpuSystemRawMetricThresholdView, #/components/schemas/MuninCpuIowaitRawMetricThresholdView, #/components/schem as/MuninCpuIrqRawMetricThresholdView, #/components/schemas/MuninCpuSoftirqRawMetricThresholdView, #/components/schemas/MuninCpuStealRawMetricThresholdView, #/components/schemas/DocumentReturnedRawMetricThresholdView, #/components/schemas/DocumentInsertedRawMetricThresholdView, #/components/schemas/MuninCpuStealRawMetricThresholdView, #/components/schemas/DocumentInsertedRawMetricThresholdView, #/components/schemas/componentsRawMetricThresholdView DocumentDeletedRawMetricThresholdView, #/components/schemas/OperationsScanAndOrderRawMetricThresholdView, #/components/schemas/QueryExecutorScannedRawMetricThresholdView, #/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView, #/components/schemas/OperationThrottlingRejectedOperationsRawMetricThresholdView, #/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView, #/components/schemas/OperationsQueriesKilledRawMetricThresholdView, #/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView, #/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView, #/components/sch emas/AvgReadExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgWriteExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgCommandExecutionTimeTimeMetricThresholdView, #/components/schemas/LogicalSizeDataMetricThresholdView, #/components/schemas/RestartsInLastHourRawMetricThresholdView, #/components/schemas/SystemMemtricThoryschem SystemMemoryAvailableDataMetricThresholdView, #/components/schemas/SwapUsageUsedDataMetricThresholdView, #/components/schemas/SwapUsageFreeDataMetricThresholdView, #/components/schemas/SystemNetworkInDataMetricThresholdView, #/components/schemas/SystemNetworkOutDataMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/MaxDiskPartitionSpaceUsedDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionSpaceUsedIndexRawMetricThresholdView, #/components/schemas/MaxDiskPart itionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/ components/schemas/MaxDiskParti tionQueueDepthDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView, #/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView, #/components/schemas/MaxSwapUsageUsedDataMetricThresholdView, #/components/schemas/MaxSwapUsageFreeDataMetricThresholdView, #/components/schemas/MaxSystemNetworkInDataMetricThresholdView, #/components/schemas/MaxSystemNetworkOutDataMetricThresholdView, #/components/schemas/SearchIndexSizeDataMetricThresholdView, #/components/schemas/SearchNumberOfFieldsInIndexRawMetricThresholdView, #/components/schemas/SearchRealThresholdView, #/components/schemas/SearchRealThresholdView, components/schemas/NumberMetricThresholdView, #/components/schemas/SearchOpCounterInsertRawMetricThresholdView, #/components/schemas/SearchOpCou nterDeleteRawMetricThresholdView, #/components/schemas/SearchOpCounterUpdateRawMetricThresholdView, #/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView, #/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView, #/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView' 到该响应的 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 响应属性'oneOf' 列表
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“ASSERT_MSG”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/AssertMsgRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“ASSERT_REGULAR”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/AssertRegularRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“ASSERT_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/AssertUserRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“ASSERT_WARNING”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/AssertWarningRawMetricThresholdView”更改为“#/components/schemas/AssertWarningRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“AVG_COMMAND_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/AvgCommandExecutionTimeTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“AVG_READ_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/AvgReadExecutionTimeTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“AVG_WRITE_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/AvgWriteExecutionTimeTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“CACHE_BYTES_READ_INTO”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/CacheBytesReadIntoDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“CACHE_BYTES_WRITTEN_FROM”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/CacheBytesWrittenFromDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“CACHE_USAGE_DIRTY”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/CacheUsageDirtyDataMetricThresholdView”更改为“#/components/schemas/CacheUsageDirtyDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“CACHE_USAGE_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/CacheUsageUsedDataMetricThresholdView”更改为“#/components/schemas/CacheUsageUsedDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“COMPUTED_MEMORY”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/ComputedMemoryDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“CONNECTIONS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ConnectionsRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“CONNECTIONS_MAX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ConnectionsMaxRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“CONNECTIONS_PERCENT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ConnectionsPercentRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“CURSORS_TOTAL_CLIENT_CURSORS_SIZE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“CURSORS_TOTAL_OPEN”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/CursorsTotalOpenRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“CURSORS_TOTAL_TIMED_OUT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/CursorsTotalTimedOutRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DB_DATA_SIZE_TOTAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DbDataSizeTotalDataMetricThresholdView”更改为“#/components/schemas/DbDataSizeTotalDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DB_DATA_SIZE_TOTAL_WO_SYSTEM”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DB_INDEX_SIZE_TOTAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DbIndexSizeTotalDataMetricThresholdView”更改为“#/components/schemas/DbIndexSizeTotalDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DB_STORAGE_TOTAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DbStorageTotalDataMetricThresholdView”更改为“#/components/schemas/DbStorageTotalDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_QUEUE_DEPTH_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_QUEUE_DEPTH_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_QUEUE_DEPTH_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_READ_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_READ_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_READ_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_READ_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_READ_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_READ_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_SPACE_USED_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_SPACE_USED_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_SPACE_USED_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionSpaceUsedJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_WRITE_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_WRITE_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_WRITE_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteIopsJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_WRITE_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_WRITE_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DISK_PARTITION_WRITE_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DOCUMENT_DELETED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DocumentDeletedRawMetricThresholdView”更改为“#/components/schemas/DocumentDeletedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DOCUMENT_INSERTED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DocumentInsertedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DOCUMENT_RETURNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DocumentReturnedRawMetricThresholdView”更改为“#/components/schemas/DocumentReturnedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“DOCUMENT_UPDATED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DocumentUpdatedRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“EXTRA_INFO_PAGE_FAULTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“FTS_DISK_UTILIZATION”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FtsDiskUtilizationDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“FTS_JVM_CURRENT_MEMORY”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“FTS_JVM_MAX_MEMORY”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView”更改为“#/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“FTS_MEMORY_MAPPED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FtsMemoryMappedDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“FTS_MEMORY_RESIDENT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/FtsMemoryResidentDataMetricThresholdView”更改为“#/components/schemas/FtsMemoryResidentDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“FTS_MEMORY_VIRTUAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/FtsMemoryVirtualDataMetricThresholdView”更改为“#/components/schemas/FtsMemoryVirtualDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“FTS_PROCESS_CPU_KERNEL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FtsProcessCpuKernelRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“FTS_PROCESS_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FtsProcessCpuUserRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“GLOBAL_ACCESSES_NOT_IN_MEMORY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalAccessesNotInMemoryRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“GLOBAL_LOCK_CURRENT_QUEUE_READERS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“GLOBAL_LOCK_CURRENT_QUEUE_TOTAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“GLOBAL_LOCK_CURRENT_QUEUE_WRITERS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“GLOBAL_LOCK_PERCENTAGE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockPercentageRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“GLOBAL_PAGE_FAULT_EXCEPTIONS_THROWN”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalPageFaultExceptionsThrownRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“INDEX_COUNTERS_BTREE_ACCESSES”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“INDEX_COUNTERS_BTREE_HITS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeHitsRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“INDEX_COUNTERS_BTREE_MISSES”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeMissesRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“INDEX_COUNTERS_BTREE_MISS_RATIO”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeMissRatioRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“JOURNALING_COMMITS_IN_WRITE_LOCK”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“JOURNALING_MB”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/JournalingMbDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“JOURNALING_WRITE_DATA_FILES_MB”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView”更改为“#/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性的鉴别器键“LOGICAL_SIZE”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/LogicalSizeDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_QUEUE_DEPTH_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionQueueDepthDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_QUEUE_DEPTH_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_QUEUE_DEPTH_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_READ_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_READ_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_READ_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_READ_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_READ_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_READ_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_SPACE_USED_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MaxDiskPartitionSpaceUsedDataRawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionSpaceUsedDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_SPACE_USED_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionSpaceUsedIndexRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_SPACE_USED_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionSpaceUsedJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_WRITE_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_WRITE_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_WRITE_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_WRITE_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_WRITE_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_DISK_PARTITION_WRITE_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_NORMALIZED_SYSTEM_CPU_STEAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_NORMALIZED_SYSTEM_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_SWAP_USAGE_FREE”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/MaxSwapUsageFreeDataMetricThresholdView”更改为“#/components/schemas/MaxSwapUsageFreeDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_SWAP_USAGE_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/MaxSwapUsageUsedDataMetricThresholdView”更改为“#/components/schemas/MaxSwapUsageUsedDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_SYSTEM_MEMORY_AVAILABLE”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_SYSTEM_MEMORY_PERCENT_USED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_SYSTEM_MEMORY_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView”更改为“#/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_SYSTEM_NETWORK_IN”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSystemNetworkInDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MAX_SYSTEM_NETWORK_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSystemNetworkOutDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MEMORY_MAPPED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/MemoryMappedDataMetricThresholdView”更改为“#/components/schemas/MemoryMappedDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MEMORY_RESIDENT”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MemoryResidentDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MEMORY_VIRTUAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/MemoryVirtualDataMetricThresholdView”更改为“#/components/schemas/MemoryVirtualDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MUNIN_CPU_IOWAIT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MuninCpuIowawaitRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MUNIN_CPU_IRQ”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MuninCpuIrqRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MUNIN_CPU_NICE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuNiceRawMetricThresholdView”更改为“#/components/schemas/MuninCpuNiceRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MUNIN_CPU_SOFTIRQ”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MuninCpuSoftirqRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MUNIN_CPU_STEAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuStealRawMetricThresholdView”更改为“#/components/schemas/MuninCpuStealRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MUNIN_CPU_SYSTEM”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuSystemRawMetricThresholdView”更改为“#/components/schemas/MuninCpuSystemRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“MUNIN_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuUserRawMetricThresholdView”更改为“#/components/schemas/MuninCpuUserRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“NETWORK_BYTES_IN”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/NetworkBytesInDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“NETWORK_BYTES_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/NetworkBytesOutDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“NETWORK_NUM_REQUESTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NetworkNumRequestsRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“NORMALIZED_FTS_PROCESS_CPU_KERNEL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“NORMALIZED_FTS_PROCESS_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“NORMALIZED_SYSTEM_CPU_STEAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“NORMALIZED_SYSTEM_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPCOUNTER_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterCmdRawMetricThresholdView”更改为“#/components/schemas/OpCounterCmdRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterDeleteRawMetricThresholdView”更改为“#/components/schemas/OpCounterDeleteRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterGetMoreRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterInsertRawMetricThresholdView”更改为“#/components/schemas/OpCounterInsertRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPCOUNTER_QUERY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterQueryRawMetricThresholdView”更改为“#/components/schemas/OpCounterQueryRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPCOUNTER_REPL_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterReplCmdRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPCOUNTER_REPL_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterReplDeleteRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPCOUNTER_REPL_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterReplInsertRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPCOUNTER_REPL_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterReplUpdateRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPCOUNTER_TTL_DELETED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterTtlDeletedRawMetricThresholdView”更改为“#/components/schemas/OpCounterTtlDeletedRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterUpdateRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPERATIONS_QUERIES_KILLED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OperationsQueriesKilledRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPERATIONS_SCAN_AND_ORDER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OperationsScanAndOrderRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPERATION_THROTTLING_REJECTED_OPERATIONS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OperationThrotdlingRejectedOperationsRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPLOG_MASTER_LAG_TIME_DIFF”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPLOG_MASTER_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogMasterTimeTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPLOG_MASTER_TIME_ESTIMATED_TTL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPLOG_RATE_GB_PER_HOUR”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/OplogRateGbPerHourDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“OPLOG_SLAVE_LAG_MASTER_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogSlaveLagMasterTimeTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“QUERY_EXECUTOR_SCANNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QueryExecutorScannedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“QUERY_EXECUTOR_SCANNED_OBJECTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“QUERY_SPILL_TO_DISK_DURING_SORT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“QUERY_TARGETING_SCANNED_OBJECTS_PER_RETURNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“QUERY_TARGETING_SCANNED_PER_RETURNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“RESTARTS_IN_LAST_HOUR”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/RestartsInLastHourRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SEARCH_INDEX_SIZE”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SearchIndexSizeDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SEARCH_NUMBER_OF_FIELDS_IN_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfFieldsInIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SEARCH_NUMBER_OF_QUERIES_ERROR”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SEARCH_NUMBER_OF_QUERIES_SUCCESS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SEARCH_NUMBER_OF_QUERIES_TOTAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SEARCH_OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterDeleteRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SEARCH_OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SEARCH_OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterInsertRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SEARCH_OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterUpdateRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SEARCH_REPLICATION_LAG”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/SearchReplicationLagTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SWAP_USAGE_FREE”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SwapUsageFreeDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SWAP_USAGE_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/SwapUsageUsedDataMetricThresholdView”更改为“#/components/schemas/SwapUsageUsedDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SYSTEM_MEMORY_AVAILABLE”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/SystemMemoryAvailableDataMetricThresholdView”更改为“#/components/schemas/SystemMemoryAvailableDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SYSTEM_MEMORY_PERCENT_USED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SYSTEM_MEMORY_USED”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SystemMemoryUsedDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SYSTEM_NETWORK_IN”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SystemNetworkInDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“SYSTEM_NETWORK_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/SystemNetworkOutDataMetricThresholdView”更改为“#/components/schemas/SystemNetworkOutDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“TICKETS_AVAILABLE_READS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/TicketsAvailableReadsRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性，鉴别器键“TICKETS_AVAILABLE_WRITES”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/TicketsAvailableWritesRawMetricThresholdView”
  • 添加 '#/components/schemas/AssertRegularRawMetricThresholdView, #/components/schemas/AssertWarningRawMetricThresholdView, #/components/schemas/AssertMsgRawMetricThresholdView, #/components/schemas/AssertUserRawMetricThresholdView, #/components/schemas/OpCounterCmdRawMetricThresholdView, #/components/schemas/OpCounterCmdRawMetricThresholdView, #/components/schemas/OpCounterRawMetricThresholdView, #/components/schemas/OpCounterCmdRawMetricThresholdView, #/components/schemas/OpCounterUpdateRawMetricThresholdView, #/components/schemas/OpCounterDeleteRawMetricThresholdView, #/components/schemas/OpCounterTtlDeletedRawMetricThresholdView, #/components/schemas/OpCounterInsertRawMetricThresholdView, #/components/schemas/OpCounterGetMoreRawMetricThresholdView, #/components/schemas/OpCounterGetMoreRawMetricReplas/OpCounterMetricReplas/schemeView components/schemas/OpCounterReplUpdateRawMetricThresholdView, #/components/schemas/OpCounterReplDeleteRawMetricThresholdView, #/components/schemas/OpCounterReplInsertRawMetricThresholdView, #/components/schemas/FtsMemoryResidentDataMetricThresholdView, #/components/schemas/FtsMemoryV irtualDataMetricThresholdView, #/components/schemas/FtsMemoryMappedDataMetricThresholdView, #/components/schemas/FtsProcessCpuUserRawMetricThresholdView, #/components/schemas/FtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MemoryResidentDataMetricThresholdView, #/components/schemas/MemoryVirtualDataMetricThresholdView, #/components/schemas/MemoryMappedDataMetricThresholdView, #/components/schemas/ComputedMemoryDataMetricThresholdView, #/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdView, #/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdViewHitsMetric components/schemas/IndexCountersBtreeMissesRawMetricThresholdView, #/components/schemas/IndexCountersBtreeMissRatioRawMetricThresholdView, #/components/schemas/GlobalLockPercentageRawMetricTh resholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/ConnectionsRawMetricThresholdView, #/components/schemas/ConnectionsMaxRawMetricThresholdView, #/components/schemas/ConnectionsPercentRawMetricThresholdView, #/components/schemas/GlobalAccessesNotInMemoryRawMetricThresholdView, #/components/schemas/GlobalPageFaultRawMetricThrownMetricThrownView #/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView, #/components/schemas/CursorsTotalOpenRawMetricThresholdView, #/components/schemas/CursorsTotalTimedOutRawMetricThresholdView, #/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView, #/ components/schemas/NetworkBytesInDataMetricThresholdView, #/components/schemas/NetworkBytesOutDataMetricThresholdView, #/components/schemas/NetworkNumRequestsRawMetricThresholdView, #/components/ schemas/OplogMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView, #/components/schemas/OplogSlaveLagMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView, #/components/schemas/OplogRateGbPerHourDataMetricThresholdView, #/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView, #/components/schemas/ DbStorageTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView, #/components/schemas/DbIndexSizeTotalDataMetricThresholdView, #/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView, #/components/schemas/JournalingMbDataMetricThresholdView, #/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView, #/components/schemas/TicketsAvailableReadsRawMetricThresholdView, #/components/schemas/TicketsAvailableWritesRawMetricThresholdView, #/components/schemas/Cache UsageDirtyDataMetricThresholdView, #/components/schemas/CacheUsageUsedDataMetricThresholdView, #/components/schemas/CacheBytesReadIntoDataMetricThresholdView, #/components/schemas/CacheBytesWrittenFromDataMetricThresholdView, #/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView, #/ components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsJournalRawMetricThre sholdView, #/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/FtsDiskUtilizationDataMetricThresholdView, #/components/schemas/MuninCpuUserRawMetricThresholdView, #/components/schemas/MuninCpuNiceRawMetricThresholdView, #/ components/schemas/MuninCpuSystemRawMetricThresholdView, #/components/schemas/MuninCpuIowaitRawMetricThresholdView, #/components/schem as/MuninCpuIrqRawMetricThresholdView, #/components/schemas/MuninCpuSoftirqRawMetricThresholdView, #/components/schemas/MuninCpuStealRawMetricThresholdView, #/components/schemas/DocumentReturnedRawMetricThresholdView, #/components/schemas/DocumentInsertedRawMetricThresholdView, #/components/schemas/MuninCpuStealRawMetricThresholdView, #/components/schemas/DocumentInsertedRawMetricThresholdView, #/components/schemas/componentsRawMetricThresholdView DocumentDeletedRawMetricThresholdView, #/components/schemas/OperationsScanAndOrderRawMetricThresholdView, #/components/schemas/QueryExecutorScannedRawMetricThresholdView, #/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView, #/components/schemas/OperationThrottlingRejectedOperationsRawMetricThresholdView, #/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView, #/components/schemas/OperationsQueriesKilledRawMetricThresholdView, #/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView, #/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView, #/components/sch emas/AvgReadExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgWriteExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgCommandExecutionTimeTimeMetricThresholdView, #/components/schemas/LogicalSizeDataMetricThresholdView, #/components/schemas/RestartsInLastHourRawMetricThresholdView, #/components/schemas/SystemMemtricThoryschem SystemMemoryAvailableDataMetricThresholdView, #/components/schemas/SwapUsageUsedDataMetricThresholdView, #/components/schemas/SwapUsageFreeDataMetricThresholdView, #/components/schemas/SystemNetworkInDataMetricThresholdView, #/components/schemas/SystemNetworkOutDataMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/MaxDiskPartitionSpaceUsedDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionSpaceUsedIndexRawMetricThresholdView, #/components/schemas/MaxDiskPart itionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/ components/schemas/MaxDiskParti tionQueueDepthDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView, #/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView, #/components/schemas/MaxSwapUsageUsedDataMetricThresholdView, #/components/schemas/MaxSwapUsageFreeDataMetricThresholdView, #/components/schemas/MaxSystemNetworkInDataMetricThresholdView, #/components/schemas/MaxSystemNetworkOutDataMetricThresholdView, #/components/schemas/SearchIndexSizeDataMetricThresholdView, #/components/schemas/SearchNumberOfFieldsInIndexRawMetricThresholdView, #/components/schemas/SearchRealThresholdView, #/components/schemas/SearchRealThresholdView, components/schemas/NumberMetricThresholdView, #/components/schemas/SearchOpCounterInsertRawMetricThresholdView, #/components/schemas/SearchOpCou nterDeleteRawMetricThresholdView, #/components/schemas/SearchOpCounterUpdateRawMetricThresholdView, #/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView, #/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView, #/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView”添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性“oneOf”列表
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“ASSERT_MSG”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/AssertMsgRawMetricThresholdView”更改为“#/components/schemas/AssertMsgRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“ASSERT_REGULAR”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/AssertRegularRawMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“ASSERT_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/AssertUserRawMetricThresholdView”更改为“#/components/schemas/AssertUserRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“ASSERT_WARNING”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/AssertWarningRawMetricThresholdView”更改为“#/components/schemas/AssertWarningRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“AVG_COMMAND_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/AvgCommandExecutionTimeTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“AVG_READ_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/AvgReadExecutionTimeTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“AVG_WRITE_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/AvgWriteExecutionTimeTimeMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“CACHE_BYTES_READ_INTO”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/CacheBytesReadIntoDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CACHE_BYTES_WRITTEN_FROM”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/CacheBytesWrittenFromDataMetricThresholdView”更改为“#/components/schemas/CacheBytesWrittenFromDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CACHE_USAGE_DIRTY”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/CacheUsageDirtyDataMetricThresholdView”更改为“#/components/schemas/CacheUsageDirtyDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CACHE_USAGE_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/CacheUsageUsedDataMetricThresholdView”更改为“#/components/schemas/CacheUsageUsedDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“COMPUTED_MEMORY”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/ComputedMemoryDataMetricThresholdView”更改
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CONNECTIONS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ConnectionsRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CONNECTIONS_MAX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ConnectionsMaxRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CONNECTIONS_PERCENT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/ConnectionsPercentRawMetricThresholdView”更改为“#/components/schemas/ConnectionsPercentRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CURSORS_TOTAL_CLIENT_CURSORS_SIZE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CURSORS_TOTAL_OPEN”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/CursorsTotalOpenRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“CURSORS_TOTAL_TIMED_OUT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/CursorsTotalTimedOutRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DB_DATA_SIZE_TOTAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DbDataSizeTotalDataMetricThresholdView”更改为“#/components/schemas/DbDataSizeTotalDataMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“DB_DATA_SIZE_TOTAL_WO_SYSTEM”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DB_INDEX_SIZE_TOTAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DbIndexSizeTotalDataMetricThresholdView”更改为“#/components/schemas/DbIndexSizeTotalDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DB_STORAGE_TOTAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DbStorageTotalDataMetricThresholdView”更改为“#/components/schemas/DbStorageTotalDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_QUEUE_DEPTH_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_QUEUE_DEPTH_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_QUEUE_DEPTH_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_READ_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_READ_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_READ_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_READ_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_READ_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_READ_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_SPACE_USED_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_SPACE_USED_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_SPACE_USED_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionSpaceUsedJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_WRITE_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_WRITE_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_WRITE_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteIopsJournalRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_WRITE_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_WRITE_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DISK_PARTITION_WRITE_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DOCUMENT_DELETED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DocumentDeletedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DOCUMENT_INSERTED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DocumentInsertedRawMetricThresholdView”更改为“#/components/schemas/DocumentInsertedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DOCUMENT_RETURNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/DocumentReturnedRawMetricThresholdView”更改为“#/components/schemas/DocumentReturnedRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“DOCUMENT_UPDATED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DocumentUpdatedRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“EXTRA_INFO_PAGE_FAULTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“FTS_DISK_UTILIZATION”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FtsDiskUtilizationDataMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“FTS_JVM_CURRENT_MEMORY”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“FTS_JVM_MAX_MEMORY”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView”更改为“#/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“FTS_MEMORY_MAPPED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/FtsMemoryMappedDataMetricThresholdView”更改为“#/components/schemas/FtsMemoryMappedDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“FTS_MEMORY_RESIDENT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/FtsMemoryResidentDataMetricThresholdView”更改为“#/components/schemas/FtsMemoryResidentDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“FTS_MEMORY_VIRTUAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/FtsMemoryVirtualDataMetricThresholdView”更改为“#/components/schemas/FtsMemoryVirtualDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“FTS_PROCESS_CPU_KERNEL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FtsProcessCpuKernelRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“FTS_PROCESS_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FtsProcessCpuUserRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“GLOBAL_ACCESSES_NOT_IN_MEMORY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalAccessesNotInMemoryRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“GLOBAL_LOCK_CURRENT_QUEUE_READERS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“GLOBAL_LOCK_CURRENT_QUEUE_TOTAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“GLOBAL_LOCK_CURRENT_QUEUE_WRITERS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“GLOBAL_LOCK_PERCENTAGE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockPercentageRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“GLOBAL_PAGE_FAULT_EXCEPTIONS_THROWN”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalPageFaultExceptionsThrownRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“INDEX_COUNTERS_BTREE_ACCESSES”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“INDEX_COUNTERS_BTREE_HITS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeHitsRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“INDEX_COUNTERS_BTREE_MISSES”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeMissesRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“INDEX_COUNTERS_BTREE_MISS_RATIO”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeMissRatioRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“JOURNALING_COMMITS_IN_WRITE_LOCK”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“JOURNALING_MB”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/JournalingMbDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“JOURNALING_WRITE_DATA_FILES_MB”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView”更改为“#/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“LOGICAL_SIZE”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/LogicalSizeDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_QUEUE_DEPTH_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionQueueDepthDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_QUEUE_DEPTH_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_QUEUE_DEPTH_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_READ_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_READ_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_READ_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_READ_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_READ_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_READ_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_SPACE_USED_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MaxDiskPartitionSpaceUsedDataRawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionSpaceUsedDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_SPACE_USED_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionSpaceUsedIndexRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_SPACE_USED_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionSpaceUsedJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_WRITE_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_WRITE_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_WRITE_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_WRITE_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_WRITE_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_DISK_PARTITION_WRITE_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_NORMALIZED_SYSTEM_CPU_STEAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_NORMALIZED_SYSTEM_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“MAX_SWAP_USAGE_FREE”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSwapUsageFreeDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_SWAP_USAGE_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/MaxSwapUsageUsedDataMetricThresholdView”更改为“#/components/schemas/MaxSwapUsageUsedDataMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“MAX_SYSTEM_MEMORY_AVAILABLE”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_SYSTEM_MEMORY_PERCENT_USED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_SYSTEM_MEMORY_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView”更改为“#/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_SYSTEM_NETWORK_IN”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSystemNetworkInDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MAX_SYSTEM_NETWORK_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/MaxSystemNetworkOutDataMetricThresholdView”更改为“#/components/schemas/MaxSystemNetworkOutDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MEMORY_MAPPED”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MemoryMappedDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MEMORY_RESIDENT”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MemoryResidentDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MEMORY_VIRTUAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/MemoryVirtualDataMetricThresholdView”更改为“#/components/schemas/MemoryVirtualDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MUNIN_CPU_IOWAIT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuIowaitRawMetricThresholdView”更改为“#/components/schemas/MuninCpuIowawaitRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MUNIN_CPU_IRQ”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuIrqRawMetricThresholdView”更改为“#/components/schemas/MuninCpuIrqRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MUNIN_CPU_NICE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuNiceRawMetricThresholdView”更改为“#/components/schemas/MuninCpuNiceRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MUNIN_CPU_SOFTIRQ”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MuninCpuSoftirqRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MUNIN_CPU_STEAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuStealRawMetricThresholdView”更改为“#/components/schemas/MuninCpuStealRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MUNIN_CPU_SYSTEM”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuSystemRawMetricThresholdView”更改为“#/components/schemas/MuninCpuSystemRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“MUNIN_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/MuninCpuUserRawMetricThresholdView”更改为“#/components/schemas/MuninCpuUserRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“NETWORK_BYTES_IN”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/NetworkBytesInDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“NETWORK_BYTES_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/NetworkBytesOutDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“NETWORK_NUM_REQUESTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NetworkNumRequestsRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“NORMALIZED_FTS_PROCESS_CPU_KERNEL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“NORMALIZED_FTS_PROCESS_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“NORMALIZED_SYSTEM_CPU_STEAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView”更改为“#/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“NORMALIZED_SYSTEM_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView”更改为“#/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterCmdRawMetricThresholdView”更改为“#/components/schemas/OpCounterCmdRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterDeleteRawMetricThresholdView”更改为“#/components/schemas/OpCounterDeleteRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterGetMoreRawMetricThresholdView”更改为“#/components/schemas/OpCounterGetMoreRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterInsertRawMetricThresholdView”更改为“#/components/schemas/OpCounterInsertRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_QUERY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterQueryRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_REPL_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterReplCmdRawMetricThresholdView”更改为“#/components/schemas/OpCounterReplCmdRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_REPL_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterReplDeleteRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_REPL_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterReplInsertRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_REPL_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterReplUpdateRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_TTL_DELETED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterTtlDeletedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/OpCounterUpdateRawMetricThresholdView”更改为“#/components/schemas/OpCounterUpdateRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPERATIONS_QUERIES_KILLED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OperationsQueriesKilledRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPERATIONS_SCAN_AND_ORDER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OperationsScanAndOrderRawMetricThresholdView”
  • 已针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPERATION_THROTTLING_REJECTED_OPERATIONS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OperationThrotdlingRejectedOperationsRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPLOG_MASTER_LAG_TIME_DIFF”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPLOG_MASTER_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogMasterTimeTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPLOG_MASTER_TIME_ESTIMATED_TTL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“OPLOG_RATE_GB_PER_HOUR”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/OplogRateGbPerHourDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“OPLOG_SLAVE_LAG_MASTER_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogSlaveLagMasterTimeTimeMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“QUERY_EXECUTOR_SCANNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/QueryExecutorScannedRawMetricThresholdView”更改为“#/components/schemas/QueryExecutorScannedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“QUERY_EXECUTOR_SCANNED_OBJECTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“QUERY_SPILL_TO_DISK_DURING_SORT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“QUERY_TARGETING_SCANNED_OBJECTS_PER_RETURNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“QUERY_TARGETING_SCANNED_PER_RETURNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“RESTARTS_IN_LAST_HOUR”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/RestartsInLastHourRawMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“SEARCH_INDEX_SIZE”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SearchIndexSizeDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_NUMBER_OF_FIELDS_IN_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfFieldsInIndexRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_NUMBER_OF_QUERIES_ERROR”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_NUMBER_OF_QUERIES_SUCCESS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_NUMBER_OF_QUERIES_TOTAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterDeleteRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterInsertRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterUpdateRawMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SEARCH_REPLICATION_LAG”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/SearchReplicationLagTimeMetricThresholdView”
  • 已将“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性的鉴别器键“SWAP_USAGE_FREE”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SwapUsageFreeDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SWAP_USAGE_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/SwapUsageUsedDataMetricThresholdView”更改为“#/components/schemas/SwapUsageUsedDataMetricThresholdView”
  • 针对“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SYSTEM_MEMORY_AVAILABLE”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/SystemMemoryAvailableDataMetricThresholdView”更改为“#/components/schemas/SystemMemoryAvailableDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SYSTEM_MEMORY_PERCENT_USED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView”更改为“#/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SYSTEM_MEMORY_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/SystemMemoryUsedDataMetricThresholdView”更改为“#/components/schemas/SystemMemoryUsedDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SYSTEM_NETWORK_IN”的映射值从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SystemNetworkInDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“SYSTEM_NETWORK_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SystemNetworkOutDataMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“TICKETS_AVAILABLE_READS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/TicketsAvailableReadsRawMetricThresholdView”更改为“#/components/schemas/TicketsAvailableReadsRawMetricThresholdView”
  • 对于“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性，鉴别器键“TICKETS_AVAILABLE_WRITES”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/TicketsAvailableWritesRawMetricThresholdView”
  • 添加 '#/components/schemas/AssertRegularRawMetricThresholdView, #/components/schemas/AssertWarningRawMetricThresholdView, #/components/schemas/AssertMsgRawMetricThresholdView, #/components/schemas/AssertUserRawMetricThresholdView, #/components/schemas/OpCounterCmdRawMetricThresholdView, #/components/schemas/OpCounterCmdRawMetricThresholdView, #/components/schemas/OpCounterRawMetricThresholdView, #/components/schemas/OpCounterCmdRawMetricThresholdView, #/components/schemas/OpCounterUpdateRawMetricThresholdView, #/components/schemas/OpCounterDeleteRawMetricThresholdView, #/components/schemas/OpCounterTtlDeletedRawMetricThresholdView, #/components/schemas/OpCounterInsertRawMetricThresholdView, #/components/schemas/OpCounterGetMoreRawMetricThresholdView, #/components/schemas/OpCounterGetMoreRawMetricReplas/OpCounterMetricReplas/schemeView components/schemas/OpCounterReplUpdateRawMetricThresholdView, #/components/schemas/OpCounterReplDeleteRawMetricThresholdView, #/components/schemas/OpCounterReplInsertRawMetricThresholdView, #/components/schemas/FtsMemoryResidentDataMetricThresholdView, #/components/schemas/FtsMemoryV irtualDataMetricThresholdView, #/components/schemas/FtsMemoryMappedDataMetricThresholdView, #/components/schemas/FtsProcessCpuUserRawMetricThresholdView, #/components/schemas/FtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MemoryResidentDataMetricThresholdView, #/components/schemas/MemoryVirtualDataMetricThresholdView, #/components/schemas/MemoryMappedDataMetricThresholdView, #/components/schemas/ComputedMemoryDataMetricThresholdView, #/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdView, #/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdViewHitsMetric components/schemas/IndexCountersBtreeMissesRawMetricThresholdView, #/components/schemas/IndexCountersBtreeMissRatioRawMetricThresholdView, #/components/schemas/GlobalLockPercentageRawMetricTh resholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/ConnectionsRawMetricThresholdView, #/components/schemas/ConnectionsMaxRawMetricThresholdView, #/components/schemas/ConnectionsPercentRawMetricThresholdView, #/components/schemas/GlobalAccessesNotInMemoryRawMetricThresholdView, #/components/schemas/GlobalPageFaultRawMetricThrownMetricThrownView #/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView, #/components/schemas/CursorsTotalOpenRawMetricThresholdView, #/components/schemas/CursorsTotalTimedOutRawMetricThresholdView, #/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView, #/ components/schemas/NetworkBytesInDataMetricThresholdView, #/components/schemas/NetworkBytesOutDataMetricThresholdView, #/components/schemas/NetworkNumRequestsRawMetricThresholdView, #/components/ schemas/OplogMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView, #/components/schemas/OplogSlaveLagMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView, #/components/schemas/OplogRateGbPerHourDataMetricThresholdView, #/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView, #/components/schemas/ DbStorageTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView, #/components/schemas/DbIndexSizeTotalDataMetricThresholdView, #/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView, #/components/schemas/JournalingMbDataMetricThresholdView, #/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView, #/components/schemas/TicketsAvailableReadsRawMetricThresholdView, #/components/schemas/TicketsAvailableWritesRawMetricThresholdView, #/components/schemas/Cache UsageDirtyDataMetricThresholdView, #/components/schemas/CacheUsageUsedDataMetricThresholdView, #/components/schemas/CacheBytesReadIntoDataMetricThresholdView, #/components/schemas/CacheBytesWrittenFromDataMetricThresholdView, #/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView, #/ components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsJournalRawMetricThre sholdView, #/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/FtsDiskUtilizationDataMetricThresholdView, #/components/schemas/MuninCpuUserRawMetricThresholdView, #/components/schemas/MuninCpuNiceRawMetricThresholdView, #/ components/schemas/MuninCpuSystemRawMetricThresholdView, #/components/schemas/MuninCpuIowaitRawMetricThresholdView, #/components/schem as/MuninCpuIrqRawMetricThresholdView, #/components/schemas/MuninCpuSoftirqRawMetricThresholdView, #/components/schemas/MuninCpuStealRawMetricThresholdView, #/components/schemas/DocumentReturnedRawMetricThresholdView, #/components/schemas/DocumentInsertedRawMetricThresholdView, #/components/schemas/MuninCpuStealRawMetricThresholdView, #/components/schemas/DocumentInsertedRawMetricThresholdView, #/components/schemas/componentsRawMetricThresholdView DocumentDeletedRawMetricThresholdView, #/components/schemas/OperationsScanAndOrderRawMetricThresholdView, #/components/schemas/QueryExecutorScannedRawMetricThresholdView, #/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView, #/components/schemas/OperationThrottlingRejectedOperationsRawMetricThresholdView, #/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView, #/components/schemas/OperationsQueriesKilledRawMetricThresholdView, #/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView, #/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView, #/components/sch emas/AvgReadExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgWriteExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgCommandExecutionTimeTimeMetricThresholdView, #/components/schemas/LogicalSizeDataMetricThresholdView, #/components/schemas/RestartsInLastHourRawMetricThresholdView, #/components/schemas/SystemMemtricThoryschem SystemMemoryAvailableDataMetricThresholdView, #/components/schemas/SwapUsageUsedDataMetricThresholdView, #/components/schemas/SwapUsageFreeDataMetricThresholdView, #/components/schemas/SystemNetworkInDataMetricThresholdView, #/components/schemas/SystemNetworkOutDataMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/MaxDiskPartitionSpaceUsedDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionSpaceUsedIndexRawMetricThresholdView, #/components/schemas/MaxDiskPart itionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/ components/schemas/MaxDiskParti tionQueueDepthDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView, #/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView, #/components/schemas/MaxSwapUsageUsedDataMetricThresholdView, #/components/schemas/MaxSwapUsageFreeDataMetricThresholdView, #/components/schemas/MaxSystemNetworkInDataMetricThresholdView, #/components/schemas/MaxSystemNetworkOutDataMetricThresholdView, #/components/schemas/SearchIndexSizeDataMetricThresholdView, #/components/schemas/SearchNumberOfFieldsInIndexRawMetricThresholdView, #/components/schemas/SearchRealThresholdView, #/components/schemas/SearchRealThresholdView, components/schemas/NumberMetricThresholdView, #/components/schemas/SearchOpCounterInsertRawMetricThresholdView, #/components/schemas/SearchOpCou nterDeleteRawMetricThresholdView, #/components/schemas/SearchOpCounterUpdateRawMetricThresholdView, #/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView, #/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView, #/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView' 到该响应的 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 响应属性'oneOf' 列表
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“ASSERT_MSG”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/AssertMsgRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“ASSERT_REGULAR”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/AssertRegularRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“ASSERT_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/AssertUserRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“ASSERT_WARNING”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/AssertWarningRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“AVG_COMMAND_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/AvgCommandExecutionTimeTimeMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“AVG_READ_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/AvgReadExecutionTimeTimeMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“AVG_WRITE_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/AvgWriteExecutionTimeTimeMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“CACHE_BYTES_READ_INTO”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/CacheBytesReadIntoDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“CACHE_BYTES_WRITTEN_FROM”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/CacheBytesWrittenFromDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“CACHE_USAGE_DIRTY”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/CacheUsageDirtyDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“CACHE_USAGE_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/CacheUsageUsedDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“COMPUTED_MEMORY”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/ComputedMemoryDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“CONNECTIONS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ConnectionsRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“CONNECTIONS_MAX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ConnectionsMaxRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“CONNECTIONS_PERCENT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ConnectionsPercentRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“CURSORS_TOTAL_CLIENT_CURSORS_SIZE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“CURSORS_TOTAL_OPEN”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/CursorsTotalOpenRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“CURSORS_TOTAL_TIMED_OUT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/CursorsTotalTimedOutRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DB_DATA_SIZE_TOTAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/DbDataSizeTotalDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DB_DATA_SIZE_TOTAL_WO_SYSTEM”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DB_INDEX_SIZE_TOTAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/DbIndexSizeTotalDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DB_STORAGE_TOTAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/DbStorageTotalDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_QUEUE_DEPTH_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_QUEUE_DEPTH_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_QUEUE_DEPTH_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_READ_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_READ_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold，鉴别器键“DISK_PARTITION_READ_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_READ_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_READ_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_READ_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_SPACE_USED_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_SPACE_USED_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9：主机指标警报配置]/metricThreshold，鉴别器键“DISK_PARTITION_SPACE_USED_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionSpaceUsedJournalRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_WRITE_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_WRITE_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold，鉴别器键 'DISK_PARTITION_WRITE_IOPS_JOURNAL' 的映射值从 '#/components/schemas/RawMetricThresholdView' 更改为 '#/components/schemas/DiskPartitionWriteIopsJournalRawMetricThresholdView' ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_WRITE_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_WRITE_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DISK_PARTITION_WRITE_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DOCUMENT_DELETED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DocumentDeletedRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DOCUMENT_INSERTED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DocumentInsertedRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DOCUMENT_RETURNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DocumentReturnedRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“DOCUMENT_UPDATED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DocumentUpdatedRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“EXTRA_INFO_PAGE_FAULTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“FTS_DISK_UTILIZATION”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FtsDiskUtilizationDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“FTS_JVM_CURRENT_MEMORY”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“FTS_JVM_MAX_MEMORY”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“FTS_MEMORY_MAPPED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FtsMemoryMappedDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“FTS_MEMORY_RESIDENT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FtsMemoryResidentDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“FTS_MEMORY_VIRTUAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FtsMemoryVirtualDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“FTS_PROCESS_CPU_KERNEL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FtsProcessCpuKernelRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“FTS_PROCESS_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FtsProcessCpuUserRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“GLOBAL_ACCESSES_NOT_IN_MEMORY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalAccessesNotInMemoryRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“GLOBAL_LOCK_CURRENT_QUEUE_READERS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“GLOBAL_LOCK_CURRENT_QUEUE_TOTAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“GLOBAL_LOCK_CURRENT_QUEUE_WRITERS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“GLOBAL_LOCK_PERCENTAGE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalLockPercentageRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“GLOBAL_PAGE_FAULT_EXCEPTIONS_THROWN”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/GlobalPageFaultExceptionsThrownRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“INDEX_COUNTERS_BTREE_ACCESSES”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“INDEX_COUNTERS_BTREE_HITS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeHitsRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“INDEX_COUNTERS_BTREE_MISSES”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeMissesRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold，鉴别器键“INDEX_COUNTERS_BTREE_MISS_RATIO”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/IndexCountersBtreeMissRatioRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“JOURNALING_COMMITS_IN_WRITE_LOCK”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“JOURNALING_MB”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/JournalingMbDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“JOURNALING_WRITE_DATA_FILES_MB”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“LOGICAL_SIZE”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/LogicalSizeDataMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold，鉴别器键“MAX_DISK_PARTITION_QUEUE_DEPTH_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionQueueDepthDataRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold，鉴别器键“MAX_DISK_PARTITION_QUEUE_DEPTH_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_DISK_PARTITION_QUEUE_DEPTH_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_DISK_PARTITION_READ_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold，鉴别器键“MAX_DISK_PARTITION_READ_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_DISK_PARTITION_READ_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_DISK_PARTITION_READ_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_DISK_PARTITION_READ_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_DISK_PARTITION_READ_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_DISK_PARTITION_SPACE_USED_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionSpaceUsedDataRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold，鉴别器键“MAX_DISK_PARTITION_SPACE_USED_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionSpaceUsedIndexRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_DISK_PARTITION_SPACE_USED_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionSpaceUsedJournalRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_DISK_PARTITION_WRITE_IOPS_DATA”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold，鉴别器键“MAX_DISK_PARTITION_WRITE_IOPS_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_DISK_PARTITION_WRITE_IOPS_JOURNAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold，鉴别器键“MAX_DISK_PARTITION_WRITE_LATENCY_DATA”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold，鉴别器键“MAX_DISK_PARTITION_WRITE_LATENCY_INDEX”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_DISK_PARTITION_WRITE_LATENCY_JOURNAL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView” ' 响应属性
  • 针对 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold，鉴别器键 'MAX_NORMALIZED_SYSTEM_CPU_STEAL' 的映射值从 '#/components/schemas/RawMetricThresholdView' 更改为 '#/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView' ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_NORMALIZED_SYSTEM_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_SWAP_USAGE_FREE”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSwapUsageFreeDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_SWAP_USAGE_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSwapUsageUsedDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_SYSTEM_MEMORY_AVAILABLE”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9：主机指标警报配置]/metricThreshold，鉴别器键“MAX_SYSTEM_MEMORY_PERCENT_USED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_SYSTEM_MEMORY_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_SYSTEM_NETWORK_IN”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSystemNetworkInDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MAX_SYSTEM_NETWORK_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MaxSystemNetworkOutDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MEMORY_MAPPED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MemoryMappedDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MEMORY_RESIDENT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MemoryResidentDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MEMORY_VIRTUAL”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/MemoryVirtualDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MUNIN_CPU_IOWAIT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MuninCpuIowawaitRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MUNIN_CPU_IRQ”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MuninCpuIrqRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MUNIN_CPU_NICE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MuninCpuNiceRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MUNIN_CPU_SOFTIRQ”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MuninCpuSoftirqRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MUNIN_CPU_STEAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MuninCpuStealRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MUNIN_CPU_SYSTEM”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MuninCpuSystemRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“MUNIN_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/MuninCpuUserRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“NETWORK_BYTES_IN”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/NetworkBytesInDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“NETWORK_BYTES_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/NetworkBytesOutDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“NETWORK_NUM_REQUESTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NetworkNumRequestsRawMetricThresholdView” ' 响应属性
  • 针对 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold，鉴别器键 'NORMALIZED_FTS_PROCESS_CPU_KERNEL' 的映射值从 '#/components/schemas/RawMetricThresholdView' 更改为 '#/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView' ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“NORMALIZED_FTS_PROCESS_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“NORMALIZED_SYSTEM_CPU_STEAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“NORMALIZED_SYSTEM_CPU_USER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPCOUNTER_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterCmdRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterDeleteRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterGetMoreRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterInsertRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPCOUNTER_QUERY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterQueryRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPCOUNTER_REPL_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterReplCmdRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPCOUNTER_REPL_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterReplDeleteRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPCOUNTER_REPL_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterReplInsertRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPCOUNTER_REPL_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterReplUpdateRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPCOUNTER_TTL_DELETED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterTtlDeletedRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OpCounterUpdateRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPERATIONS_QUERIES_KILLED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OperationsQueriesKilledRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPERATIONS_SCAN_AND_ORDER”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OperationsScanAndOrderRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPERATION_THROTTLING_REJECTED_OPERATIONS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/OperationThrotdlingRejectedOperationsRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPLOG_MASTER_LAG_TIME_DIFF”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView” ' 响应属性
  • 对于 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold，鉴别器键 'OPLOG_MASTER_TIME' 的映射值从 '#/components/schemas/TimeMetricThresholdView' 更改为 '#/components/schemas/OplogMasterTimeTimeMetricThresholdView' ' 响应属性
  • 针对“results/items/oneOf[subschema #9：主机指标警报配置]/metricThreshold，鉴别器键“OPLOG_MASTER_TIME_ESTIMATED_TTL”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPLOG_RATE_GB_PER_HOUR”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/OplogRateGbPerHourDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“OPLOG_SLAVE_LAG_MASTER_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/OplogSlaveLagMasterTimeTimeMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“QUERY_EXECUTOR_SCANNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QueryExecutorScannedRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“QUERY_EXECUTOR_SCANNED_OBJECTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView” ' 响应属性
  • 鉴别器键“QUERY_SPILL_TO_DISK_DURING_SORT”的映射值从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView”（针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold） ' 响应属性
  • 针对“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“QUERY_TARGETING_SCANNED_OBJECTS_PER_RETURNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“QUERY_TARGETING_SCANNED_PER_RETURNED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“RESTARTS_IN_LAST_HOUR”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/RestartsInLastHourRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SEARCH_INDEX_SIZE”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SearchIndexSizeDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SEARCH_NUMBER_OF_FIELDS_IN_INDEX”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfFieldsInIndexRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SEARCH_NUMBER_OF_QUERIES_ERROR”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SEARCH_NUMBER_OF_QUERIES_SUCCESS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView” ' 响应属性
  • 针对“results/items/oneOf[subschema #9：主机指标警报配置]/metricThreshold，鉴别器键“SEARCH_NUMBER_OF_QUERIES_TOTAL”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SEARCH_OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterDeleteRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SEARCH_OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SEARCH_OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterInsertRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SEARCH_OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SearchOpCounterUpdateRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SEARCH_REPLICATION_LAG”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/SearchReplicationLagTimeMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SWAP_USAGE_FREE”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SwapUsageFreeDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SWAP_USAGE_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SwapUsageUsedDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SYSTEM_MEMORY_AVAILABLE”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SystemMemoryAvailableDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SYSTEM_MEMORY_PERCENT_USED”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SYSTEM_MEMORY_USED”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SystemMemoryUsedDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SYSTEM_NETWORK_IN”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SystemNetworkInDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“SYSTEM_NETWORK_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/SystemNetworkOutDataMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“TICKETS_AVAILABLE_READS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/TicketsAvailableReadsRawMetricThresholdView” ' 响应属性
  • 对于“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”，鉴别器键“TICKETS_AVAILABLE_WRITES”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/TicketsAvailableWritesRawMetricThresholdView” ' 响应属性
  • 添加 '#/components/schemas/AssertRegularRawMetricThresholdView, #/components/schemas/AssertWarningRawMetricThresholdView, #/components/schemas/AssertMsgRawMetricThresholdView, #/components/schemas/AssertUserRawMetricThresholdView, #/components/schemas/OpCounterCmdRawMetricThresholdView, #/components/schemas/OpCounterCmdRawMetricThresholdView, #/components/schemas/OpCounterRawMetricThresholdView, #/components/schemas/OpCounterCmdRawMetricThresholdView, #/components/schemas/OpCounterUpdateRawMetricThresholdView, #/components/schemas/OpCounterDeleteRawMetricThresholdView, #/components/schemas/OpCounterTtlDeletedRawMetricThresholdView, #/components/schemas/OpCounterInsertRawMetricThresholdView, #/components/schemas/OpCounterGetMoreRawMetricThresholdView, #/components/schemas/OpCounterGetMoreRawMetricReplas/OpCounterMetricReplas/schemeView components/schemas/OpCounterReplUpdateRawMetricThresholdView, #/components/schemas/OpCounterReplDeleteRawMetricThresholdView, #/components/schemas/OpCounterReplInsertRawMetricThresholdView, #/components/schemas/FtsMemoryResidentDataMetricThresholdView, #/components/schemas/FtsMemoryV irtualDataMetricThresholdView, #/components/schemas/FtsMemoryMappedDataMetricThresholdView, #/components/schemas/FtsProcessCpuUserRawMetricThresholdView, #/components/schemas/FtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MemoryResidentDataMetricThresholdView, #/components/schemas/MemoryVirtualDataMetricThresholdView, #/components/schemas/MemoryMappedDataMetricThresholdView, #/components/schemas/ComputedMemoryDataMetricThresholdView, #/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdView, #/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdViewHitsMetric components/schemas/IndexCountersBtreeMissesRawMetricThresholdView, #/components/schemas/IndexCountersBtreeMissRatioRawMetricThresholdView, #/components/schemas/GlobalLockPercentageRawMetricTh resholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/ConnectionsRawMetricThresholdView, #/components/schemas/ConnectionsMaxRawMetricThresholdView, #/components/schemas/ConnectionsPercentRawMetricThresholdView, #/components/schemas/GlobalAccessesNotInMemoryRawMetricThresholdView, #/components/schemas/GlobalPageFaultRawMetricThrownMetricThrownView #/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView, #/components/schemas/CursorsTotalOpenRawMetricThresholdView, #/components/schemas/CursorsTotalTimedOutRawMetricThresholdView, #/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView, #/ components/schemas/NetworkBytesInDataMetricThresholdView, #/components/schemas/NetworkBytesOutDataMetricThresholdView, #/components/schemas/NetworkNumRequestsRawMetricThresholdView, #/components/ schemas/OplogMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView, #/components/schemas/OplogSlaveLagMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView, #/components/schemas/OplogRateGbPerHourDataMetricThresholdView, #/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView, #/components/schemas/ DbStorageTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView, #/components/schemas/DbIndexSizeTotalDataMetricThresholdView, #/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView, #/components/schemas/JournalingMbDataMetricThresholdView, #/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView, #/components/schemas/TicketsAvailableReadsRawMetricThresholdView, #/components/schemas/TicketsAvailableWritesRawMetricThresholdView, #/components/schemas/Cache UsageDirtyDataMetricThresholdView, #/components/schemas/CacheUsageUsedDataMetricThresholdView, #/components/schemas/CacheBytesReadIntoDataMetricThresholdView, #/components/schemas/CacheBytesWrittenFromDataMetricThresholdView, #/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView, #/ components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsJournalRawMetricThre sholdView, #/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/FtsDiskUtilizationDataMetricThresholdView, #/components/schemas/MuninCpuUserRawMetricThresholdView, #/components/schemas/MuninCpuNiceRawMetricThresholdView, #/ components/schemas/MuninCpuSystemRawMetricThresholdView, #/components/schemas/MuninCpuIowaitRawMetricThresholdView, #/components/schem as/MuninCpuIrqRawMetricThresholdView, #/components/schemas/MuninCpuSoftirqRawMetricThresholdView, #/components/schemas/MuninCpuStealRawMetricThresholdView, #/components/schemas/DocumentReturnedRawMetricThresholdView, #/components/schemas/DocumentInsertedRawMetricThresholdView, #/components/schemas/MuninCpuStealRawMetricThresholdView, #/components/schemas/DocumentInsertedRawMetricThresholdView, #/components/schemas/componentsRawMetricThresholdView DocumentDeletedRawMetricThresholdView, #/components/schemas/OperationsScanAndOrderRawMetricThresholdView, #/components/schemas/QueryExecutorScannedRawMetricThresholdView, #/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView, #/components/schemas/OperationThrottlingRejectedOperationsRawMetricThresholdView, #/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView, #/components/schemas/OperationsQueriesKilledRawMetricThresholdView, #/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView, #/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView, #/components/sch emas/AvgReadExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgWriteExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgCommandExecutionTimeTimeMetricThresholdView, #/components/schemas/LogicalSizeDataMetricThresholdView, #/components/schemas/RestartsInLastHourRawMetricThresholdView, #/components/schemas/SystemMemtricThoryschem SystemMemoryAvailableDataMetricThresholdView, #/components/schemas/SwapUsageUsedDataMetricThresholdView, #/components/schemas/SwapUsageFreeDataMetricThresholdView, #/components/schemas/SystemNetworkInDataMetricThresholdView, #/components/schemas/SystemNetworkOutDataMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/MaxDiskPartitionSpaceUsedDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionSpaceUsedIndexRawMetricThresholdView, #/components/schemas/MaxDiskPart itionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/ components/schemas/MaxDiskParti tionQueueDepthDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView, #/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView, #/components/schemas/MaxSwapUsageUsedDataMetricThresholdView, #/components/schemas/MaxSwapUsageFreeDataMetricThresholdView, #/components/schemas/MaxSystemNetworkInDataMetricThresholdView, #/components/schemas/MaxSystemNetworkOutDataMetricThresholdView, #/components/schemas/SearchIndexSizeDataMetricThresholdView, #/components/schemas/SearchNumberOfFieldsInIndexRawMetricThresholdView, #/components/schemas/SearchRealThresholdView, #/components/schemas/SearchRealThresholdView, components/schemas/NumberMetricThresholdView, #/components/schemas/SearchOpCounterInsertRawMetricThresholdView, #/components/schemas/SearchOpCou nterDeleteRawMetricThresholdView, #/components/schemas/SearchOpCounterUpdateRawMetricThresholdView, #/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView, #/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView, #/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView”添加到该响应的“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性“oneOf”列表

2025 年 7 月 23 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 对于“results/items/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”，鉴别器键“FLEX_AVG_COMMAND_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”，鉴别器键“FLEX_AVG_WRITE_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/FlexAVGWriteExecutionTimeMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”，鉴别器键“FLEX_CONNECTIONS_PERCENT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexConnectionPercentRawMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”，鉴别器键“FLEX_NETWORK_BYTES_IN”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FlexNetworkBytesInDataMetricThresholdView”响应属性
  • 针对“results/items/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”，鉴别器键“FLEX_NETWORK_BYTES_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FlexNetworkBytesOutDataMetricThresholdView”响应属性
  • 针对“results/items/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”，鉴别器键“FLEX_NETWORK_NUM_REQUESTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexNetworkNumRequestsRawMetricThresholdView”响应属性
  • 针对“results/items/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”，鉴别器键“FLEX_OPCOUNTER_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterCMDRawMetricThresholdView”响应属性
  • 针对“results/items/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”，鉴别器键“FLEX_OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterDeleteRawMetricThresholdView”响应属性
  • 针对“results/items/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”，鉴别器键“FLEX_OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterGetMoreRawMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”，鉴别器键“FLEX_OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterInsertRawMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”，鉴别器键“FLEX_OPCOUNTER_QUERY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterQueryRawMetricThresholdView”响应属性
  • 针对“results/items/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”，鉴别器键“FLEX_OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterUpdateRawMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”，鉴别器键“SERVERLESS_AVG_COMMAND_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”，鉴别器键“SERVERLESS_AVG_WRITE_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”，鉴别器键“SERVERLESS_CONNECTIONS_PERCENT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessConnectionPercentageRawMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”，鉴别器键“SERVERLESS_NETWORK_BYTES_IN”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”，鉴别器键“SERVERLESS_NETWORK_BYTES_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”，鉴别器键“SERVERLESS_NETWORK_NUM_REQUESTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”，鉴别器键“SERVERLESS_OPCOUNTER_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”，鉴别器键“SERVERLESS_OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”，鉴别器键“SERVERLESS_OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”，鉴别器键“SERVERLESS_OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”，鉴别器键“SERVERLESS_OPCOUNTER_QUERY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”，鉴别器键“SERVERLESS_OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterUpdateRawMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”，鉴别器键“SERVERLESS_TOTAL_WRITE_UNITS”的映射值从“#/components/schemas/RPUMetricThresholdView”从“#/components/schemas/RPUMetricThresholdView”更改为“#/components/schemas/ServerlessTotalWriteUnitsRPUMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #16：流处理器指标警报配置]/”，鉴别器键“STREAM_PROCESSOR_DLQ_MESSAGE_COUNT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DLQRawMetricThresholdView”。阈值响应属性
  • 鉴别器键 'STREAM_PROCESSOR_KAFKA_LAG' 的映射值从 '#/components/schemas/RawMetricThresholdView' 更改为 'results/items/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/阈值响应属性
  • 将 '#/components/schemas/KafkaRawMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/DLQRawMetricThresholdView, #/components/schemas/RawMetricThresholdView' 添加到 'results/items/oneOf[subschema #16: Stream处理器指标警报配置]/threshold' 响应的响应属性'oneOf' 列表
  • 已添加 '#/components/schemas/RawMetricThresholdView, #/components/schemas/FlexConnectionPercentRawMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/components/schemas/FlexNetworkBytesInDataMetricThresholdView, #/components/schemas/FlexNetworkBytesOutDataMetricThresholdView, #/components/schemas/FlexNetworkNumRequestsRawMetricThresholdView, #/components/schemas/FlexOpCounterCMDRawMetricThresholdView, #/components/schemas/FlexOpCounterDeleteRawMetricThresholdView, #/components/schemas/FlexOpCounterInsertRawMetricThresholdView, #/components/schemas/FlexOpCounterQueryRawMetricThresholdView, #/components/schemas/FlexOpCounterUpdateRawMetricThresholdView, #/components/components/schemas/FlexOpCounterUpdateRawMetricThreshold components/schemas/TimeMetricThresholdView, #/components/schemas/FlexAVGWriteTimeMetricThresholdView, #/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView' 到 'results/items/oneOf[subschema #14: Flex Alert Configuration]/metricT href 响应的响应属性'oneOf' 列表
  • 添加了 '#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView, #/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/ServerlessTotalWriteUnitsRPUMetricThresholdView, #/components/schemas/RPUMetricThresholdView, #/components/schemas/RPUMetricViewerUpdateRaw,MetricView #/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView, #/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView, #/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView, #/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView, #/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView, #/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView, #/ components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView, #/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/compon ents/schemas/ServerlessConnectionPercentageRawMetricThresholdView, #/components/schemas/RawMetricThresholdView' 到该响应的 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold' 响应属性'oneOf' 列表
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”请求属性，鉴别器键“FLEX_AVG_COMMAND_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”请求属性，鉴别器键“FLEX_AVG_WRITE_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/FlexAVGWriteExecutionTimeMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”请求属性，鉴别器键“FLEX_CONNECTIONS_PERCENT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexConnectionPercentRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”请求属性，鉴别器键“FLEX_NETWORK_BYTES_IN”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FlexNetworkBytesInDataMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”请求属性，鉴别器键“FLEX_NETWORK_BYTES_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FlexNetworkBytesOutDataMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”请求属性，鉴别器键“FLEX_NETWORK_NUM_REQUESTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexNetworkNumRequestsRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”请求属性，鉴别器键“FLEX_OPCOUNTER_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterCMDRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”请求属性，鉴别器键“FLEX_OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterDeleteRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”请求属性，鉴别器键“FLEX_OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterGetMoreRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”请求属性，鉴别器键“FLEX_OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterInsertRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”请求属性，鉴别器键“FLEX_OPCOUNTER_QUERY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterQueryRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”请求属性，鉴别器键“FLEX_OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterUpdateRawMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”请求属性，鉴别器键“SERVERLESS_AVG_COMMAND_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”请求属性，鉴别器键“SERVERLESS_AVG_WRITE_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”请求属性，鉴别器键“SERVERLESS_CONNECTIONS_PERCENT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessConnectionPercentageRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”请求属性，鉴别器键“SERVERLESS_NETWORK_BYTES_IN”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”请求属性，鉴别器键“SERVERLESS_NETWORK_BYTES_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”请求属性，鉴别器键“SERVERLESS_NETWORK_NUM_REQUESTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”请求属性，鉴别器键“SERVERLESS_OPCOUNTER_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”请求属性，鉴别器键“SERVERLESS_OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”请求属性，鉴别器键“SERVERLESS_OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”请求属性，鉴别器键“SERVERLESS_OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”请求属性，鉴别器键“SERVERLESS_OPCOUNTER_QUERY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”请求属性，鉴别器键“SERVERLESS_OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterUpdateRawMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”请求属性，鉴别器键“SERVERLESS_TOTAL_WRITE_UNITS”的映射值从“#/components/schemas/RPUMetricThresholdView”从“#/components/schemas/RPUMetricThresholdView”更改为“#/components/schemas/ServerlessTotalWriteUnitsRPUMetricThresholdView”
  • 针对“/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold”请求，鉴别器键“STREAM_PROCESSOR_DLQ_MESSAGE_COUNT”的映射值从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DLQRawMetricThresholdView”属性
  • 针对“/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold”请求，鉴别器键“STREAM_PROCESSOR_KAFKA_LAG”的映射值从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/KafkaRawMetricThresholdView”属性
  • 将 '#/components/schemas/KafkaRawMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/DLQRawMetricThresholdView, #/components/schemas/RawMetricThresholdView' 添加到 '/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold'请求属性'oneOf' 列表
  • 已添加 '#/components/schemas/RawMetricThresholdView, #/components/schemas/FlexConnectionPercentRawMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/components/schemas/FlexNetworkBytesInDataMetricThresholdView, #/components/schemas/FlexNetworkBytesOutDataMetricThresholdView, #/components/schemas/FlexNetworkNumRequestsRawMetricThresholdView, #/components/schemas/FlexOpCounterCMDRawMetricThresholdView, #/components/schemas/FlexOpCounterDeleteRawMetricThresholdView, #/components/schemas/FlexOpCounterInsertRawMetricThresholdView, #/components/schemas/FlexOpCounterQueryRawMetricThresholdView, #/components/schemas/FlexOpCounterUpdateRawMetricThresholdView, #/components/components/schemas/FlexOpCounterUpdateRawMetricThreshold components/schemas/TimeMetricThresholdView, #/components/schemas/FlexAVGWriteTimeMetricThresholdView, #/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView' 到 '/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold'请求属性'oneOf' 列表
  • 添加了 '#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView, #/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/ServerlessTotalWriteUnitsRPUMetricThresholdView, #/components/schemas/RPUMetricThresholdView, #/components/schemas/RPUMetricViewerUpdateRaw,MetricView #/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView, #/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView, #/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView, #/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView, #/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView, #/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView, #/ components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView, #/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/compon ents/schemas/ServerlessConnectionPercentageRawMetricThresholdView, #/components/schemas/RawMetricThresholdView' 到 '/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold'请求属性'oneOf' 列表
  • 已将“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性的鉴别器键“FLEX_AVG_COMMAND_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView”
  • 已将“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性的鉴别器键“FLEX_AVG_WRITE_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/FlexAVGWriteExecutionTimeMetricThresholdView”
  • 已将“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性的鉴别器键“FLEX_CONNECTIONS_PERCENT”的映射值从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexConnectionPercentRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex 警报配置]/metricThreshold”响应属性，鉴别器键“FLEX_NETWORK_BYTES_IN”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FlexNetworkBytesInDataMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性，鉴别器键“FLEX_NETWORK_BYTES_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FlexNetworkBytesOutDataMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性，鉴别器键“FLEX_NETWORK_NUM_REQUESTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexNetworkNumRequestsRawMetricThresholdView”
  • 对于“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性，鉴别器键“FLEX_OPCOUNTER_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterCMDRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex 警报配置]/metricThreshold”响应属性，鉴别器键“FLEX_OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterDeleteRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性，鉴别器键“FLEX_OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterGetMoreRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性，鉴别器键“FLEX_OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterInsertRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性，鉴别器键“FLEX_OPCOUNTER_QUERY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/FlexOpCounterQueryRawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterQueryRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性，鉴别器键“FLEX_OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterUpdateRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_AVG_COMMAND_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_AVG_WRITE_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_CONNECTIONS_PERCENT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessConnectionPercentageRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_NETWORK_BYTES_IN”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_NETWORK_BYTES_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_NETWORK_NUM_REQUESTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_OPCOUNTER_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_OPCOUNTER_QUERY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterUpdateRawMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_TOTAL_WRITE_UNITS”的映射值从“#/components/schemas/RPUMetricThresholdView”从“#/components/schemas/RPUMetricThresholdView”更改为“#/components/schemas/ServerlessTotalWriteUnitsRPUMetricThresholdView”
  • 针对“/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold”响应，鉴别器键“STREAM_PROCESSOR_DLQ_MESSAGE_COUNT”的映射值从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DLQRawMetricThresholdView”属性
  • 针对“/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold”响应，鉴别器键“STREAM_PROCESSOR_KAFKA_LAG”的映射值从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/KafkaRawMetricThresholdView”属性
  • 将 '#/components/schemas/KafkaRawMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/DLQRawMetricThresholdView, #/components/schemas/RawMetricThresholdView' 添加到 '/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold' 响应的响应属性'oneOf' 列表
  • 已添加 '#/components/schemas/RawMetricThresholdView, #/components/schemas/FlexConnectionPercentRawMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/components/schemas/FlexNetworkBytesInDataMetricThresholdView, #/components/schemas/FlexNetworkBytesOutDataMetricThresholdView, #/components/schemas/FlexNetworkNumRequestsRawMetricThresholdView, #/components/schemas/FlexOpCounterCMDRawMetricThresholdView, #/components/schemas/FlexOpCounterDeleteRawMetricThresholdView, #/components/schemas/FlexOpCounterInsertRawMetricThresholdView, #/components/schemas/FlexOpCounterQueryRawMetricThresholdView, #/components/schemas/FlexOpCounterUpdateRawMetricThresholdView, #/components/components/schemas/FlexOpCounterUpdateRawMetricThreshold components/schemas/TimeMetricThresholdView, #/components/schemas/FlexAVGWriteTimeMetricThresholdView, #/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView' 到 '/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold' res响应的 ponse属性“oneOf”列表
  • 添加了 '#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView, #/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/ServerlessTotalWriteUnitsRPUMetricThresholdView, #/components/schemas/RPUMetricThresholdView, #/components/schemas/RPUMetricViewerUpdateRaw,MetricView #/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView, #/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView, #/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView, #/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView, #/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView, #/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView, #/ components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView, #/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/compon ents/schemas/ServerlessConnectionPercentageRawMetricThresholdView, #/components/schemas/RawMetricThresholdView' 添加到响应的 '/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold' 响应属性'oneOf' 列表
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 已将“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性的鉴别器键“FLEX_AVG_COMMAND_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView”
  • 已将“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性的鉴别器键“FLEX_AVG_WRITE_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/FlexAVGWriteExecutionTimeMetricThresholdView”
  • 已将“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性的鉴别器键“FLEX_CONNECTIONS_PERCENT”的映射值从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexConnectionPercentRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex 警报配置]/metricThreshold”响应属性，鉴别器键“FLEX_NETWORK_BYTES_IN”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FlexNetworkBytesInDataMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性，鉴别器键“FLEX_NETWORK_BYTES_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FlexNetworkBytesOutDataMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性，鉴别器键“FLEX_NETWORK_NUM_REQUESTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexNetworkNumRequestsRawMetricThresholdView”
  • 对于“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性，鉴别器键“FLEX_OPCOUNTER_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterCMDRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex 警报配置]/metricThreshold”响应属性，鉴别器键“FLEX_OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterDeleteRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性，鉴别器键“FLEX_OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterGetMoreRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性，鉴别器键“FLEX_OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterInsertRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性，鉴别器键“FLEX_OPCOUNTER_QUERY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/FlexOpCounterQueryRawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterQueryRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性，鉴别器键“FLEX_OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterUpdateRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_AVG_COMMAND_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_AVG_WRITE_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_CONNECTIONS_PERCENT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessConnectionPercentageRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_NETWORK_BYTES_IN”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_NETWORK_BYTES_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_NETWORK_NUM_REQUESTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_OPCOUNTER_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_OPCOUNTER_QUERY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterUpdateRawMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_TOTAL_WRITE_UNITS”的映射值从“#/components/schemas/RPUMetricThresholdView”从“#/components/schemas/RPUMetricThresholdView”更改为“#/components/schemas/ServerlessTotalWriteUnitsRPUMetricThresholdView”
  • 针对“/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold”响应，鉴别器键“STREAM_PROCESSOR_DLQ_MESSAGE_COUNT”的映射值从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DLQRawMetricThresholdView”属性
  • 针对“/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold”响应，鉴别器键“STREAM_PROCESSOR_KAFKA_LAG”的映射值从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/KafkaRawMetricThresholdView”属性
  • 将 '#/components/schemas/KafkaRawMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/DLQRawMetricThresholdView, #/components/schemas/RawMetricThresholdView' 添加到 '/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold' 响应的响应属性'oneOf' 列表
  • 已添加 '#/components/schemas/RawMetricThresholdView, #/components/schemas/FlexConnectionPercentRawMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/components/schemas/FlexNetworkBytesInDataMetricThresholdView, #/components/schemas/FlexNetworkBytesOutDataMetricThresholdView, #/components/schemas/FlexNetworkNumRequestsRawMetricThresholdView, #/components/schemas/FlexOpCounterCMDRawMetricThresholdView, #/components/schemas/FlexOpCounterDeleteRawMetricThresholdView, #/components/schemas/FlexOpCounterInsertRawMetricThresholdView, #/components/schemas/FlexOpCounterQueryRawMetricThresholdView, #/components/schemas/FlexOpCounterUpdateRawMetricThresholdView, #/components/components/schemas/FlexOpCounterUpdateRawMetricThreshold components/schemas/TimeMetricThresholdView, #/components/schemas/FlexAVGWriteTimeMetricThresholdView, #/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView' 到 '/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold' res响应的 ponse属性“oneOf”列表
  • 添加了 '#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView, #/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/ServerlessTotalWriteUnitsRPUMetricThresholdView, #/components/schemas/RPUMetricThresholdView, #/components/schemas/RPUMetricViewerUpdateRaw,MetricView #/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView, #/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView, #/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView, #/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView, #/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView, #/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView, #/ components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView, #/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/compon ents/schemas/ServerlessConnectionPercentageRawMetricThresholdView, #/components/schemas/RawMetricThresholdView' 添加到响应的 '/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold' 响应属性'oneOf' 列表
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 已将“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性的鉴别器键“FLEX_AVG_COMMAND_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView”
  • 已将“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性的鉴别器键“FLEX_AVG_WRITE_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/FlexAVGWriteExecutionTimeMetricThresholdView”
  • 已将“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性的鉴别器键“FLEX_CONNECTIONS_PERCENT”的映射值从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexConnectionPercentRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex 警报配置]/metricThreshold”响应属性，鉴别器键“FLEX_NETWORK_BYTES_IN”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FlexNetworkBytesInDataMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性，鉴别器键“FLEX_NETWORK_BYTES_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FlexNetworkBytesOutDataMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性，鉴别器键“FLEX_NETWORK_NUM_REQUESTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexNetworkNumRequestsRawMetricThresholdView”
  • 对于“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性，鉴别器键“FLEX_OPCOUNTER_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterCMDRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex 警报配置]/metricThreshold”响应属性，鉴别器键“FLEX_OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterDeleteRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性，鉴别器键“FLEX_OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterGetMoreRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性，鉴别器键“FLEX_OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterInsertRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性，鉴别器键“FLEX_OPCOUNTER_QUERY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/FlexOpCounterQueryRawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterQueryRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性，鉴别器键“FLEX_OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterUpdateRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_AVG_COMMAND_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_AVG_WRITE_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_CONNECTIONS_PERCENT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessConnectionPercentageRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_NETWORK_BYTES_IN”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_NETWORK_BYTES_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_NETWORK_NUM_REQUESTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_OPCOUNTER_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_OPCOUNTER_QUERY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterUpdateRawMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_TOTAL_WRITE_UNITS”的映射值从“#/components/schemas/RPUMetricThresholdView”从“#/components/schemas/RPUMetricThresholdView”更改为“#/components/schemas/ServerlessTotalWriteUnitsRPUMetricThresholdView”
  • 针对“/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold”响应，鉴别器键“STREAM_PROCESSOR_DLQ_MESSAGE_COUNT”的映射值从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DLQRawMetricThresholdView”属性
  • 针对“/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold”响应，鉴别器键“STREAM_PROCESSOR_KAFKA_LAG”的映射值从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/KafkaRawMetricThresholdView”属性
  • 将 '#/components/schemas/KafkaRawMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/DLQRawMetricThresholdView, #/components/schemas/RawMetricThresholdView' 添加到 '/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold' 响应的响应属性'oneOf' 列表
  • 已添加 '#/components/schemas/RawMetricThresholdView, #/components/schemas/FlexConnectionPercentRawMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/components/schemas/FlexNetworkBytesInDataMetricThresholdView, #/components/schemas/FlexNetworkBytesOutDataMetricThresholdView, #/components/schemas/FlexNetworkNumRequestsRawMetricThresholdView, #/components/schemas/FlexOpCounterCMDRawMetricThresholdView, #/components/schemas/FlexOpCounterDeleteRawMetricThresholdView, #/components/schemas/FlexOpCounterInsertRawMetricThresholdView, #/components/schemas/FlexOpCounterQueryRawMetricThresholdView, #/components/schemas/FlexOpCounterUpdateRawMetricThresholdView, #/components/components/schemas/FlexOpCounterUpdateRawMetricThreshold components/schemas/TimeMetricThresholdView, #/components/schemas/FlexAVGWriteTimeMetricThresholdView, #/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView' 到 '/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold' res响应的 ponse属性“oneOf”列表
  • 添加了 '#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView, #/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/ServerlessTotalWriteUnitsRPUMetricThresholdView, #/components/schemas/RPUMetricThresholdView, #/components/schemas/RPUMetricViewerUpdateRaw,MetricView #/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView, #/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView, #/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView, #/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView, #/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView, #/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView, #/ components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView, #/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/compon ents/schemas/ServerlessConnectionPercentageRawMetricThresholdView, #/components/schemas/RawMetricThresholdView' 添加到响应的 '/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold' 响应属性'oneOf' 列表
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”请求属性，鉴别器键“FLEX_AVG_COMMAND_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”请求属性，鉴别器键“FLEX_AVG_WRITE_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/FlexAVGWriteExecutionTimeMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”请求属性，鉴别器键“FLEX_CONNECTIONS_PERCENT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexConnectionPercentRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”请求属性，鉴别器键“FLEX_NETWORK_BYTES_IN”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FlexNetworkBytesInDataMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”请求属性，鉴别器键“FLEX_NETWORK_BYTES_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FlexNetworkBytesOutDataMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”请求属性，鉴别器键“FLEX_NETWORK_NUM_REQUESTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexNetworkNumRequestsRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”请求属性，鉴别器键“FLEX_OPCOUNTER_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterCMDRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”请求属性，鉴别器键“FLEX_OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterDeleteRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”请求属性，鉴别器键“FLEX_OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterGetMoreRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”请求属性，鉴别器键“FLEX_OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterInsertRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”请求属性，鉴别器键“FLEX_OPCOUNTER_QUERY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterQueryRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”请求属性，鉴别器键“FLEX_OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterUpdateRawMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”请求属性，鉴别器键“SERVERLESS_AVG_COMMAND_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”请求属性，鉴别器键“SERVERLESS_AVG_WRITE_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”请求属性，鉴别器键“SERVERLESS_CONNECTIONS_PERCENT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessConnectionPercentageRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”请求属性，鉴别器键“SERVERLESS_NETWORK_BYTES_IN”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”请求属性，鉴别器键“SERVERLESS_NETWORK_BYTES_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”请求属性，鉴别器键“SERVERLESS_NETWORK_NUM_REQUESTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”请求属性，鉴别器键“SERVERLESS_OPCOUNTER_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”请求属性，鉴别器键“SERVERLESS_OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”请求属性，鉴别器键“SERVERLESS_OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”请求属性，鉴别器键“SERVERLESS_OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”请求属性，鉴别器键“SERVERLESS_OPCOUNTER_QUERY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”请求属性，鉴别器键“SERVERLESS_OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterUpdateRawMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”请求属性，鉴别器键“SERVERLESS_TOTAL_WRITE_UNITS”的映射值从“#/components/schemas/RPUMetricThresholdView”从“#/components/schemas/RPUMetricThresholdView”更改为“#/components/schemas/ServerlessTotalWriteUnitsRPUMetricThresholdView”
  • 针对“/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold”请求，鉴别器键“STREAM_PROCESSOR_DLQ_MESSAGE_COUNT”的映射值从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DLQRawMetricThresholdView”属性
  • 针对“/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold”请求，鉴别器键“STREAM_PROCESSOR_KAFKA_LAG”的映射值从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/KafkaRawMetricThresholdView”属性
  • 将 '#/components/schemas/KafkaRawMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/DLQRawMetricThresholdView, #/components/schemas/RawMetricThresholdView' 添加到 '/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold'请求属性'oneOf' 列表
  • 已添加 '#/components/schemas/RawMetricThresholdView, #/components/schemas/FlexConnectionPercentRawMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/components/schemas/FlexNetworkBytesInDataMetricThresholdView, #/components/schemas/FlexNetworkBytesOutDataMetricThresholdView, #/components/schemas/FlexNetworkNumRequestsRawMetricThresholdView, #/components/schemas/FlexOpCounterCMDRawMetricThresholdView, #/components/schemas/FlexOpCounterDeleteRawMetricThresholdView, #/components/schemas/FlexOpCounterInsertRawMetricThresholdView, #/components/schemas/FlexOpCounterQueryRawMetricThresholdView, #/components/schemas/FlexOpCounterUpdateRawMetricThresholdView, #/components/components/schemas/FlexOpCounterUpdateRawMetricThreshold components/schemas/TimeMetricThresholdView, #/components/schemas/FlexAVGWriteTimeMetricThresholdView, #/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView' 到 '/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold'请求属性'oneOf' 列表
  • 添加了 '#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView, #/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/ServerlessTotalWriteUnitsRPUMetricThresholdView, #/components/schemas/RPUMetricThresholdView, #/components/schemas/RPUMetricViewerUpdateRaw,MetricView #/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView, #/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView, #/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView, #/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView, #/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView, #/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView, #/ components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView, #/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/compon ents/schemas/ServerlessConnectionPercentageRawMetricThresholdView, #/components/schemas/RawMetricThresholdView' 到 '/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold'请求属性'oneOf' 列表
  • 已将“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性的鉴别器键“FLEX_AVG_COMMAND_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView”
  • 已将“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性的鉴别器键“FLEX_AVG_WRITE_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/FlexAVGWriteExecutionTimeMetricThresholdView”
  • 已将“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性的鉴别器键“FLEX_CONNECTIONS_PERCENT”的映射值从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexConnectionPercentRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex 警报配置]/metricThreshold”响应属性，鉴别器键“FLEX_NETWORK_BYTES_IN”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FlexNetworkBytesInDataMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性，鉴别器键“FLEX_NETWORK_BYTES_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FlexNetworkBytesOutDataMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性，鉴别器键“FLEX_NETWORK_NUM_REQUESTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexNetworkNumRequestsRawMetricThresholdView”
  • 对于“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性，鉴别器键“FLEX_OPCOUNTER_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterCMDRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex 警报配置]/metricThreshold”响应属性，鉴别器键“FLEX_OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterDeleteRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性，鉴别器键“FLEX_OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterGetMoreRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性，鉴别器键“FLEX_OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterInsertRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性，鉴别器键“FLEX_OPCOUNTER_QUERY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/FlexOpCounterQueryRawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterQueryRawMetricThresholdView”
  • 针对“/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”响应属性，鉴别器键“FLEX_OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterUpdateRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_AVG_COMMAND_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_AVG_WRITE_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_CONNECTIONS_PERCENT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessConnectionPercentageRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_NETWORK_BYTES_IN”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_NETWORK_BYTES_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_NETWORK_NUM_REQUESTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_OPCOUNTER_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView”
  • 针对“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_OPCOUNTER_QUERY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterUpdateRawMetricThresholdView”
  • 对于“/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”响应属性，鉴别器键“SERVERLESS_TOTAL_WRITE_UNITS”的映射值从“#/components/schemas/RPUMetricThresholdView”从“#/components/schemas/RPUMetricThresholdView”更改为“#/components/schemas/ServerlessTotalWriteUnitsRPUMetricThresholdView”
  • 针对“/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold”响应，鉴别器键“STREAM_PROCESSOR_DLQ_MESSAGE_COUNT”的映射值从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DLQRawMetricThresholdView”属性
  • 针对“/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold”响应，鉴别器键“STREAM_PROCESSOR_KAFKA_LAG”的映射值从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/KafkaRawMetricThresholdView”属性
  • 将 '#/components/schemas/KafkaRawMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/DLQRawMetricThresholdView, #/components/schemas/RawMetricThresholdView' 添加到 '/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold' 响应的响应属性'oneOf' 列表
  • 已添加 '#/components/schemas/RawMetricThresholdView, #/components/schemas/FlexConnectionPercentRawMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/components/schemas/FlexNetworkBytesInDataMetricThresholdView, #/components/schemas/FlexNetworkBytesOutDataMetricThresholdView, #/components/schemas/FlexNetworkNumRequestsRawMetricThresholdView, #/components/schemas/FlexOpCounterCMDRawMetricThresholdView, #/components/schemas/FlexOpCounterDeleteRawMetricThresholdView, #/components/schemas/FlexOpCounterInsertRawMetricThresholdView, #/components/schemas/FlexOpCounterQueryRawMetricThresholdView, #/components/schemas/FlexOpCounterUpdateRawMetricThresholdView, #/components/components/schemas/FlexOpCounterUpdateRawMetricThreshold components/schemas/TimeMetricThresholdView, #/components/schemas/FlexAVGWriteTimeMetricThresholdView, #/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView' 到 '/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold' res响应的 ponse属性“oneOf”列表
  • 添加了 '#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView, #/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/ServerlessTotalWriteUnitsRPUMetricThresholdView, #/components/schemas/RPUMetricThresholdView, #/components/schemas/RPUMetricViewerUpdateRaw,MetricView #/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView, #/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView, #/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView, #/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView, #/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView, #/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView, #/ components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView, #/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/compon ents/schemas/ServerlessConnectionPercentageRawMetricThresholdView, #/components/schemas/RawMetricThresholdView' 添加到响应的 '/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold' 响应属性'oneOf' 列表
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 对于“results/items/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”，鉴别器键“FLEX_AVG_COMMAND_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”，鉴别器键“FLEX_AVG_WRITE_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/FlexAVGWriteExecutionTimeMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”，鉴别器键“FLEX_CONNECTIONS_PERCENT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexConnectionPercentRawMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”，鉴别器键“FLEX_NETWORK_BYTES_IN”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FlexNetworkBytesInDataMetricThresholdView”响应属性
  • 针对“results/items/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”，鉴别器键“FLEX_NETWORK_BYTES_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/FlexNetworkBytesOutDataMetricThresholdView”响应属性
  • 针对“results/items/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”，鉴别器键“FLEX_NETWORK_NUM_REQUESTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexNetworkNumRequestsRawMetricThresholdView”响应属性
  • 针对“results/items/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”，鉴别器键“FLEX_OPCOUNTER_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterCMDRawMetricThresholdView”响应属性
  • 针对“results/items/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”，鉴别器键“FLEX_OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterDeleteRawMetricThresholdView”响应属性
  • 针对“results/items/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”，鉴别器键“FLEX_OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterGetMoreRawMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”，鉴别器键“FLEX_OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterInsertRawMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”，鉴别器键“FLEX_OPCOUNTER_QUERY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterQueryRawMetricThresholdView”响应属性
  • 针对“results/items/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold”，鉴别器键“FLEX_OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/FlexOpCounterUpdateRawMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”，鉴别器键“SERVERLESS_AVG_COMMAND_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”，鉴别器键“SERVERLESS_AVG_WRITE_EXECUTION_TIME”的映射值从“#/components/schemas/TimeMetricThresholdView”从“#/components/schemas/TimeMetricThresholdView”更改为“#/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”，鉴别器键“SERVERLESS_CONNECTIONS_PERCENT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessConnectionPercentageRawMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”，鉴别器键“SERVERLESS_NETWORK_BYTES_IN”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”，鉴别器键“SERVERLESS_NETWORK_BYTES_OUT”的映射值从“#/components/schemas/DataMetricThresholdView”从“#/components/schemas/DataMetricThresholdView”更改为“#/components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”，鉴别器键“SERVERLESS_NETWORK_NUM_REQUESTS”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”，鉴别器键“SERVERLESS_OPCOUNTER_CMD”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”，鉴别器键“SERVERLESS_OPCOUNTER_DELETE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”，鉴别器键“SERVERLESS_OPCOUNTER_GETMORE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”，鉴别器键“SERVERLESS_OPCOUNTER_INSERT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”，鉴别器键“SERVERLESS_OPCOUNTER_QUERY”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”，鉴别器键“SERVERLESS_OPCOUNTER_UPDATE”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/ServerlessOpCounterUpdateRawMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold”，鉴别器键“SERVERLESS_TOTAL_WRITE_UNITS”的映射值从“#/components/schemas/RPUMetricThresholdView”从“#/components/schemas/RPUMetricThresholdView”更改为“#/components/schemas/ServerlessTotalWriteUnitsRPUMetricThresholdView”响应属性
  • 对于“results/items/oneOf[subschema #16：流处理器指标警报配置]/”，鉴别器键“STREAM_PROCESSOR_DLQ_MESSAGE_COUNT”的映射值从“#/components/schemas/RawMetricThresholdView”从“#/components/schemas/RawMetricThresholdView”更改为“#/components/schemas/DLQRawMetricThresholdView”。阈值响应属性
  • 鉴别器键 'STREAM_PROCESSOR_KAFKA_LAG' 的映射值从 '#/components/schemas/RawMetricThresholdView' 更改为 'results/items/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/阈值响应属性
  • 将 '#/components/schemas/KafkaRawMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/DLQRawMetricThresholdView, #/components/schemas/RawMetricThresholdView' 添加到 'results/items/oneOf[subschema #16: Stream处理器指标警报配置]/threshold' 响应的响应属性'oneOf' 列表
  • 已添加 '#/components/schemas/RawMetricThresholdView, #/components/schemas/FlexConnectionPercentRawMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/components/schemas/FlexNetworkBytesInDataMetricThresholdView, #/components/schemas/FlexNetworkBytesOutDataMetricThresholdView, #/components/schemas/FlexNetworkNumRequestsRawMetricThresholdView, #/components/schemas/FlexOpCounterCMDRawMetricThresholdView, #/components/schemas/FlexOpCounterDeleteRawMetricThresholdView, #/components/schemas/FlexOpCounterInsertRawMetricThresholdView, #/components/schemas/FlexOpCounterQueryRawMetricThresholdView, #/components/schemas/FlexOpCounterUpdateRawMetricThresholdView, #/components/components/schemas/FlexOpCounterUpdateRawMetricThreshold components/schemas/TimeMetricThresholdView, #/components/schemas/FlexAVGWriteTimeMetricThresholdView, #/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView' 到 'results/items/oneOf[subschema #14: Flex Alert Configuration]/metricT href 响应的响应属性'oneOf' 列表
  • 添加了 '#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView, #/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/ServerlessTotalWriteUnitsRPUMetricThresholdView, #/components/schemas/RPUMetricThresholdView, #/components/schemas/RPUMetricViewerUpdateRaw,MetricView #/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView, #/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView, #/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView, #/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView, #/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView, #/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView, #/ components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView, #/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/compon ents/schemas/ServerlessConnectionPercentageRawMetricThresholdView, #/components/schemas/RawMetricThresholdView' 到该响应的 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold' 响应属性'oneOf' 列表

2025 年 7 月 16 日发布

POST /api/atlas/v2/groups
Updated
  • 请求可选属性“withDefaultAlertsSettings”变为非只写属性
GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将新的“MOGOT”枚举值添加到“results/items/oneOf[subschema #8: Host Alert Configuration]/matchers/items/value”响应属性
  • 将新的“MOGOT”枚举值添加到“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/matchers/items/value”响应属性
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将新的“MONGOT”枚举值添加到“/oneOf[subschema #8: Host Alert Configuration]/matchers/items/value”响应属性
  • 将新的“MONGOT”枚举值添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/matchers/items/value”响应属性
  • 已将新的“MONGOT”枚举值添加到请求属性“/oneOf[subschema #8: Host Alert Configuration]/matchers/items/value”
  • 已将新的“MONGOT”枚举值添加到请求属性“/oneOf[subschema #9: Host Metric Alert Configuration]/matchers/items/value”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将新的“MONGOT”枚举值添加到“/oneOf[subschema #8: Host Alert Configuration]/matchers/items/value”响应属性
  • 将新的“MONGOT”枚举值添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/matchers/items/value”响应属性
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将新的“MONGOT”枚举值添加到“/oneOf[subschema #8: Host Alert Configuration]/matchers/items/value”响应属性
  • 将新的“MONGOT”枚举值添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/matchers/items/value”响应属性
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将新的“MONGOT”枚举值添加到“/oneOf[subschema #8: Host Alert Configuration]/matchers/items/value”响应属性
  • 将新的“MONGOT”枚举值添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/matchers/items/value”响应属性
  • 已将新的“MONGOT”枚举值添加到请求属性“/oneOf[subschema #8: Host Alert Configuration]/matchers/items/value”
  • 已将新的“MONGOT”枚举值添加到请求属性“/oneOf[subschema #9: Host Metric Alert Configuration]/matchers/items/value”
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 将新的“MOGOT”枚举值添加到“results/items/oneOf[subschema #8: Host Alert Configuration]/matchers/items/value”响应属性
  • 将新的“MOGOT”枚举值添加到“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/matchers/items/value”响应属性
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 在“results/items/oneOf[subschema #15: NDS Audits]/eventTypeName”响应属性中添加了新的“MONGOTUNE_DISABLED、MONGOTUNE_ENABLED”枚举值
  • 在响应中添加了可选属性“results/items/oneOf[subschema #4: API User Events]/targetPublicKey、results/items/oneOf[subschema #4: API User Events]/whitelistEntry”
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 已将新的“MONGOTUNE_DISABLED、MONGOTUNE_ENABLED”枚举值添加到“/oneOf[subschema #15: NDS Audits]/eventTypeName”响应属性
  • 在响应中添加了可选属性“/oneOf[subschema #4: API User Events]/targetPublicKey, /oneOf[subschema #4: API User Events]/whitelistEntry”
GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在响应中添加了可选属性“results/items/connections/items/networking”
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在响应中添加了可选属性“connections/items/networking”
  • 添加了新的可选请求属性“connections/items/networking”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在响应中添加了可选属性“connections/items/networking”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在响应中添加了可选属性“connections/items/networking”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 在响应中添加了可选属性“results/items/networking”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 在响应中添加了可选属性“/networking”
  • 添加了新的可选请求属性“/networking”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 在响应中添加了可选属性“/networking”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 在响应中添加了可选属性“/networking”
  • 添加了新的可选请求属性“/networking”
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
Updated
  • 在响应中添加了可选属性“connections/items/networking”
POST /api/atlas/v2/orgs
Updated
  • 在响应中添加了可选属性“serviceAccount”
  • 添加了新的可选请求属性“serviceAccount”
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 在响应中添加了可选属性“results/items/oneOf[subschema #4: API User Events]/targetPublicKey、results/items/oneOf[subschema #4: API User Events]/whitelistEntry”
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 在响应中添加了可选属性“/oneOf[subschema #4: API User Events]/targetPublicKey, /oneOf[subschema #4: API User Events]/whitelistEntry”

2025 年 7 月 02 日发布

GET / API/ Atlas/v2/groups/{groupId}/clusters/{clusterName}/queryShapeInsights/summaries
已交
  • 已添加端点
GET / API/ Atlas/v2/groups/{groupId}/clusters/{clusterName}/queryShapeInsights/{queryShapeHash}/details
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/dataFederation
Updated
  • 已将新的“SAOPAULO_BRA, SEOUL_KOR”枚举值添加到“/items/dataProcessRegion/ 地区/”响应属性
POST /api/atlas/v2/groups/{groupId}/dataFederation
Updated
  • 在“dataProcessRegion/ 地区/”响应属性中添加了新的“SAOPAULO_BRA, SEOUL_KOR”枚举值
  • 已将新的“SAOPAULO_BRA, SEOUL_KOR”枚举值添加到请求属性“dataProcessRegion/ 地区/”
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 在“dataProcessRegion/ 地区/”响应属性中添加了新的“SAOPAULO_BRA, SEOUL_KOR”枚举值
PATCH /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 在“dataProcessRegion/ 地区/”响应属性中添加了新的“SAOPAULO_BRA, SEOUL_KOR”枚举值
  • 已将新的“SAOPAULO_BRA, SEOUL_KOR”枚举值添加到请求属性“dataProcessRegion/ 地区/”

2025 年 6 月 25 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #6: NDS Audit Types]/”响应属性中添加了新的“CLUSTER_BLOCK_WRITE、CLUSTER_UNBLOCK_WRITE”枚举值
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #6: NDS Audit Types]/”响应属性中添加了新的“CLUSTER_BLOCK_WRITE、CLUSTER_UNBLOCK_WRITE”枚举值
  • 已将新的“CLUSTER_BLOCK_WRITE、CLUSTER_UNBLOCK_WRITE”枚举值添加到请求属性“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #6: NDS Audit Types]/”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #6: NDS Audit Types]/”响应属性中添加了新的“CLUSTER_BLOCK_WRITE、CLUSTER_UNBLOCK_WRITE”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #6: NDS Audit Types]/”响应属性中添加了新的“CLUSTER_BLOCK_WRITE、CLUSTER_UNBLOCK_WRITE”枚举值
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #6: NDS Audit Types]/”响应属性中添加了新的“CLUSTER_BLOCK_WRITE、CLUSTER_UNBLOCK_WRITE”枚举值
  • 已将新的“CLUSTER_BLOCK_WRITE、CLUSTER_UNBLOCK_WRITE”枚举值添加到请求属性“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #6: NDS Audit Types]/”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 在“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #6: NDS Audit Types]/”响应属性中添加了新的“CLUSTER_BLOCK_WRITE、CLUSTER_UNBLOCK_WRITE”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 在“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #6: NDS Audit Types]/”响应属性中添加了新的“CLUSTER_BLOCK_WRITE、CLUSTER_UNBLOCK_WRITE”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 在“/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #6: NDS Audit Types]/”响应属性中添加了新的“CLUSTER_BLOCK_WRITE、CLUSTER_UNBLOCK_WRITE”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 在“/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #6: NDS Audit Types]/”响应属性中添加了新的“CLUSTER_BLOCK_WRITE、CLUSTER_UNBLOCK_WRITE”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 在“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #6: NDS Audit Types]/”响应属性中添加了新的“CLUSTER_BLOCK_WRITE、CLUSTER_UNBLOCK_WRITE”枚举值
GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 将新的 'ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL'枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/regionName /oneOf[subschema #2: Azure Regions]/' 响应属性
  • 已将新的 'ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL'枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/regionName/oneOf [subschema #2: Azure Regions]/' 响应属性
  • 已将新的 'ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL'枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/regionName/oneOf [subschema #2: Azure Regions]/' 响应属性
  • 已将新的 'ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL'枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional ReplicationSpecifications]/regionName/oneOf [subschema #2: Azure Regions]/' 响应属性
  • 在“results/items/replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #2: Azure Regions]/”响应属性中添加了新的“ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL”枚举值
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 枚举 ReplicationSpecifications]/regionName/oneOf[subschema #2: Azure Regions]/' 响应属性
  • 在 'replicationSpecs/items/ 枚举 /items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/regionName/oneOf[subschema #2： Azure区域]/' 响应属性
  • 已将新的 'ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/regionName/oneOf[subschema #2： Azure区域]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4 中添加了新的 'ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL'枚举值：租户区域复制规范]/regionName/oneOf[subschema #2： Azure区域]/' 响应属性
  • 在“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #2: Azure Regions]/”响应属性中添加了新的“ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL”枚举值
  • 已将新的 'ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/regionName/oneOf [subschema #2: Azure区域]/'
  • 在请求枚举'replicationSpecs/items/regionConfigs/items/oneOf[subschema2 # {属性} : Azure Regional ReplicationSpecifications]/regionName/oneOf[subschema2 #: Azure区域]/'
  • 在请求枚举'replicationSpecs/items/regionConfigs/items/oneOf[subschema3 #{GCP2 属性 ReplicationSpecifications]/regionName/oneOf[subschema #: Azure区域]/'
  • 在请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范] /regionName/oneOf[subschema #2: Azure区域]/'
  • 在请求属性'replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #2: Azure Regions]/' 中添加了新的 'ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL'枚举值
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 在“providerSettings/oneOf[subschema #2: Cloud Service Provider Settings for a Cluster]/regionName”响应属性中添加了新的“ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL”枚举值
  • 在请求属性“providerSettings/oneOf[subschema #2: Cloud Service Provider Settings for a Cluster]/regionName” （适用于集群的云服务提供商设置）中添加了新的“ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL”枚举值
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 枚举 ReplicationSpecifications]/regionName/oneOf[subschema #2: Azure Regions]/' 响应属性
  • 在 'replicationSpecs/items/ 枚举 /items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/regionName/oneOf[subschema #2： Azure区域]/' 响应属性
  • 已将新的 'ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/regionName/oneOf[subschema #2： Azure区域]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4 中添加了新的 'ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL'枚举值：租户区域复制规范]/regionName/oneOf[subschema #2： Azure区域]/' 响应属性
  • 在“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #2: Azure Regions]/”响应属性中添加了新的“ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL”枚举值
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 枚举 ReplicationSpecifications]/regionName/oneOf[subschema #2: Azure Regions]/' 响应属性
  • 在 'replicationSpecs/items/ 枚举 /items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/regionName/oneOf[subschema #2： Azure区域]/' 响应属性
  • 已将新的 'ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/regionName/oneOf[subschema #2： Azure区域]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4 中添加了新的 'ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL'枚举值：租户区域复制规范]/regionName/oneOf[subschema #2： Azure区域]/' 响应属性
  • 在“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #2: Azure Regions]/”响应属性中添加了新的“ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL”枚举值
  • 已将新的 'ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/regionName/oneOf [subschema #2: Azure区域]/'
  • 在请求枚举'replicationSpecs/items/regionConfigs/items/oneOf[subschema2 # {属性} : Azure Regional ReplicationSpecifications]/regionName/oneOf[subschema2 #: Azure区域]/'
  • 在请求枚举'replicationSpecs/items/regionConfigs/items/oneOf[subschema3 #{GCP2 属性 ReplicationSpecifications]/regionName/oneOf[subschema #: Azure区域]/'
  • 在请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范] /regionName/oneOf[subschema #2: Azure区域]/'
  • 在请求属性'replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #2: Azure Regions]/' 中添加了新的 'ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL'枚举值
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/index
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/performanceAdvisor/dropIndexSuggestions
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/performanceAdvisor/schemaAdvice
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/performanceAdvisor/suggestedIndexes
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/dbAccessHistory/clusters/{clusterName}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/dbAccessHistory/processes/{hostname}
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 在响应中添加了可选属性“googleCloudKms/roleId”
PATCH /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 在响应中添加了可选属性“googleCloudKms/roleId”
  • 添加了新的可选请求属性“googleCloudKms/roleId”
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
Updated
  • 已将新的“ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL”枚举值添加到“results/items/oneOf[subschema #1”： Azure Key Vault EAR Private Endpoint]/regionName/oneOf[subschema #1 : Azure Regions]/' 响应属性
  • 已将新的 'ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL'枚举值添加到 'results/items/oneOf[subschema #2: Amazon Web Services KMS EAR Private Endpoint]/regionName/oneOf[subschema #1: Azure Regions]/' 响应属性
  • 在“results/items/regionName/oneOf[subschema #1: Azure Regions]/”响应属性中添加了新的“ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL”枚举值
POST /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
Updated
  • 将新的 'ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL'枚举值添加到 '/oneOf[subschema #1: Azure Key Vault EAR Private Endpoint]/regionName/oneOf[subschema #1: Azure区域]/' 响应属性
  • 将新的 'ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL'枚举值添加到 '/oneOf[subschema #2: Amazon Web Services KMS EAR Private Endpoint]/regionName/oneOf[subschema #1: Azure Regions]/' 响应属性
  • 在“regionName/oneOf[subschema #1: Azure Regions]/”响应属性中添加了新的“ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL”枚举值
  • 在请求属性'/oneOf[subschema #1: Azure Key Vault 枚举 Private Endpoint]/regionName/oneOf[subschema #1: Azure区域]/'
  • 已将新的 'ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL'枚举值添加到请求属性'/oneOf[subschema #2: Amazon Web Services KMS EAR Private Endpoint]/regionName/oneOf[subschema #1 : Azure区域]/'
  • 已将新的“ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL”枚举值添加到请求属性“regionName/oneOf[subschema #1: Azure Regions]/”
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints/{endpointId}
Updated
  • 将新的 'ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL'枚举值添加到 '/oneOf[subschema #1: Azure Key Vault EAR Private Endpoint]/regionName/oneOf[subschema #1: Azure区域]/' 响应属性
  • 将新的 'ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL'枚举值添加到 '/oneOf[subschema #2: Amazon Web Services KMS EAR Private Endpoint]/regionName/oneOf[subschema #1: Azure Regions]/' 响应属性
  • 在“regionName/oneOf[subschema #1: Azure Regions]/”响应属性中添加了新的“ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL”枚举值
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 添加了状态为“ 429 ”的非成功响应
  • 在“results/items/oneOf[subschema #15: NDS Audits]/eventTypeName”响应属性中添加了新的“CLUSTER_BLOCK_WRITE、CLUSTER_UNBLOCK_WRITE、PROXY_PROTOCOL_FOR_PRIVATE_LINK_MODE_UPDATED”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 在 '/oneOf[subschema #15: NDS Audits]/eventTypeName' 响应属性中添加了新的 'CLUSTER_BLOCK_WRITE、CLUSTER_UNBLOCK_WRITE、PROXY_PROTOCOL_FOR_PRIVATE_LINK_MODE_UPDATED'枚举值
POST /api/atlas/v2/groups/{groupId}/flexClusters:tenantUpgrade
Updated
  • 已将新的 'ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/regionName/oneOf [subschema #2: Azure区域]/'
  • 在请求枚举'replicationSpecs/items/regionConfigs/items/oneOf[subschema2 # {属性} : Azure Regional ReplicationSpecifications]/regionName/oneOf[subschema2 #: Azure区域]/'
  • 在请求枚举'replicationSpecs/items/regionConfigs/items/oneOf[subschema3 #{GCP2 属性 ReplicationSpecifications]/regionName/oneOf[subschema #: Azure区域]/'
  • 在请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范] /regionName/oneOf[subschema #2: Azure区域]/'
  • 在请求属性'replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #2: Azure Regions]/' 中添加了新的 'ISRAEL_CENTRAL、ITALY_NORTH、MEXICO_CENTRAL、NEW_ZEALAND_NORTH、POLAND_CENTRAL、SPAIN_CENTRAL'枚举值
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics/indexes/{databaseName}/{collectionName}/measurements
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics/indexes/{databaseName}/{collectionName}/{indexName}/measurements
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics/measurements
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/managedSlowMs
Updated
  • 添加了状态为“ 429 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/managedSlowMs/disable
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/managedSlowMs/enable
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/performanceAdvisor/namespaces
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/performanceAdvisor/slowQueryLogs
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/performanceAdvisor/suggestedIndexes
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/performanceAdvisor/autoIndexing
Updated
  • 添加了状态为“ 429 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/performanceAdvisor/autoIndexing
Updated
  • 添加了状态为“ 429 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 将“AWSKinesisDataStreams”鉴别器映射键添加到“results/items/connections/items/”响应属性
  • 将“#/components/schemas/StreamsAWSKinesisDataStreamsConnection”添加到响应的“results/items/connections/items/”响应属性“oneOf”列表中
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 将“AWSKinesisDataStreams”鉴别器映射键添加到“connections/items/”请求属性
  • 将“#/components/schemas/StreamsAWSKinesisDataStreamsConnection”添加到“connections/items/”请求属性“oneOf”列表
  • 将“AWSKinesisDataStreams”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/schemas/StreamsAWSKinesisDataStreamsConnection”添加到了响应的“connections/items/”响应属性“oneOf”列表
  • 将新的“AWSKinesisDataStreams”枚举值添加到请求属性“connections/items/type”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 将“AWSKinesisDataStreams”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/schemas/StreamsAWSKinesisDataStreamsConnection”添加到了响应的“connections/items/”响应属性“oneOf”列表
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 将“AWSKinesisDataStreams”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/schemas/StreamsAWSKinesisDataStreamsConnection”添加到了响应的“connections/items/”响应属性“oneOf”列表
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 将“AWSKinesisDataStreams”鉴别器映射键添加到“results/items/”响应属性
  • 将“#/components/schemas/StreamsAWSKinesisDataStreamsConnection”添加到了响应的“results/items/”响应属性“oneOf”列表
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 将“AWSKinesisDataStreams”映射键添加到请求鉴别器
  • 将“#/components/schemas/StreamsAWSKinesisDataStreamsConnection”添加到请求正文“oneOf”列表
  • 已将“AWSKinesisDataStreams”映射键添加到响应状态“200”的响应鉴别器
  • 将“#/components/schemas/StreamsAWSKinesisDataStreamsConnection”添加到响应的响应正文“oneOf”列表中
  • 已将新的“AWSKinesisDataStreams”枚举值添加到请求属性“/type”
  • 已将新的“AWSKinesisDataStreams”枚举值添加到请求属性“type”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 已将“AWSKinesisDataStreams”映射键添加到响应状态“200”的响应鉴别器
  • 将“#/components/schemas/StreamsAWSKinesisDataStreamsConnection”添加到响应的响应正文“oneOf”列表中
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 将“AWSKinesisDataStreams”映射键添加到请求鉴别器
  • 将“#/components/schemas/StreamsAWSKinesisDataStreamsConnection”添加到请求正文“oneOf”列表
  • 已将“AWSKinesisDataStreams”映射键添加到响应状态“200”的响应鉴别器
  • 将“#/components/schemas/StreamsAWSKinesisDataStreamsConnection”添加到响应的响应正文“oneOf”列表中
  • 已将新的“AWSKinesisDataStreams”枚举值添加到请求属性“/type”
  • 已将新的“AWSKinesisDataStreams”枚举值添加到请求属性“type”
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
Updated
  • 将“AWSKinesisDataStreams”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/schemas/StreamsAWSKinesisDataStreamsConnection”添加到了响应的“connections/items/”响应属性“oneOf”列表
GET / API/ Atlas/v2/groups/{groupId}/teams/{teamId}
已交
  • 已添加端点
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 在“results/items/oneOf[subschema #8: Org Events]/eventTypeName”响应属性中添加了新的“CUSTOM_SESSION_TIMEOUT_MODIFIED、SANDBOX_DISABLED_FOR_ORG、SANDBOX_ENABLED_FOR_ORG”枚举值
  • Added the new 'VERCEL_INVOICE_CREATED, VERCEL_INVOICE_NOT_PAID, VERCEL_INVOICE_PAID, VERCEL_INVOICE_REFUNDED, VERCEL_SELF_SERVE_ACCOUNT_CANCELLED, VERCEL_SELF_SERVE_ACCOUNT_LINKED, VERCEL_SELF_SERVE_ACCOUNT_LINK_FAILED, VERCEL_SELF_SERVE_ACCOUNT_LINK_PENDING' 枚举 values to the 'results/items/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #4: Partner Event Types]/' 响应属性
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 在“/oneOf[subschema #8: Org Events]/eventTypeName”响应属性中添加了新的“CUSTOM_SESSION_TIMEOUT_MODIFIED、SANDBOX_DISABLED_FOR_ORG、SANDBOX_ENABLED_FOR_ORG”枚举值
  • Added the new 'VERCEL_INVOICE_CREATED, VERCEL_INVOICE_NOT_PAID, VERCEL_INVOICE_PAID, VERCEL_INVOICE_REFUNDED, VERCEL_SELF_SERVE_ACCOUNT_CANCELLED, VERCEL_SELF_SERVE_ACCOUNT_LINKED, VERCEL_SELF_SERVE_ACCOUNT_LINK_FAILED, VERCEL_SELF_SERVE_ACCOUNT_LINK_PENDING' 枚举 values to the '/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #4: Partner Event Types]/' 响应属性
GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • Added the new 'ATLAS_GCP_STREAM_PROCESSING_DATA_TRANSFER, ATLAS_GCP_STREAM_PROCESSING_INSTANCE_SP10, ATLAS_GCP_STREAM_PROCESSING_INSTANCE_SP30, ATLAS_GCP_STREAM_PROCESSING_INSTANCE_SP50, ATLAS_GCP_STREAM_PROCESSING_PRIVATELINK' 枚举 values to the 'results/items/lineItems/items/sku' response 属性
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
Updated
  • 将新的 'ATLAS_GCP_STREAM_PROCESSING_DATA_TRANSFER、ATLAS_GCP_STREAM_PROCESSING_INSTANCE_SP10、ATLAS_GCP_STREAM_PROCESSING_INSTANCE_SP30、ATLAS_GCP_STREAM_PROCESSING_INSTANCE_SP50、ATLAS_GCP_STREAM_PROCESSING_INSTANCE_SP、ATLAS_GCP_STREAM_PROCESSING_INSTANCE_SP、ATLAS_GCP_STREAM_STREAM_PROCESSING_INSTANCE_SP、ATLAS_GCP_STREAM_PROCESSING_INSTANCE_SP、ATLAS_GCP_STREAM_PROCESSING_INSTANCE_SP'枚举值添加到了 responseItems'msku/ 属性
PATCH /api/atlas/v2/orgs/{orgId}/settings
Updated
  • 添加了状态为“ 429 ”的非成功响应

2025 年 6 月 18 日发布

GET /api/atlas/v2/orgs/{orgId}/settings
Updated
  • 在响应中添加了可选属性“streamsCrossGroupEnabled”
PATCH /api/atlas/v2/orgs/{orgId}/settings
Updated
  • 在响应中添加了可选属性“streamsCrossGroupEnabled”
  • 添加了新的可选请求属性“streamsCrossGroupEnabled”

2025 年 6 月 17 日发布

GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在响应中添加了可选属性“results/items/connections/items/clusterGroupId”
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在响应中添加了可选属性“connections/items/clusterGroupId”
  • 添加了新的可选请求属性“connections/items/clusterGroupId”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在响应中添加了可选属性“connections/items/clusterGroupId”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在响应中添加了可选属性“connections/items/clusterGroupId”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 在响应中添加了可选属性“results/items/clusterGroupId”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 在响应中添加了可选属性“/clusterGroupId”
  • 添加了新的可选请求属性'/clusterGroupId'
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 在响应中添加了可选属性“/clusterGroupId”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 在响应中添加了可选属性“/clusterGroupId”
  • 添加了新的可选请求属性'/clusterGroupId'
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
Updated
  • 在响应中添加了可选属性“connections/items/clusterGroupId”

2025 年 6 月 04 日发布

GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 在“results/items/oneOf[subschema #15: NDS Audits]/eventTypeName”响应属性中添加了新的“ENCRYPTION_AT_REST_CONFIGURATION_VALIDATION_SUCCEEDED、STEP_SKIPPED”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 已将新的“ENCRYPTION_AT_REST_CONFIGURATION_VALIDATION_SUCCEEDED、STEP_SKIPPED”枚举值添加到“/oneOf[subschema #15: NDS Audits]/eventTypeName”响应属性
GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在响应中添加了可选属性“results/items/connections/items/networking/ 访问权限/tgwRouteId”
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在响应中添加了可选属性“connections/items/networking/ 访问权限/tgwRouteId”
  • 添加了新的可选请求属性“connections/items/networking/ 访问权限/tgwRouteId”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在响应中添加了可选属性“connections/items/networking/ 访问权限/tgwRouteId”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在响应中添加了可选属性“connections/items/networking/ 访问权限/tgwRouteId”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 在响应中添加了可选属性“results/items/networking/ 访问权限/tgwRouteId”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 在响应中添加了可选属性“/networking/ 访问权限/tgwRouteId”
  • 添加了新的可选请求属性“/networking/ 访问权限/tgwRouteId”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 在响应中添加了可选属性“/networking/ 访问权限/tgwRouteId”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 在响应中添加了可选属性“/networking/ 访问权限/tgwRouteId”
  • 添加了新的可选请求属性“/networking/ 访问权限/tgwRouteId”
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
Updated
  • 在响应中添加了可选属性“connections/items/networking/ 访问权限/tgwRouteId”
GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • 将新的 'ATLAS_NDS_GCP_SNAPSHOT_EXPORT_UPLOAD'枚举值添加到 'results/items/lineItems/items/sku' 响应属性
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
Updated
  • 在“lineItems/items/sku”响应属性中添加了新的“ATLAS_NDS_GCP_SNAPSHOT_EXPORT_UPLOAD”枚举值

20 5 月2025发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 将“#/components/schemas/ClusterAlertViewForNdsGroup”添加到响应的“results/items/”响应属性“oneOf”列表中
  • 已从响应的“results/items/”响应属性“oneOf”列表中删除“#/components/schemas/ClusterAlertView”
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 将“#/components/schemas/ClusterAlertViewForNdsGroup”添加到响应的“results/items/”响应属性“oneOf”列表中
  • 已从响应的“results/items/”响应属性“oneOf”列表中删除“#/components/schemas/ClusterAlertView”
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“#/components/schemas/ClusterAlertViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
  • 已从响应的响应正文“oneOf”列表中删除“#/components/schemas/ClusterAlertView”
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“#/components/schemas/ClusterAlertViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
  • 已从响应的响应正文“oneOf”列表中删除“#/components/schemas/ClusterAlertView”

08 5 月2025发布

GET /api/atlas/v2/groups/{groupId}/accessList
Updated
  • 更正端点包含Atlas内部条目的问题。
  • 更正端点包含Atlas内部条目的问题。
  • 更正端点包含Atlas内部条目的问题。
  • 更正端点包含Atlas内部条目的问题。
  • 更正端点包含Atlas内部条目的问题。
  • 更正端点包含Atlas内部条目的问题。
  • 更正端点包含Atlas内部条目的问题。
  • 更正端点包含Atlas内部条目的问题。
  • 更正端点包含Atlas内部条目的问题。
  • 更正端点包含Atlas内部条目的问题。
GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 添加了可选属性 'results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/severityOverride, results/items/oneOf[subschema #11: Replica Set Alert Configuration]/severityOverride, results/items/oneOf[subschema #12: 副本集阈值警报配置]/severityOverride, results/items/oneOf[subschema #13: Serverless 警报配置]/severityOverride, results/items/oneOf[subschema #14: Flex 警报配置]/severityOverride, results/items/oneOf[subschema #15: 流处理器警报配置]/severityOverride, results/items/oneOf[subschema #16: 流处理器指标警报配置]/severityOverride, Results/items/oneOf[subschema #1: Any other Alert Configurations]/severityOverride, results/items/oneOf[subschema #2: App Services Alert Configuration]/severityOverride, results/items/oneOf[subschema #3： App Services指标警报配置]/severityOverride, results/items/oneOf[subschema #4：账单阈值警报配置]/severityOverride, results/items/oneOf[subschema #5: 集群警报配置]/severityOverride, results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/severityOverride, results/items/ oneOf[subschema #7: Encryption Key Alert Configuration]/severityOverride, results/items/oneOf[subschema #8: Host Alert Configuration]/severityOverride, results/items/oneOf[subschema #9: Host Metric Alert Configuration]/severityOverride' 到响应
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 添加了可选属性 '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/severityOverride, /oneOf[subschema #11: 副本集警报配置]/severityOverride, /oneOf[subschema #12：副本集阈值警报配置]/severityOverride, /oneOf[subschema #13：无服务器警报配置]/severityOverride，/oneOf[subschema #14：Flex 警报配置]/severityOverride，/oneOf[subschema #15：流处理器警报配置]/severityOverride, /oneOf[subschema #16：流处理器指标警报配置]/severityOverride, /oneOf[subschema #1：任何其他警报配置]/severityOverride, /oneOf[subschema #2： App Services警报配置]/severityOverride，/oneOf[subschema #3： App Services指标警报配置]/severityOverride，/oneOf[subschema #4：账单阈值警报配置]/severityOverride，/oneOf [subschema #5: 集群警报配置]/severityOverride, /oneOf[subschema #6: Cps 返回up 阈值警报配置]/severityOverride, /oneOf[subschema #7: 加密密钥警报配置]/severityOverride, /oneOf[subschema #8: 主机警报配置]/severityOverride, /oneOf[subschema #9: Host Metric Alert Configuration]/severityOverride' 到响应
  • 添加了新的可选请求属性 '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/severityOverride、/oneOf[subschema #11：副本集警报配置]/severityOverride、/oneOf[subschema #12：副本集阈值警报配置]/severityOverride，/oneOf[subschema #13：无服务器警报配置]/severityOverride，/oneOf[subschema #14：Flex 警报配置]/severityOverride，/oneOf[subschema #15：流处理器警报配置]/severityOverride，/oneOf[subschema #16：流处理器指标警报配置]/severityOverride，/oneOf[subschema #1：任何其他警报配置]/severityOverride，/oneOf[subschema #2： App Services警报配置]/severityOverride、/oneOf[subschema #3： App Services指标警报配置]/severityOverride、/oneOf[subschema #4：账单阈值警报配置]/severityOverride、 /oneOf[subschema #5: 集群警报配置]/severityOverride, /oneOf[subschema #6：Cps 备份阈值警报配置]/severityOverride, /oneOf[subschema #7：加密密钥警报配置]/severityOverride, /oneOf[subschema #8：主机警报配置]/severityOverride, /oneOf[subschema #9：主机指标警报配置]/severityOverride'
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 添加了可选属性 '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/severityOverride, /oneOf[subschema #11: 副本集警报配置]/severityOverride, /oneOf[subschema #12：副本集阈值警报配置]/severityOverride, /oneOf[subschema #13：无服务器警报配置]/severityOverride，/oneOf[subschema #14：Flex 警报配置]/severityOverride，/oneOf[subschema #15：流处理器警报配置]/severityOverride, /oneOf[subschema #16：流处理器指标警报配置]/severityOverride, /oneOf[subschema #1：任何其他警报配置]/severityOverride, /oneOf[subschema #2： App Services警报配置]/severityOverride，/oneOf[subschema #3： App Services指标警报配置]/severityOverride，/oneOf[subschema #4：账单阈值警报配置]/severityOverride，/oneOf [subschema #5: 集群警报配置]/severityOverride, /oneOf[subschema #6: Cps 返回up 阈值警报配置]/severityOverride, /oneOf[subschema #7: 加密密钥警报配置]/severityOverride, /oneOf[subschema #8: 主机警报配置]/severityOverride, /oneOf[subschema #9: Host Metric Alert Configuration]/severityOverride' 到响应
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 添加了可选属性 '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/severityOverride, /oneOf[subschema #11: 副本集警报配置]/severityOverride, /oneOf[subschema #12：副本集阈值警报配置]/severityOverride, /oneOf[subschema #13：无服务器警报配置]/severityOverride，/oneOf[subschema #14：Flex 警报配置]/severityOverride，/oneOf[subschema #15：流处理器警报配置]/severityOverride, /oneOf[subschema #16：流处理器指标警报配置]/severityOverride, /oneOf[subschema #1：任何其他警报配置]/severityOverride, /oneOf[subschema #2： App Services警报配置]/severityOverride，/oneOf[subschema #3： App Services指标警报配置]/severityOverride，/oneOf[subschema #4：账单阈值警报配置]/severityOverride，/oneOf [subschema #5: 集群警报配置]/severityOverride, /oneOf[subschema #6: Cps 返回up 阈值警报配置]/severityOverride, /oneOf[subschema #7: 加密密钥警报配置]/severityOverride, /oneOf[subschema #8: 主机警报配置]/severityOverride, /oneOf[subschema #9: Host Metric Alert Configuration]/severityOverride' 到响应
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 添加了可选属性 '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/severityOverride, /oneOf[subschema #11: 副本集警报配置]/severityOverride, /oneOf[subschema #12：副本集阈值警报配置]/severityOverride, /oneOf[subschema #13：无服务器警报配置]/severityOverride，/oneOf[subschema #14：Flex 警报配置]/severityOverride，/oneOf[subschema #15：流处理器警报配置]/severityOverride, /oneOf[subschema #16：流处理器指标警报配置]/severityOverride, /oneOf[subschema #1：任何其他警报配置]/severityOverride, /oneOf[subschema #2： App Services警报配置]/severityOverride，/oneOf[subschema #3： App Services指标警报配置]/severityOverride，/oneOf[subschema #4：账单阈值警报配置]/severityOverride，/oneOf [subschema #5: 集群警报配置]/severityOverride, /oneOf[subschema #6: Cps 返回up 阈值警报配置]/severityOverride, /oneOf[subschema #7: 加密密钥警报配置]/severityOverride, /oneOf[subschema #8: 主机警报配置]/severityOverride, /oneOf[subschema #9: Host Metric Alert Configuration]/severityOverride' 到响应
  • 添加了新的可选请求属性 '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/severityOverride、/oneOf[subschema #11：副本集警报配置]/severityOverride、/oneOf[subschema #12：副本集阈值警报配置]/severityOverride，/oneOf[subschema #13：无服务器警报配置]/severityOverride，/oneOf[subschema #14：Flex 警报配置]/severityOverride，/oneOf[subschema #15：流处理器警报配置]/severityOverride，/oneOf[subschema #16：流处理器指标警报配置]/severityOverride，/oneOf[subschema #1：任何其他警报配置]/severityOverride，/oneOf[subschema #2： App Services警报配置]/severityOverride、/oneOf[subschema #3： App Services指标警报配置]/severityOverride、/oneOf[subschema #4：账单阈值警报配置]/severityOverride、 /oneOf[subschema #5: 集群警报配置]/severityOverride, /oneOf[subschema #6：Cps 备份阈值警报配置]/severityOverride, /oneOf[subschema #7：加密密钥警报配置]/severityOverride, /oneOf[subschema #8：主机警报配置]/severityOverride, /oneOf[subschema #9：主机指标警报配置]/severityOverride'
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 添加了可选属性 'results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/severityOverride, results/items/oneOf[subschema #11: Replica Set Alert Configuration]/severityOverride, results/items/oneOf[subschema #12: 副本集阈值警报配置]/severityOverride, results/items/oneOf[subschema #13: Serverless 警报配置]/severityOverride, results/items/oneOf[subschema #14: Flex 警报配置]/severityOverride, results/items/oneOf[subschema #15: 流处理器警报配置]/severityOverride, results/items/oneOf[subschema #16: 流处理器指标警报配置]/severityOverride, Results/items/oneOf[subschema #1: Any other Alert Configurations]/severityOverride, results/items/oneOf[subschema #2: App Services Alert Configuration]/severityOverride, results/items/oneOf[subschema #3： App Services指标警报配置]/severityOverride, results/items/oneOf[subschema #4：账单阈值警报配置]/severityOverride, results/items/oneOf[subschema #5: 集群警报配置]/severityOverride, results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/severityOverride, results/items/ oneOf[subschema #7: Encryption Key Alert Configuration]/severityOverride, results/items/oneOf[subschema #8: Host Alert Configuration]/severityOverride, results/items/oneOf[subschema #9: Host Metric Alert Configuration]/severityOverride' 到响应
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/performanceAdvisor/slowQueryLogs
Updated
  • 添加了新的可选“查询”请求参数“includeMetrics”
  • 添加了新的可选“查询”请求参数“includeOpType”
  • 添加了新的可选“查询”请求参数“includeReplicaState”
  • 在响应中添加了可选属性“slowQueries/items/ 指标、slowQueries/items/opType、slowQueries/items/replicaState”
POST / API/ Atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}:startWith
已交
  • 已添加端点
GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • Added the new 'ATLAS_FLEX_AWS_LEGACY_100_USAGE_HOURS, ATLAS_FLEX_AWS_LEGACY_200_USAGE_HOURS, ATLAS_FLEX_AWS_LEGACY_300_USAGE_HOURS, ATLAS_FLEX_AWS_LEGACY_400_USAGE_HOURS, ATLAS_FLEX_AWS_LEGACY_500_USAGE_HOURS, ATLAS_FLEX_AZURE_LEGACY_100_USAGE_HOURS, ATLAS_FLEX_AZURE_LEGACY_200_USAGE_HOURS, ATLAS_FLEX_AZURE_LEGACY_300 _USAGE_HOURS, ATLAS_FLEX_AZURE_LEGACY_400_USAGE_HOURS, ATLAS_FLEX_AZURE_LEGACY_500_USAGE_HOURS, ATLAS_FLEX_GCP_LEGACY_100_USAGE_HOURS, ATLAS_FLEX_GCP_LEGACY_200_USAGE_HOURS, ATLAS_FLEX_GCP_LEGACY_300_USAGE_HOURS, ATLAS_FLEX_GCP_LEGACY_400_USAGE_HOURS, ATLAS_FLEX_GCP_LEGACY_500_USAGE_HOURS' 枚举 values to the 'results /items/lineItems/items/sku' 响应属性
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
Updated
  • Added the new 'ATLAS_FLEX_AWS_LEGACY_100_USAGE_HOURS, ATLAS_FLEX_AWS_LEGACY_200_USAGE_HOURS, ATLAS_FLEX_AWS_LEGACY_300_USAGE_HOURS, ATLAS_FLEX_AWS_LEGACY_400_USAGE_HOURS, ATLAS_FLEX_AWS_LEGACY_500_USAGE_HOURS, ATLAS_FLEX_AZURE_LEGACY_100_USAGE_HOURS, ATLAS_FLEX_AZURE_LEGACY_200_USAGE_HOURS, ATLAS_FLEX_AZURE_LEGACY_300_USAGE_HOURS, ATLAS_FLEX_AZURE_LEGACY_400_USAGE_HOURS, ATLAS_FLEX_AZURE_LEGACY_500_USAGE_HOURS, ATLAS_FLEX_GCP_LEGACY_100_USAGE_HOURS, ATLAS_FLEX_GCP_LEGACY_200_USAGE_HOURS, ATLAS_FLEX_GCP_LEGACY_300_USAGE_HOURS, ATLAS_FLEX_GCP_LEGACY_400_USAGE_HOURS, ATLAS_FLEX_GCP_LEGACY_500_USAGE_HOURS' enum values to the 'lineItems/items/sku' response property

2025 年 4 月 23 日发布

GET /api/atlas/v2
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/alertConfigs/matchers/fieldNames
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/clusters
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/eventTypes
Updated
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs
Updated
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
Updated
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings
Updated
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings
Updated
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings/{id}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings/{id}
Updated
  • 添加了状态为“403”的不成功响应
PUT /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings/{id}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders
Updated
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}/jwks
Updated
  • 添加了状态为“ 401 ”的非成功响应
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}/metadata.xml
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/byName/{groupName}
Updated
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/access
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/accessList
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
POST /api/atlas/v2/groups/{groupId}/accessList
Updated
  • 添加了状态为“404”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/accessList/{entryValue}
Updated
  • 添加了状态为“ 401 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 添加了状态为“403”的不成功响应
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/apiKeys
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
POST /api/atlas/v2/groups/{groupId}/apiKeys
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
Updated
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
POST /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/auditLog
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/auditLog
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/awsCustomDNS
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/awsCustomDNS
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/backup/exportBuckets
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
  • 将“GCP”鉴别器映射键添加到“results/items/”响应属性
  • 将新的“GCP”枚举值添加到“results/items/cloudProvider”响应属性中
POST /api/atlas/v2/groups/{groupId}/backup/exportBuckets
Updated
  • 将“GCP”映射键添加到请求鉴别器
  • 已将“GCP”映射键添加到响应状态“200”的响应鉴别器
  • 添加了状态为“403”的不成功响应
  • 已将新的“GCP”枚举值添加到“cloudProvider”响应属性中
  • 已将新的“GCP”枚举值添加到请求属性“cloudProvider”中
DELETE /api/atlas/v2/groups/{groupId}/backup/exportBuckets/{exportBucketId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/backup/exportBuckets/{exportBucketId}
Updated
  • 已将“GCP”映射键添加到响应状态“200”的响应鉴别器
  • 添加了状态为“403”的不成功响应
  • 已将新的“GCP”枚举值添加到“cloudProvider”响应属性中
DELETE /api/atlas/v2/groups/{groupId}/backupCompliancePolicy
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/backupCompliancePolicy
Updated
  • 添加了状态为“403”的不成功响应
PUT /api/atlas/v2/groups/{groupId}/backupCompliancePolicy
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/cloudProviderAccess
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/cloudProviderAccess
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/cloudProviderAccess/{cloudProvider}/{roleId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/cloudProviderAccess/{roleId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/cloudProviderAccess/{roleId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/provider/regions
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 添加了状态为“404”的不成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgradeToServerless
Updated
  • 添加了状态为“404”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 添加了状态为“403”的不成功响应
GET / API/ Atlas/v2/groups/{groupId}/clusters/{clusterName}/autoScalingConfiguration
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports
Updated
  • 添加了状态为“ 401 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports/{exportId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs
Updated
  • 添加了状态为“ 401 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs/{restoreJobId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs/{restoreJobId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/shardedCluster/{snapshotId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/shardedCluster/{snapshotId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/shardedClusters
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/restore
Updated
  • 添加了状态为“ 401 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/restores
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/restores/{restoreId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/snapshots
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/snapshots/{snapshotId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backupCheckpoints
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backupCheckpoints/{checkpointId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • 添加了状态为“ 401 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • 添加了状态为“ 401 ”的非成功响应
PUT /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • 添加了状态为“ 401 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/unpin
Updated
  • 添加了状态为“ 401 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{databaseName}/{collectionName}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/customZoneMapping
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/customZoneMapping
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/managedNamespaces
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/managedNamespaces
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/index
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/queryLogs.gz
Updated
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/outageSimulation
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/outageSimulation
Updated
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/outageSimulation
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/performanceAdvisor/dropIndexSuggestions
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/performanceAdvisor/schemaAdvice
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/performanceAdvisor/suggestedIndexes
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restartPrimaries
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs/{jobId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshotSchedule
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshotSchedule
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots/{snapshotId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots/{snapshotId}
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots/{snapshotId}
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/status
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/{clusterView}/collStats/namespaces
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/{clusterView}/{databaseName}/{collectionName}/collStats/measurements
Updated
  • 添加了状态为“ 401 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}:grantMongoDBEmployeeAccess
Updated
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}:pinFeatureCompatibilityVersion
Updated
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}:revokeMongoDBEmployeeAccess
Updated
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}:unpinFeatureCompatibilityVersion
Updated
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/collStats/metrics
Updated
  • 添加了状态为“ 401 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/containers
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/containers/all
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
  • 在“/items/actions/items/ 动作”响应属性中添加了新的“CLEAR_JUMBO_FLAG、KIL_ANY_CURSOR、REFINE_COLLECTION_SHARD_KEY、RESHARD_COLLECTION、SHARDED_DATA_DISTRIBUTION”枚举值
POST /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 在“actions/items/ 动作”响应属性中添加了新的“CLEAR_JUMBO_FLAG、KIL_ANY_CURSOR、REFINE_COLLECTION_SHARD_KEY、RESHARD_COLLECTION、SHARDED_DATA_DISTRIBUTION”枚举值
  • 在请求属性“actions/items/ 动作 ”中添加了新的“CLEAR_JUMBO_FLAG、KIL_ANY_CURSOR、REFINE_COLLECTION_SHARD_KEY、RESHARD_COLLECTION、SHARDED_DATA_DISTRIBUTION”枚举值
DELETE /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 添加了状态为“403”的不成功响应
  • 在“actions/items/ 动作”响应属性中添加了新的“CLEAR_JUMBO_FLAG、KIL_ANY_CURSOR、REFINE_COLLECTION_SHARD_KEY、RESHARD_COLLECTION、SHARDED_DATA_DISTRIBUTION”枚举值
PATCH /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 在“actions/items/ 动作”响应属性中添加了新的“CLEAR_JUMBO_FLAG、KIL_ANY_CURSOR、REFINE_COLLECTION_SHARD_KEY、RESHARD_COLLECTION、SHARDED_DATA_DISTRIBUTION”枚举值
  • 在请求属性“actions/items/ 动作 ”中添加了新的“CLEAR_JUMBO_FLAG、KIL_ANY_CURSOR、REFINE_COLLECTION_SHARD_KEY、RESHARD_COLLECTION、SHARDED_DATA_DISTRIBUTION”枚举值
GET /api/atlas/v2/groups/{groupId}/dataFederation
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
POST /api/atlas/v2/groups/{groupId}/dataFederation
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/limits
Updated
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/limits/{limitName}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/limits/{limitName}
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/limits/{limitName}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/databaseUsers
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/databaseUsers/{databaseName}/{username}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/databaseUsers/{username}/certs
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/dbAccessHistory/clusters/{clusterName}
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/dbAccessHistory/processes/{hostname}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 添加了状态为“ 401 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“404”的不成功响应
POST /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“404”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints/{endpointId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints/{endpointId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
  • Added the new 'AUTO_HEALING_CANNOT_REPAIR_INTERNAL, AUTO_HEALING_CANNOT_RESYNC_INTERNAL, AUTO_HEALING_REQUESTED_CRITICAL_INSTANCE_POWER_CYCLE, AUTO_HEALING_REQUESTED_INSTANCE_REPLACEMENT, AUTO_HEALING_REQUESTED_NODE_RESYNC, FTDC_SETTINGS_UPDATED' 枚举 values to the 'results/items/oneOf[subschema #15: NDS Audits]/eventTypeName' response 属性
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 添加了状态为“403”的不成功响应
  • Added the new 'AUTO_HEALING_CANNOT_REPAIR_INTERNAL, AUTO_HEALING_CANNOT_RESYNC_INTERNAL, AUTO_HEALING_REQUESTED_CRITICAL_INSTANCE_POWER_CYCLE, AUTO_HEALING_REQUESTED_INSTANCE_REPLACEMENT, AUTO_HEALING_REQUESTED_NODE_RESYNC, FTDC_SETTINGS_UPDATED' 枚举 values to the '/oneOf[subschema #15: NDS Audits]/eventTypeName' response 属性
GET /api/atlas/v2/groups/{groupId}/flexClusters
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
POST /api/atlas/v2/groups/{groupId}/flexClusters
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/flexClusters/{name}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/flexClusters/{name}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/restoreJobs
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/restoreJobs
Updated
  • 添加了状态为“ 401 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/restoreJobs/{restoreJobId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/snapshots
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/snapshots/{snapshotId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/flexClusters:tenantUpgrade
Updated
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics/indexes/{databaseName}/{collectionName}/measurements
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics/indexes/{databaseName}/{collectionName}/{indexName}/measurements
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics/measurements
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/integrations
Updated
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 添加了状态为“403”的不成功响应
PUT /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/invites
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/invites
Updated
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/invites
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/invites/{invitationId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/invites/{invitationId}
Updated
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/invites/{invitationId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/ipAddresses
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/limits
Updated
  • 添加了状态为“403”的不成功响应
  • 已删除“dataFederation.bytesProcessed”。查询，dataFederation.bytesProcessed.weekly,dataFederation.bytesProcessed.daily,dataFederation.bytesProcessed.monthly'鉴别器映射来自 '/items/' 响应属性的键
DELETE /api/atlas/v2/groups/{groupId}/limits/{limitName}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/limits/{limitName}
Updated
  • 删除了 'dataFederation.bytesProcessed.monthly,dataFederation.bytesProcessed。查询，dataFederation.bytesProcessed.weekly,dataFederation.bytesProcessed.daily'将来自响应鉴别器的键映射到响应状态“200”
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/limits/{limitName}
Updated
  • 删除了 'dataFederation.bytesProcessed.weekly,dataFederation.bytesProcessed.daily,dataFederation.bytesProcessed.monthly,dataFederation.bytesProcessed。 查询'从请求鉴别器映射键
  • 已删除“dataFederation.bytesProcessed”。查询，dataFederation.bytesProcessed.weekly,dataFederation.bytesProcessed.daily,dataFederation.bytesProcessed.monthly'将来自响应鉴别器的键映射到响应状态“200”
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/maintenanceWindow
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/maintenanceWindow
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/maintenanceWindow
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/maintenanceWindow/autoDefer
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/maintenanceWindow/defer
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/managedSlowMs
Updated
  • 添加了状态为“404”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/managedSlowMs/disable
Updated
  • 添加了状态为“404”的不成功响应
POST /api/atlas/v2/groups/{groupId}/managedSlowMs/enable
Updated
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/peers
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/peers
Updated
  • 添加了状态为“ 401 ”的非成功响应
DELETE /api/atlas/v2/groups/{groupId}/peers/{peerId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/peers/{peerId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/peers/{peerId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/pipelines
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/pipelines
Updated
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/availableSchedules
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/availableSnapshots
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/pause
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/resume
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/runs
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/runs/{pipelineRunId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/runs/{pipelineRunId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/trigger
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/privateEndpoint/endpointService
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/regionalMode
Updated
  • 添加了状态为“ 401 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/privateEndpoint/regionalMode
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint/{endpointId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint/{endpointId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint/{endpointId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}/endpoint
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}/endpoint/{endpointId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}/endpoint/{endpointId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/privateIpMode
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/privateIpMode
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds
Updated
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds/{endpointId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds/{endpointId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/processes
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/processes/{processId}
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/collStats/namespaces
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/databases
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/databases/{databaseName}
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/databases/{databaseName}/measurements
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/disks
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/disks/{partitionName}
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/disks/{partitionName}/measurements
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/measurements
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/performanceAdvisor/namespaces
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/performanceAdvisor/slowQueryLogs
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/performanceAdvisor/suggestedIndexes
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/{databaseName}/{collectionName}/collStats/measurements
Updated
  • 添加了状态为“ 401 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/sampleDatasetLoad/{name}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/sampleDatasetLoad/{sampleDatasetId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/serverless
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
POST /api/atlas/v2/groups/{groupId}/serverless
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/restoreJobs
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/restoreJobs
Updated
  • 添加了状态为“ 401 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/restoreJobs/{restoreJobId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/snapshots
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/performanceAdvisor/autoIndexing
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
POST /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/performanceAdvisor/autoIndexing
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/serverless/{name}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/serverless/{name}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/serverless/{name}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/serviceAccounts
Updated
  • 添加了状态为“404”的不成功响应
POST /api/atlas/v2/groups/{groupId}/serviceAccounts
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
Updated
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/accessList
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
POST /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/accessList
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/accessList/{ipAddress}
Updated
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/secrets
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/secrets/{secretId}
Updated
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}:invite
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
  • 已将新的 'TRANSIT_GATEWAY'枚举值添加到 'results/items/connections/items/networking/ 访问权限/type' 响应属性
  • 在响应中添加了可选属性“results/items/connections/items/networking/ 访问权限/tgwId、results/items/connections/items/networking/ 访问权限/vpcCIDR”
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
  • 将新的“TRANSIT_GATEWAY”枚举值添加到“connections/items/networking/ 访问权限/type”响应属性中
  • 已将新的“TRANSIT_GATEWAY”枚举值添加到请求属性“connections/items/networking/ 访问权限/type”
  • 在响应中添加了可选属性“connections/items/networking/ 访问权限/tgwId、connections/items/networking/ 访问权限/vpcCIDR”
  • 添加了新的可选请求属性“connections/items/networking/ 访问权限/tgwId、connections/items/networking/ 访问权限/vpcCIDR”
GET /api/atlas/v2/groups/{groupId}/streams/accountDetails
Updated
  • 为响应状态“200”添加了响应鉴别器
  • 将“#/components/schemas/AWSAccountDetails, #/components/schemas/AzureAccountDetails”添加到响应的响应正文“oneOf”列表中
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/streams/activeVpcPeeringConnections
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections
Updated
  • 添加了状态为“403”的不成功响应
  • 已添加“results/items/arn”响应的属性模式“^arn:aws:kafka”
  • 在响应中添加了可选属性“results/items/azureResourceIds”
  • 响应属性“results/items/ 提供商”变为必填项
POST /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
  • 已添加“arn”响应的属性模式“^arn:aws:kafka”
  • 在响应中添加了可选属性“azureResourceIds”
  • 响应属性“提供商”变为必需
  • 添加了新的可选请求属性“azureResourceIds”
GET /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections/{connectionId}
Updated
  • 添加了状态为“403”的不成功响应
  • 已添加“arn”响应的属性模式“^arn:aws:kafka”
  • 在响应中添加了可选属性“azureResourceIds”
  • 响应属性“提供商”变为必需
GET /api/atlas/v2/groups/{groupId}/streams/vpcPeeringConnections
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 添加了状态为“403”的不成功响应
  • 将新的“TRANSIT_GATEWAY”枚举值添加到“connections/items/networking/ 访问权限/type”响应属性中
  • 在响应中添加了可选属性“connections/items/networking/ 访问权限/tgwId、connections/items/networking/ 访问权限/vpcCIDR”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 将新的“TRANSIT_GATEWAY”枚举值添加到“connections/items/networking/ 访问权限/type”响应属性中
  • 在响应中添加了可选属性“connections/items/networking/ 访问权限/tgwId、connections/items/networking/ 访问权限/vpcCIDR”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 添加了状态为“403”的不成功响应
  • 将新的“TRANSIT_GATEWAY”枚举值添加到“results/items/networking/ 访问权限/type”响应属性中
  • 在响应中添加了可选属性“results/items/networking/ 访问权限/tgwId、results/items/networking/ 访问权限/vpcCIDR”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
  • 在“/networking/ 访问权限/type”响应属性中添加了新的“TRANSIT_GATEWAY”枚举值
  • 已将新的“TRANSIT_GATEWAY”枚举值添加到请求属性“/networking/ 访问权限/type”
  • 在响应中添加了可选属性“/networking/ 访问权限/tgwId, /networking/ 访问权限/vpcCIDR”
  • 添加了新的可选请求属性“/networking/ 访问权限/tgwId、/networking/ 访问权限/vpcCIDR”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 添加了状态为“403”的不成功响应
  • 在“/networking/ 访问权限/type”响应属性中添加了新的“TRANSIT_GATEWAY”枚举值
  • 在响应中添加了可选属性“/networking/ 访问权限/tgwId, /networking/ 访问权限/vpcCIDR”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 在“/networking/ 访问权限/type”响应属性中添加了新的“TRANSIT_GATEWAY”枚举值
  • 已将新的“TRANSIT_GATEWAY”枚举值添加到请求属性“/networking/ 访问权限/type”
  • 在响应中添加了可选属性“/networking/ 访问权限/tgwId, /networking/ 访问权限/vpcCIDR”
  • 添加了新的可选请求属性“/networking/ 访问权限/tgwId、/networking/ 访问权限/vpcCIDR”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processors
Updated
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
  • 将新的“TRANSIT_GATEWAY”枚举值添加到“connections/items/networking/ 访问权限/type”响应属性中
  • 在响应中添加了可选属性“connections/items/networking/ 访问权限/tgwId、connections/items/networking/ 访问权限/vpcCIDR”
GET /api/atlas/v2/groups/{groupId}/userSecurity
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/groups/{groupId}/userSecurity
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/userSecurity/customerX509
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/userSecurity/ldap/userToDNMapping
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/groups/{groupId}/userSecurity/ldap/verify
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/userSecurity/ldap/verify/{requestId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/groups/{groupId}/users
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/users/{userId}
Updated
  • 添加了状态为“ 401 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}:migrate
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/orgs
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/orgs/{orgId}
Updated
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/orgs/{orgId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/apiKeys
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
POST /api/atlas/v2/orgs/{orgId}/apiKeys
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
DELETE /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
PATCH /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
POST /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
DELETE /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList/{ipAddress}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList/{ipAddress}
Updated
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/orgs/{orgId}/billing/costExplorer/usage
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/billing/costExplorer/usage/{token}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/federationSettings
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/groups
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/invites
Updated
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/orgs/{orgId}/invites
Updated
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/orgs/{orgId}/invites
Updated
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
Updated
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/invoices
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}/csv
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}/lineItems:search
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/liveMigrations/availableProjects
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/orgs/{orgId}/liveMigrations/linkTokens
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/orgs/{orgId}/liveMigrations/linkTokens
Updated
  • 添加了状态为“ 401 ”的非成功响应
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/nonCompliantResources
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/resourcePolicies
Updated
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/orgs/{orgId}/resourcePolicies
Updated
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/orgs/{orgId}/resourcePolicies/{resourcePolicyId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/resourcePolicies/{resourcePolicyId}
Updated
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/orgs/{orgId}/resourcePolicies/{resourcePolicyId}
Updated
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/orgs/{orgId}/resourcePolicies:validate
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts
Updated
  • 添加了状态为“404”的不成功响应
POST /api/atlas/v2/orgs/{orgId}/serviceAccounts
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
DELETE /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}
Updated
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/accessList
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
POST /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/accessList
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
DELETE /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/accessList/{ipAddress}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/groups
Updated
  • 添加了状态为“404”的不成功响应
POST /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/secrets
Updated
  • 添加了状态为“403”的不成功响应
  • 添加了状态为“404”的不成功响应
DELETE /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/secrets/{secretId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/teams
Updated
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/orgs/{orgId}/teams
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/teams/byName/{teamName}
Updated
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/orgs/{orgId}/teams/{teamId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/teams/{teamId}
Updated
  • 添加了状态为“403”的不成功响应
PATCH /api/atlas/v2/orgs/{orgId}/teams/{teamId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users
Updated
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users
Updated
  • 添加了状态为“403”的不成功响应
DELETE /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users/{userId}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/users
Updated
  • 添加了状态为“403”的不成功响应
POST /api/atlas/v2/users
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/users/byName/{userName}
Updated
  • 添加了状态为“403”的不成功响应
GET /api/atlas/v2/users/{userId}
Updated
  • 添加了状态为“403”的不成功响应

2025 年 4 月 02 日发布

DELETE /api/atlas/v2/groups/{groupId}
Updated
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“subschema #13： Atlas资源策略审核类型”添加到“results/items/oneOf[subschema #1：任何其他警报配置]/eventTypeName”响应属性“oneOf”列表中
  • 在“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #10: Resource Event Types]/”响应属性中添加了新的“CLUSTER_TAGS_MODIFIED”枚举值
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“subschema #13： Atlas资源策略审核类型”添加到“/oneOf[subschema #1：任何其他警报配置]/eventTypeName”请求属性“oneOf”列表
  • 将“subschema #13： Atlas资源策略审核类型”添加到“/oneOf[subschema #1：任何其他警报配置]/eventTypeName”响应属性“oneOf”列表中
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #10: Resource Event Types]/”响应属性中添加了新的“CLUSTER_TAGS_MODIFIED”枚举值
  • 已将新的 'CLUSTER_TAGS_MODIFIED'枚举值添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #10: Resource Event Types]/'
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“subschema #13： Atlas资源策略审核类型”添加到“/oneOf[subschema #1：任何其他警报配置]/eventTypeName”响应属性“oneOf”列表中
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #10: Resource Event Types]/”响应属性中添加了新的“CLUSTER_TAGS_MODIFIED”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“subschema #13： Atlas资源策略审核类型”添加到“/oneOf[subschema #1：任何其他警报配置]/eventTypeName”响应属性“oneOf”列表中
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #10: Resource Event Types]/”响应属性中添加了新的“CLUSTER_TAGS_MODIFIED”枚举值
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“subschema #13： Atlas资源策略审核类型”添加到“/oneOf[subschema #1：任何其他警报配置]/eventTypeName”请求属性“oneOf”列表
  • 将“subschema #13： Atlas资源策略审核类型”添加到“/oneOf[subschema #1：任何其他警报配置]/eventTypeName”响应属性“oneOf”列表中
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #10: Resource Event Types]/”响应属性中添加了新的“CLUSTER_TAGS_MODIFIED”枚举值
  • 已将新的 'CLUSTER_TAGS_MODIFIED'枚举值添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #10: Resource Event Types]/'
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 将“subschema #17： Atlas资源策略审核类型”添加到“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表中
  • 在“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #13: Resource Event Types]/”响应属性中添加了新的“CLUSTER_TAGS_MODIFIED”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 将“subschema #17： Atlas资源策略审核类型”添加到“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表中
  • 在“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #13: Resource Event Types]/”响应属性中添加了新的“CLUSTER_TAGS_MODIFIED”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“subschema #17： Atlas资源策略审核类型”添加到“/oneOf[subschema #7：任何其他警报]/eventTypeName”响应属性“oneOf”列表中
  • 在“/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #13: Resource Event Types]/”响应属性中添加了新的“CLUSTER_TAGS_MODIFIED”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“subschema #17： Atlas资源策略审核类型”添加到“/oneOf[subschema #7：任何其他警报]/eventTypeName”响应属性“oneOf”列表中
  • 在“/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #13: Resource Event Types]/”响应属性中添加了新的“CLUSTER_TAGS_MODIFIED”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 将“subschema #13： Atlas资源策略审核类型”添加到“results/items/oneOf[subschema #1：任何其他警报配置]/eventTypeName”响应属性“oneOf”列表中
  • 在“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #10: Resource Event Types]/”响应属性中添加了新的“CLUSTER_TAGS_MODIFIED”枚举值
DELETE /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
Updated
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/backup/exportBuckets
Updated
  • 已从响应的 'results/items/' 响应属性'oneOf' 列表中删除 '#/components/schemas/DiskBackupSnapshotAWSExportBucketResponse, #/components/schemas/DiskBackupSnapshotAzureExportBucketResponse'
POST /api/atlas/v2/groups/{groupId}/backup/exportBuckets
Updated
  • 已从响应正文“oneOf”列表中删除“#/components/schemas/DiskBackupSnapshotAWSExportBucketResponse, #/components/schemas/DiskBackupSnapshotAzureExportBucketResponse”
GET /api/atlas/v2/groups/{groupId}/backup/exportBuckets/{exportBucketId}
Updated
  • 已从响应正文“oneOf”列表中删除“#/components/schemas/DiskBackupSnapshotAWSExportBucketResponse, #/components/schemas/DiskBackupSnapshotAzureExportBucketResponse”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 在响应中添加了可选属性“encryptionAtRestProvider”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 在响应中添加了可选属性“encryptionAtRestProvider”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 在响应中添加了可选属性“encryptionAtRestProvider”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots/{snapshotId}
Updated
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 在“/items/actions/items/ 动作”响应属性中添加了新的“ANALYZE_SHARD_KEY、MOVE_CHUNK、SPLIT_CHUNK”枚举值
POST /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 在“actions/items/ 动作”响应属性中添加了新的“ANALYZE_SHARD_KEY、MOVE_CHUNK、SPLIT_CHUNK”枚举值
  • 在请求属性“actions/items/ 动作 ”中添加了新的“ANALYZE_SHARD_KEY、MOVE_CHUNK、SPLIT_CHUNK”枚举值
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 在“actions/items/ 动作”响应属性中添加了新的“ANALYZE_SHARD_KEY、MOVE_CHUNK、SPLIT_CHUNK”枚举值
PATCH /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 在“actions/items/ 动作”响应属性中添加了新的“ANALYZE_SHARD_KEY、MOVE_CHUNK、SPLIT_CHUNK”枚举值
  • 在请求属性“actions/items/ 动作 ”中添加了新的“ANALYZE_SHARD_KEY、MOVE_CHUNK、SPLIT_CHUNK”枚举值
DELETE /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/limits/{limitName}
Updated
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 在响应中添加了可选属性“enabledForSearchNodes”
PATCH /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 在响应中添加了可选属性“enabledForSearchNodes”
  • 添加了新的可选请求属性“enabledForSearchNodes”
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
Updated
  • 已将鉴别器添加到 'results/items/' 响应属性
POST /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
Updated
  • 添加了请求鉴别器
  • 为响应状态“202”添加了响应鉴别器
DELETE /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints/{endpointId}
Updated
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints/{endpointId}
Updated
  • 为响应状态“200”添加了响应鉴别器
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • 将“#/components/schemas/AtlasResourcePolicyAuditForNdsGroup”添加到响应的“results/items/”响应属性“oneOf”列表中
  • 将新的“AZ_BALANCING_OVERRIDE_MODIFIED”枚举值添加到“results/items/oneOf[subschema #15: NDS Audits]/eventTypeName”响应属性
  • 将新的 'CLUSTER_TAGS_MODIFIED'枚举值添加到 'results/items/oneOf[subschema #23: Resource Events]/eventTypeName' 响应属性
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 将“#/components/schemas/AtlasResourcePolicyAuditForNdsGroup”添加到响应的响应正文“oneOf”列表中
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • 将新的“AZ_BALANCING_OVERRIDE_MODIFIED”枚举值添加到“/oneOf[subschema #15: NDS Audits]/eventTypeName”响应属性
  • 将新的 'CLUSTER_TAGS_MODIFIED'枚举值添加到 '/oneOf[subschema #23: Resource Events]/eventTypeName' 响应属性
DELETE /api/atlas/v2/groups/{groupId}/invites/{invitationId}
Updated
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/pipelines
Updated
  • 已从响应的“/items/source”响应属性“oneOf”列表中删除“#/components/schemas/OnDemandCpsSnapshotSource, #/components/schemas/PeriodicCpsSnapshotSource”
POST /api/atlas/v2/groups/{groupId}/pipelines
Updated
  • 已从响应的“源”响应属性“oneOf”列表中删除“#/components/schemas/OnDemandCpsSnapshotSource, #/components/schemas/PeriodicCpsSnapshotSource”
DELETE /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}
Updated
  • 添加了状态为“ 200 ”的成功响应
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}
Updated
  • 已从响应的“源”响应属性“oneOf”列表中删除“#/components/schemas/OnDemandCpsSnapshotSource, #/components/schemas/PeriodicCpsSnapshotSource”
PATCH /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}
Updated
  • 已从响应的“源”响应属性“oneOf”列表中删除“#/components/schemas/OnDemandCpsSnapshotSource, #/components/schemas/PeriodicCpsSnapshotSource”
POST /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/pause
Updated
  • 已从响应的“源”响应属性“oneOf”列表中删除“#/components/schemas/OnDemandCpsSnapshotSource, #/components/schemas/PeriodicCpsSnapshotSource”
POST /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/resume
Updated
  • 已从响应的“源”响应属性“oneOf”列表中删除“#/components/schemas/OnDemandCpsSnapshotSource, #/components/schemas/PeriodicCpsSnapshotSource”
DELETE /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}
Updated
  • 添加了状态为“404”的不成功响应
DELETE /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}/endpoint/{endpointId}
Updated
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在响应中添加了可选的只写属性“results/items/connections/items/ 身份验证/sslKey”
  • 在响应中添加了可选的只写属性“results/items/connections/items/ 身份验证/sslKeyPassword”
  • 在响应中添加了可选属性“results/items/connections/items/ 身份验证/sslCertificate”
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在响应中添加了可选的只写属性“connections/items/ 身份验证/sslKey”
  • 在响应中添加了可选的只写属性“connections/items/ 身份验证/sslKeyPassword”
  • 在响应中添加了可选属性“connections/items/ 身份验证/sslCertificate”
  • 添加了新的可选请求属性“connections/items/ 身份验证/sslCertificate、connections/items/ 身份验证/sslKey、connections/items/ 身份验证/sslKeyPassword”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在响应中添加了可选的只写属性“connections/items/ 身份验证/sslKey”
  • 在响应中添加了可选的只写属性“connections/items/ 身份验证/sslKeyPassword”
  • 在响应中添加了可选属性“connections/items/ 身份验证/sslCertificate”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在响应中添加了可选的只写属性“connections/items/ 身份验证/sslKey”
  • 在响应中添加了可选的只写属性“connections/items/ 身份验证/sslKeyPassword”
  • 在响应中添加了可选属性“connections/items/ 身份验证/sslCertificate”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 在响应中添加了可选的只写属性“results/items/ 身份验证/sslKey”
  • 在响应中添加了可选的只写属性“results/items/ 身份验证/sslKeyPassword”
  • 在响应中添加了可选属性“results/items/ 身份验证/sslCertificate”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 在响应中添加了可选的只写属性“/ 身份验证/sslKey”
  • 在响应中添加了可选的只写属性“/ 身份验证/sslKeyPassword”
  • 在响应中添加了可选属性“/ 身份验证/sslCertificate”
  • 添加了新的可选请求属性“/ 身份验证/sslCertificate、/ 身份验证/sslKey、/ 身份验证/sslKeyPassword”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 在响应中添加了可选的只写属性“/ 身份验证/sslKey”
  • 在响应中添加了可选的只写属性“/ 身份验证/sslKeyPassword”
  • 在响应中添加了可选属性“/ 身份验证/sslCertificate”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 在响应中添加了可选的只写属性“/ 身份验证/sslKey”
  • 在响应中添加了可选的只写属性“/ 身份验证/sslKeyPassword”
  • 在响应中添加了可选属性“/ 身份验证/sslCertificate”
  • 添加了新的可选请求属性“/ 身份验证/sslCertificate、/ 身份验证/sslKey、/ 身份验证/sslKeyPassword”
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
Updated
  • 在响应中添加了可选的只写属性“connections/items/ 身份验证/sslKey”
  • 在响应中添加了可选的只写属性“connections/items/ 身份验证/sslKeyPassword”
  • 在响应中添加了可选属性“connections/items/ 身份验证/sslCertificate”
DELETE /api/atlas/v2/orgs/{orgId}
Updated
  • 添加了状态为“404”的不成功响应
DELETE /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}
Updated
  • 添加了状态为“404”的不成功响应
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • 在“results/items/oneOf[subschema #12: Atlas Resource Policy Audits]/eventTypeName”响应属性中添加了新的“RESOURCE_POLICY_VIOLATED”枚举值
  • 将新的“TAGS_MODIFIED”枚举值添加到“results/items/oneOf[subschema #11: Resource Events]/eventTypeName”响应属性
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • “isGlobalAdmin”响应的属性默认值“false”已删除
  • 将新的“RESOURCE_POLICY_VIOLATED”枚举值添加到“/oneOf[subschema #12: Atlas Resource Policy Audits]/eventTypeName”响应属性
  • 将新的“TAGS_MODIFIED”枚举值添加到“/oneOf[subschema #11: Resource Events]/eventTypeName”响应属性
GET /api/atlas/v2/users/{userId}
Updated
  • API 关闭日期已删除，但保留了 deprecated=true

2025 年 3 月 12 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
已交
  • 将“#/components/schemas/StreamProcessorMetricAlertConfigViewForNdsGroup”添加到响应的“results/items/”响应属性“oneOf”列表中
  • 将新的“CLUSTER_AGENT_IN_CRASH_LOOP”枚举值添加到“results/items/oneOf[subschema #5: Cluster Alert Configuration]/eventTypeName”响应属性
  • 将新的“ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID”枚举值添加到“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性
  • 已将新的 'PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE'枚举值添加到 'results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #12: NDS Auto Scaling Audit Types] ' 响应属性
POST /api/atlas/v2/groups/{groupId}/alertConfigs
已交
  • 将“#/components/schemas/StreamProcessorMetricAlertConfigViewForNdsGroup”添加到请求正文“oneOf”列表
  • 将“#/components/schemas/StreamProcessorMetricAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
  • 将新的“CLUSTER_AGENT_IN_CRASH_LOOP”枚举值添加到“/oneOf[subschema #5: Cluster Alert Configuration]/eventTypeName”响应属性
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性中添加了新的“ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID”枚举值
  • 在 '/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #12: NDS Auto Scaling Audit Types]/' 响应属性中添加了新的 'PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE'枚举值
  • 已将新的“CLUSTER_AGENT_IN_CRASH_LOOP”枚举值添加到请求属性“/oneOf[subschema #5: Cluster Alert Configuration]/eventTypeName”
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/' 中添加了新的 'ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID'枚举值
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #11: Stream Processor Event Types]/' 中添加了新的 'OUTSIDE_STREAM_PROCESSOR_METRIC_THRESHOLD'枚举值
  • 已将新的“PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE”、“PREDICTIVE_COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE”、“PREDICTIVE_COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE”枚举值添加到请求属性“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #12: NDS Auto] Scaling Audit Types/”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
已交
  • 将“#/components/schemas/StreamProcessorMetricAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
  • 将新的“CLUSTER_AGENT_IN_CRASH_LOOP”枚举值添加到“/oneOf[subschema #5: Cluster Alert Configuration]/eventTypeName”响应属性
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性中添加了新的“ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID”枚举值
  • 在 '/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #12: NDS Auto Scaling Audit Types]/' 响应属性中添加了新的 'PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE'枚举值
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
已交
  • 将“#/components/schemas/StreamProcessorMetricAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
  • 将新的“CLUSTER_AGENT_IN_CRASH_LOOP”枚举值添加到“/oneOf[subschema #5: Cluster Alert Configuration]/eventTypeName”响应属性
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性中添加了新的“ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID”枚举值
  • 在 '/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #12: NDS Auto Scaling Audit Types]/' 响应属性中添加了新的 'PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE'枚举值
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
已交
  • 将“#/components/schemas/StreamProcessorMetricAlertConfigViewForNdsGroup”添加到请求正文“oneOf”列表
  • 将“#/components/schemas/StreamProcessorMetricAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
  • 将新的“CLUSTER_AGENT_IN_CRASH_LOOP”枚举值添加到“/oneOf[subschema #5: Cluster Alert Configuration]/eventTypeName”响应属性
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性中添加了新的“ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID”枚举值
  • 在 '/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #12: NDS Auto Scaling Audit Types]/' 响应属性中添加了新的 'PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE'枚举值
  • 已将新的“CLUSTER_AGENT_IN_CRASH_LOOP”枚举值添加到请求属性“/oneOf[subschema #5: Cluster Alert Configuration]/eventTypeName”
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/' 中添加了新的 'ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID'枚举值
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #11: Stream Processor Event Types]/' 中添加了新的 'OUTSIDE_STREAM_PROCESSOR_METRIC_THRESHOLD'枚举值
  • 已将新的“PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE”、“PREDICTIVE_COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE”、“PREDICTIVE_COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE”枚举值添加到请求属性“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #12: NDS Auto] Scaling Audit Types/”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
已交
  • 将新的“CLUSTER_AGENT_IN_CRASH_LOOP”枚举值添加到“results/items/oneOf[subschema #2: Cluster Alerts]/eventTypeName”响应属性
  • 将新的“ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID”枚举值添加到“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性
  • 将新的枚举值“PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE”、“PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE”、“PREDICTIVE_COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE”添加到“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #15: NDS Auto Scaling Audit Types/”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts
已交
  • 将新的“CLUSTER_AGENT_IN_CRASH_LOOP”枚举值添加到“results/items/oneOf[subschema #2: Cluster Alerts]/eventTypeName”响应属性
  • 将新的“ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID”枚举值添加到“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性
  • 将新的枚举值“PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE”、“PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE”、“PREDICTIVE_COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE”添加到“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #15: NDS Auto Scaling Audit Types/”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
已交
  • 将新的“CLUSTER_AGENT_IN_CRASH_LOOP”枚举值添加到“/oneOf[subschema #2: Cluster Alerts]/eventTypeName”响应属性
  • 将新的“ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID”枚举值添加到“/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性
  • 已将新的 'PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE'枚举值添加到 '/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #15: NDS Auto Scaling Audit Types]/'属性
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
已交
  • 将新的“CLUSTER_AGENT_IN_CRASH_LOOP”枚举值添加到“/oneOf[subschema #2: Cluster Alerts]/eventTypeName”响应属性
  • 将新的“ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID”枚举值添加到“/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性
  • 已将新的 'PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE'枚举值添加到 '/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #15: NDS Auto Scaling Audit Types]/'属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
已交
  • 将“#/components/schemas/StreamProcessorMetricAlertConfigViewForNdsGroup”添加到响应的“results/items/”响应属性“oneOf”列表中
  • 将新的“CLUSTER_AGENT_IN_CRASH_LOOP”枚举值添加到“results/items/oneOf[subschema #5: Cluster Alert Configuration]/eventTypeName”响应属性
  • 将新的“ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID”枚举值添加到“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性
  • 已将新的 'PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE'枚举值添加到 'results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #12: NDS Auto Scaling Audit Types] ' 响应属性
GET /api/atlas/v2/groups/{groupId}/clusters
已交
  • 添加了可选属性 'results/items/advancedConfiguration、results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsAutoScaling/compute/predictiveEnabled、results/items/replicationSpecs /items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/autoScaling/compute/predictiveEnabled, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsAutoScaling/compute/predictiveEnabled, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/autoScaling/compute/predictiveEnabled, results/items/replicationSpecs/items /regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsAutoScaling/compute/predictiveEnabled, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema # 3： GCP区域复制规范]/autoScaling/compute/predictiveEnabled' 到响应
POST /api/atlas/v2/groups/{groupId}/clusters
已交
  • 添加了可选属性 'advancedConfiguration, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsAutoScaling/compute/predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1： Amazon Web Services区域复制规范]/autoScaling/compute/predictiveEnabled，replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/analyticsAutoScaling/compute/predictiveEnabled，replicationSpecs/items/regionConfigs /items/oneOf[subschema #2： Azure区域复制规范]/autoScaling/compute/predictiveEnabled、replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/analyticsAutoScaling/compute/predictiveEnabled 、replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/autoScaling/compute/predictiveEnabled' 到响应SE
  • 添加了新的可选请求属性 'advancedConfiguration, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsAutoScaling/compute/predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/autoScaling/compute/predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsAutoScaling/compute/predictiveEnabled, replicationSpecs/items /regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/autoScaling/compute/predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsAutoScaling/compute /predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/autoScaling/compute/predictiveEnabled'
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
已交
  • 在响应中添加了可选属性“advancedConfiguration, autoScaling/compute/predictiveEnabled”
  • 添加了新的可选请求属性“advancedConfiguration, autoScaling/compute/predictiveEnabled”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
已交
  • 添加了可选属性 'advancedConfiguration, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsAutoScaling/compute/predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1： Amazon Web Services区域复制规范]/autoScaling/compute/predictiveEnabled，replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/analyticsAutoScaling/compute/predictiveEnabled，replicationSpecs/items/regionConfigs /items/oneOf[subschema #2： Azure区域复制规范]/autoScaling/compute/predictiveEnabled、replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/analyticsAutoScaling/compute/predictiveEnabled 、replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/autoScaling/compute/predictiveEnabled' 到响应SE
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
已交
  • 添加了可选属性 'advancedConfiguration, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsAutoScaling/compute/predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1： Amazon Web Services区域复制规范]/autoScaling/compute/predictiveEnabled，replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/analyticsAutoScaling/compute/predictiveEnabled，replicationSpecs/items/regionConfigs /items/oneOf[subschema #2： Azure区域复制规范]/autoScaling/compute/predictiveEnabled、replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/analyticsAutoScaling/compute/predictiveEnabled 、replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/autoScaling/compute/predictiveEnabled' 到响应SE
  • 添加了新的可选请求属性 'advancedConfiguration, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsAutoScaling/compute/predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/autoScaling/compute/predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsAutoScaling/compute/predictiveEnabled, replicationSpecs/items /regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/autoScaling/compute/predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsAutoScaling/compute /predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/autoScaling/compute/predictiveEnabled'
GET / API/ Atlas/v2/groups/{groupId}/clusters/{clusterName}/autoScalingConfiguration
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
已交
  • 更新当不存在节点时API的返回，端点返回带有空JSON ({}) 的 200，而不是 400。
GET /api/atlas/v2/groups/{groupId}/events
已交
  • 将“#/components/schemas/ChartsAudit”添加到响应的“results/items/”响应属性“oneOf”列表中
  • 将新的“CLUSTER_AGENT_IN_CRASH_LOOP”枚举值添加到“results/items/oneOf[subschema #9: Cluster Events]/eventTypeName”响应属性
  • 在“results/items/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #12: Group Event Types]/”响应属性中添加了新的“ENCRYPTION_AT_REST_CONFIG_IS_VALID、ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID”枚举值
  • 在“results/items/oneOf[subschema #16: NDS Auto Scaling Audits]/eventTypeName”响应属性中添加了新的“PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
已交
  • 将“#/components/schemas/ChartsAudit”添加到响应的响应正文“oneOf”列表中
  • 将新的“CLUSTER_AGENT_IN_CRASH_LOOP”枚举值添加到“/oneOf[subschema #9: Cluster Events]/eventTypeName”响应属性
  • 在“/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #12: Group Event Types]/”响应属性中添加了新的“ENCRYPTION_AT_REST_CONFIG_IS_VALID”、“ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID”枚举值
  • 在 '/oneOf[subschema #16: NDS Auto Scaling Audits]/eventTypeName' 响应属性中添加了新的 'PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE'枚举值
POST /api/atlas/v2/groups/{groupId}/flexClusters:tenantUpgrade
已交
  • 添加了新的可选请求属性 'advancedConfiguration, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsAutoScaling/compute/predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/autoScaling/compute/predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsAutoScaling/compute/predictiveEnabled, replicationSpecs/items /regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/autoScaling/compute/predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsAutoScaling/compute /predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/autoScaling/compute/predictiveEnabled'
GET /api/atlas/v2/groups/{groupId}/streams
已交
  • 将“S3”鉴别器映射键添加到“results/items/connections/items/”响应属性
  • 将“#/components/schemas/ApiStreamsGCPRegionView”添加到响应的“results/items/dataProcessRegion/ 地区”响应属性“oneOf”列表中
  • 已将“#/components/schemas/StreamsS3Connection”添加到响应的“results/items/connections/items/”响应属性“oneOf”列表中
  • 将新的“OHIO_USA”枚举值添加到“results/items/dataProcessRegion/ 地区/”响应属性中
  • 在响应中添加了可选属性'results/items/connections/items/ Amazon Web Services/testBucket'
POST /api/atlas/v2/groups/{groupId}/streams
已交
  • 将“S3”鉴别器映射键添加到“connections/items/”请求属性
  • 将“#/components/schemas/ApiStreamsGCPRegionView”添加到“dataProcessRegion/ 地区”请求属性“oneOf”列表
  • 将“#/components/schemas/StreamsS3Connection”添加到“connections/items/”请求属性“oneOf”列表
  • 将“S3”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/schemas/ApiStreamsGCPRegionView”添加到响应的“dataProcessRegion/ 地区”响应属性“oneOf”列表中
  • 已将“#/components/schemas/StreamsS3Connection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 将新的“OHIO_USA”枚举值添加到“dataProcessRegion/ 地区/”响应属性中
  • 将新的“OHIO_USA”枚举值添加到请求属性“dataProcessRegion/ 地区/”
  • 在响应中添加了可选属性“connections/items/ Amazon Web Services/testBucket”
  • 添加了新的可选请求属性“connections/items/ Amazon Web Services/testBucket”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
已交
  • 将“S3”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/schemas/ApiStreamsGCPRegionView”添加到响应的“dataProcessRegion/ 地区”响应属性“oneOf”列表中
  • 已将“#/components/schemas/StreamsS3Connection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 将新的“OHIO_USA”枚举值添加到“dataProcessRegion/ 地区/”响应属性中
  • 在响应中添加了可选属性“connections/items/ Amazon Web Services/testBucket”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
已交
  • 将“#/components/schemas/ApiStreamsGCPRegionView”添加到“地区”请求属性“oneOf”列表
  • 将“S3”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/schemas/ApiStreamsGCPRegionView”添加到响应的“dataProcessRegion/ 地区”响应属性“oneOf”列表中
  • 已将“#/components/schemas/StreamsS3Connection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 将新的“OHIO_USA”枚举值添加到“dataProcessRegion/ 地区/”响应属性中
  • 将新的“OHIO_USA”枚举值添加到请求属性“地区/”
  • 在响应中添加了可选属性“connections/items/ Amazon Web Services/testBucket”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
已交
  • 将“S3”鉴别器映射键添加到“results/items/”响应属性
  • 已将“#/components/schemas/StreamsS3Connection”添加到响应的“results/items/”响应属性“oneOf”列表中
  • 在响应中添加了可选属性“results/items/ Amazon Web Services/testBucket”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
已交
  • 为请求鉴别器添加了“S3”映射键
  • 将“#/components/schemas/StreamsS3Connection”添加到请求正文“oneOf”列表
  • 将“S3”映射键添加到响应状态“200”的响应鉴别器
  • 已将“#/components/schemas/StreamsS3Connection”添加到响应的响应正文“oneOf”列表中
  • 在响应中添加了可选属性“/ Amazon Web Services/testBucket”
  • 添加了新的可选请求属性'/ Amazon Web Services/testBucket'
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
已交
  • 将“S3”映射键添加到响应状态“200”的响应鉴别器
  • 已将“#/components/schemas/StreamsS3Connection”添加到响应的响应正文“oneOf”列表中
  • 在响应中添加了可选属性“/ Amazon Web Services/testBucket”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
已交
  • 为请求鉴别器添加了“S3”映射键
  • 将“#/components/schemas/StreamsS3Connection”添加到请求正文“oneOf”列表
  • 将“S3”映射键添加到响应状态“200”的响应鉴别器
  • 已将“#/components/schemas/StreamsS3Connection”添加到响应的响应正文“oneOf”列表中
  • 在响应中添加了可选属性“/ Amazon Web Services/testBucket”
  • 添加了新的可选请求属性'/ Amazon Web Services/testBucket'
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
已交
  • 将“S3”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/schemas/ApiStreamsGCPRegionView”添加到响应的“dataProcessRegion/ 地区”响应属性“oneOf”列表中
  • 已将“#/components/schemas/StreamsS3Connection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 将新的“OHIO_USA”枚举值添加到“dataProcessRegion/ 地区/”响应属性中
  • 在响应中添加了可选属性“connections/items/ Amazon Web Services/testBucket”
GET /api/atlas/v2/orgs/{orgId}/events
已交
  • 将新的“GROUP_MOVED_FROM_ORG”枚举值添加到“results/items/oneOf[subschema #8: Org Events]/eventTypeName”响应属性
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
已交
  • 将新的“GROUP_MOVED_FROM_ORG”枚举值添加到“/oneOf[subschema #8: Org Events]/eventTypeName”响应属性
GET /api/atlas/v2/orgs/{orgId}/invoices/pending
已交
  • Added the new 'ATLAS_AWS_SEARCH_INSTANCE_S40_STORAGE_NVME, ATLAS_AWS_SEARCH_INSTANCE_S50_STORAGE_NVME, ATLAS_AWS_SEARCH_INSTANCE_S60_STORAGE_NVME, ATLAS_AWS_SEARCH_INSTANCE_S80_STORAGE_NVME, ATLAS_AWS_SEARCH_INSTANCE_S90_STORAGE_NVME' 枚举 values to the 'results/items/lineItems/items/sku' response属性
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
已交
  • Added the new 'ATLAS_AWS_SEARCH_INSTANCE_S40_STORAGE_NVME, ATLAS_AWS_SEARCH_INSTANCE_S50_STORAGE_NVME, ATLAS_AWS_SEARCH_INSTANCE_S60_STORAGE_NVME, ATLAS_AWS_SEARCH_INSTANCE_S80_STORAGE_NVME, ATLAS_AWS_SEARCH_INSTANCE_S90_STORAGE_NVME' 枚举 values to the 'lineItems/items/sku' response 属性

2025 年 2 月 25 日发布

GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/regionName/oneOf [subschema #3: GCP Regions]/' 响应属性
  • 将新的“AFRICA_SOUTH_1”、“NORTH_AMERICA_SOUTH_1”枚举值添加到“results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/regionName/oneOf[subschema” #3: GCP Regions]/' 响应属性
  • 已将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/regionName/oneOf[subschema #3: GCP Regions]/' 响应属性
  • 将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/regionName/oneOf[subschema #3: GCP Regions]/' 响应属性
  • 在“results/items/replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #3: GCP Regions]/”响应属性中添加了新的“AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1”枚举值
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1： Amazon Web Services区域复制规范”中]/regionName/oneOf[subschema #1: Amazon Web Services Regions]/' 响应属性
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/” regionName/oneOf[subschema #1: Amazon Web Services Regions]/' 响应属性
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/” regionName/oneOf[subschema #1: Amazon Web Services Regions]/' 响应属性
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/” regionName/oneOf[subschema #1: Amazon Web Services Regions]/' 响应属性
  • 571在'results/items/replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema1 #: Amazon Web Services Regions ]/' 响应属性
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/regionName/oneOf[subschema #3: GCP Regions]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/regionName/oneOf[subschema #3 中添加了新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值: GCP Regions]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/regionName/oneOf[subschema #3 中添加了新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值: GCP Regions]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/regionName/oneOf[subschema #3 中添加了新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值: GCP Regions]/' 响应属性
  • 在“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #3: GCP Regions]/”响应属性中添加了新的“AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1”枚举值
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/regionName/ oneOf[subschema #1: Amazon Web Services Regions]/' 响应属性
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/regionName/oneOf[ subschema #1: Amazon Web Services Regions]/' 响应属性
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/regionName/oneOf[ subschema #1: Amazon Web Services Regions]/' 响应属性
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional ReplicationSpecifications]/regionName/oneOf[ subschema #1: Amazon Web Services Regions]/' 响应属性
  • 在“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #1: Amazon Web Services Regions]/”响应中添加了新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值属性
  • 11在请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema1 #: Amazon Web Services Regional ReplicationSpecifications]/regionName/oneOf[subschema3 #: GCP地区]/'
  • 已将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/regionName/oneOf[subschema #3: GCP地区]/'
  • 已将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/regionName/oneOf[subschema #3: GCP地区]/'
  • 已将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/regionName/oneOf[subschema #3: GCP地区]/'
  • 已将新的“AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #3: GCP Regions]/”
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1： Amazon Web Services区域复制规范]/” regionName/oneOf[subschema #1: Amazon Web Services Regions]/'
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/regionName/” oneOf[subschema #1: Amazon Web Services Regions]/'
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/regionName/” oneOf[subschema #1: Amazon Web Services Regions]/'
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/regionName/” oneOf[subschema #1: Amazon Web Services Regions]/'
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #1: Amazon Web Services Regions]/” '
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 在“providerSettings/oneOf[subschema #3: Cloud Service Provider Settings for a Cluster]/regionName”响应属性中添加了新的“AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1”枚举值
  • 在“providerSettings/oneOf[subschema #1: Cloud Service Provider Settings for a Cluster]/regionName”响应属性中添加了新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值
  • 在请求属性“providerSettings/oneOf[subschema #3: Cloud Service Provider Settings for a Cluster]/regionName”中添加了新的“AFRICA_SOUTH_1”、“NORTH_AMERICA_SOUTH_1”枚举值
  • 在请求属性“providerSettings/oneOf[subschema #1: Cloud Service Provider Settings for a Cluster]/regionName”中添加了新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/regionName/oneOf[subschema #3: GCP Regions]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/regionName/oneOf[subschema #3 中添加了新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值: GCP Regions]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/regionName/oneOf[subschema #3 中添加了新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值: GCP Regions]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/regionName/oneOf[subschema #3 中添加了新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值: GCP Regions]/' 响应属性
  • 在“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #3: GCP Regions]/”响应属性中添加了新的“AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1”枚举值
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/regionName/ oneOf[subschema #1: Amazon Web Services Regions]/' 响应属性
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/regionName/oneOf[ subschema #1: Amazon Web Services Regions]/' 响应属性
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/regionName/oneOf[ subschema #1: Amazon Web Services Regions]/' 响应属性
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional ReplicationSpecifications]/regionName/oneOf[ subschema #1: Amazon Web Services Regions]/' 响应属性
  • 在“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #1: Amazon Web Services Regions]/”响应中添加了新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值属性
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/regionName/oneOf[subschema #3: GCP Regions]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/regionName/oneOf[subschema #3 中添加了新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值: GCP Regions]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/regionName/oneOf[subschema #3 中添加了新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值: GCP Regions]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/regionName/oneOf[subschema #3 中添加了新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值: GCP Regions]/' 响应属性
  • 在“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #3: GCP Regions]/”响应属性中添加了新的“AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1”枚举值
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/regionName/ oneOf[subschema #1: Amazon Web Services Regions]/' 响应属性
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/regionName/oneOf[ subschema #1: Amazon Web Services Regions]/' 响应属性
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/regionName/oneOf[ subschema #1: Amazon Web Services Regions]/' 响应属性
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional ReplicationSpecifications]/regionName/oneOf[ subschema #1: Amazon Web Services Regions]/' 响应属性
  • 在“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #1: Amazon Web Services Regions]/”响应中添加了新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值属性
  • 11在请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema1 #: Amazon Web Services Regional ReplicationSpecifications]/regionName/oneOf[subschema3 #: GCP地区]/'
  • 已将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/regionName/oneOf[subschema #3: GCP地区]/'
  • 已将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/regionName/oneOf[subschema #3: GCP地区]/'
  • 已将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/regionName/oneOf[subschema #3: GCP地区]/'
  • 已将新的“AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #3: GCP Regions]/”
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1： Amazon Web Services区域复制规范]/” regionName/oneOf[subschema #1: Amazon Web Services Regions]/'
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/regionName/” oneOf[subschema #1: Amazon Web Services Regions]/'
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/regionName/” oneOf[subschema #1: Amazon Web Services Regions]/'
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/regionName/” oneOf[subschema #1: Amazon Web Services Regions]/'
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #1: Amazon Web Services Regions]/” '
GET /api/atlas/v2/groups/{groupId}/containers
Updated
  • 在“results/items/oneOf[subschema #2: GCP]/regions/items/”响应属性中添加了新的“AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1”枚举值
  • 在“results/items/oneOf[subschema #3: Amazon Web Services]/regionName”响应属性中添加了新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值
POST /api/atlas/v2/groups/{groupId}/containers
Updated
  • 在 '/oneOf[subschema #2: GCP]/regions/items/' 响应属性中添加了新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“/oneOf[subschema #3: Amazon Web Services]/regionName”响应属性
  • 在请求属性'/oneOf[subschema #2: GCP ]/regions/items/' 中添加了新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“/oneOf[subschema #3: Amazon Web Services]/regionName”
GET /api/atlas/v2/groups/{groupId}/containers/all
Updated
  • 在“results/items/oneOf[subschema #2: GCP]/regions/items/”响应属性中添加了新的“AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1”枚举值
  • 在“results/items/oneOf[subschema #3: Amazon Web Services]/regionName”响应属性中添加了新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值
GET /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 在 '/oneOf[subschema #2: GCP]/regions/items/' 响应属性中添加了新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“/oneOf[subschema #3: Amazon Web Services]/regionName”响应属性
PATCH /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 在 '/oneOf[subschema #2: GCP]/regions/items/' 响应属性中添加了新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“/oneOf[subschema #3: Amazon Web Services]/regionName”响应属性
  • 在请求属性'/oneOf[subschema #2: GCP ]/regions/items/' 中添加了新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“/oneOf[subschema #3: Amazon Web Services]/regionName”
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 在“awsKms/ 地区”响应属性中添加了新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值
PATCH /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 在“awsKms/ 地区”响应属性中添加了新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“awsKms/ 地区”
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
Updated
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“results/items/oneOf[subschema #1: Azure Key Vault EAR Private Endpoint]/regionName/oneOf[subschema # 2： Amazon Web Services Regions]/' 响应属性
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“results/items/oneOf[subschema #2: Amazon Web Services KMS EAR Private Endpoint]/regionName/oneOf[subschema #2: Amazon Web Services Regions]/' 响应属性
  • 在“results/items/regionName/oneOf[subschema #2: Amazon Web Services Regions]/”响应属性中添加了新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值
POST /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
Updated
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“/oneOf[subschema #1: Azure Key Vault EAR Private Endpoint]/regionName/oneOf[subschema #2” : Amazon Web Services Regions]/' 响应属性
  • 将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到 '/oneOf[subschema #2: Amazon Web Services KMS EAR Private Endpoint]/regionName/oneOf[subschema #2: Amazon Web Services Regions]/' 响应属性
  • 在“regionName/oneOf[subschema #2: Amazon Web Services Regions]/”响应属性中添加了新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性'/oneOf[subschema #1: Azure Key Vault EAR Private Endpoint]/regionName/oneOf[subschema #2: Amazon Web Services Regions]/'
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性'/oneOf[subschema #2: Amazon Web Services KMS EAR Private Endpoint]/regionName/oneOf[subschema # 2： Amazon Web Services地区]/'
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“regionName/oneOf[subschema #2: Amazon Web Services Regions]/”
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints/{endpointId}
Updated
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“/oneOf[subschema #1: Azure Key Vault EAR Private Endpoint]/regionName/oneOf[subschema #2” : Amazon Web Services Regions]/' 响应属性
  • 将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到 '/oneOf[subschema #2: Amazon Web Services KMS EAR Private Endpoint]/regionName/oneOf[subschema #2: Amazon Web Services Regions]/' 响应属性
  • 在“regionName/oneOf[subschema #2: Amazon Web Services Regions]/”响应属性中添加了新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值
POST /api/atlas/v2/groups/{groupId}/flexClusters:tenantUpgrade
Updated
  • 11在请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema1 #: Amazon Web Services Regional ReplicationSpecifications]/regionName/oneOf[subschema3 #: GCP地区]/'
  • 已将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/regionName/oneOf[subschema #3: GCP地区]/'
  • 已将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/regionName/oneOf[subschema #3: GCP地区]/'
  • 已将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/regionName/oneOf[subschema #3: GCP地区]/'
  • 已将新的“AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #3: GCP Regions]/”
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1： Amazon Web Services区域复制规范]/” regionName/oneOf[subschema #1: Amazon Web Services Regions]/'
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/regionName/” oneOf[subschema #1: Amazon Web Services Regions]/'
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/regionName/” oneOf[subschema #1: Amazon Web Services Regions]/'
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/regionName/” oneOf[subschema #1: Amazon Web Services Regions]/'
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #1: Amazon Web Services Regions]/” '

2025 年 2 月 20 日发布

PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
已交
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、ORG_BILLING_READ_ONLY”枚举值添加到请求属性“roleMappings/items/roleAssignments/items/ 角色”
POST /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings
已交
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、ORG_BILLING_READ_ONLY”枚举值添加到请求属性“roleAssignments/items/ 角色”
PUT /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings/{id}
已交
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、ORG_BILLING_READ_ONLY”枚举值添加到请求属性“roleAssignments/items/ 角色”
POST /api/atlas/v2/groups/{groupId}/access
已交
  • 端点已弃用
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、GROUP_SEARCH_INDEX_EDITOR、GROUP_STREAM_PROCESSING_OWNER”枚举值添加到请求属性“roles/items/”
GET /api/atlas/v2/groups/{groupId}/alertConfigs
已交
  • 在“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/”响应属性中添加了新的“CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY”枚举值
  • 将新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值添加到“results/items/oneOf[subschema #15: Stream Processor Alert Configuration]/eventTypeName”响应属性
  • 在“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #11: Stream Processor Event Types]/”响应属性中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值
POST /api/atlas/v2/groups/{groupId}/alertConfigs
已交
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/”响应属性中添加了新的“CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY”枚举值
  • 将新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值添加到“/oneOf[subschema #15: Stream Processor Alert Configuration]/eventTypeName”响应属性
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #11: Stream Processor Event Types]/”响应属性中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/' 中添加了新的 'CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY'枚举值
  • 在请求属性'/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ 通知/items/oneOf[subschema #3: 群组通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #11: 枚举 Set Alert Configuration]/ 通知/items/oneOf[subschema #3:群组通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #:12 枚举 Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema :3 Group notification]/roles/items/'
  • 在请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #3: Group通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #14: Flex Alert Configuration]/ 通知/items/oneOf[subschema #3: Group通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #15: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #3:群组通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #3:群组通知]/roles/items/'
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、GROUP_READ_ONLY、GROUP_SEARCH_INDEX_EDITOR、GROUP_STREAM_PROCESSING_OWNER”枚举值添加到请求属性“/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #3：群组通知]/roles/items/'
  • 已将新的 'GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、GROUP_READ_ONLY、GROUP_SEARCH_INDEX_EDITOR、GROUP_STREAM_PROCESSING_OWNER'枚举值添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #3 : Group notification]/roles/items/'
  • 在请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #3:群组通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #3: Group通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #6: Cps 备份枚举值警报配置]/ 通知/items/oneOf[subschema #3 : Group notification]/roles/items/'
  • 在请求属性'/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #3:群组通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #3: Group通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #3:群组通知]/roles/items/'
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性'/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles /items/'
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #12: 副本集阈值警报配置]/ 通知/items/oneOf[subschema #7: 组织通知]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #14: Flex Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #15: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 在请求属性“/oneOf[subschema #15: Stream Processor Alert Configuration]/eventTypeName”中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #11: Stream Processor Event Types]/' 中添加了新的 'STREAM_PROCESSOR_KAFKA_LAG_BEHIND'枚举值
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
已交
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/”响应属性中添加了新的“CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY”枚举值
  • 将新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值添加到“/oneOf[subschema #15: Stream Processor Alert Configuration]/eventTypeName”响应属性
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #11: Stream Processor Event Types]/”响应属性中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
已交
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/”响应属性中添加了新的“CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY”枚举值
  • 将新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值添加到“/oneOf[subschema #15: Stream Processor Alert Configuration]/eventTypeName”响应属性
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #11: Stream Processor Event Types]/”响应属性中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
已交
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/”响应属性中添加了新的“CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY”枚举值
  • 将新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值添加到“/oneOf[subschema #15: Stream Processor Alert Configuration]/eventTypeName”响应属性
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #11: Stream Processor Event Types]/”响应属性中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/' 中添加了新的 'CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY'枚举值
  • 在请求属性'/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ 通知/items/oneOf[subschema #3: 群组通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #11: 枚举 Set Alert Configuration]/ 通知/items/oneOf[subschema #3:群组通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #:12 枚举 Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema :3 Group notification]/roles/items/'
  • 在请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #3: Group通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #14: Flex Alert Configuration]/ 通知/items/oneOf[subschema #3: Group通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #15: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #3:群组通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #3:群组通知]/roles/items/'
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、GROUP_READ_ONLY、GROUP_SEARCH_INDEX_EDITOR、GROUP_STREAM_PROCESSING_OWNER”枚举值添加到请求属性“/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #3：群组通知]/roles/items/'
  • 已将新的 'GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、GROUP_READ_ONLY、GROUP_SEARCH_INDEX_EDITOR、GROUP_STREAM_PROCESSING_OWNER'枚举值添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #3 : Group notification]/roles/items/'
  • 在请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #3:群组通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #3: Group通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #6: Cps 备份枚举值警报配置]/ 通知/items/oneOf[subschema #3 : Group notification]/roles/items/'
  • 在请求属性'/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #3:群组通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #3: Group通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #3:群组通知]/roles/items/'
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性'/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles /items/'
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #12: 副本集阈值警报配置]/ 通知/items/oneOf[subschema #7: 组织通知]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #14: Flex Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #15: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 在请求属性“/oneOf[subschema #15: Stream Processor Alert Configuration]/eventTypeName”中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #11: Stream Processor Event Types]/' 中添加了新的 'STREAM_PROCESSOR_KAFKA_LAG_BEHIND'枚举值
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
已交
  • 在“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/”响应属性中添加了新的“CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY”枚举值
  • 在“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #14: Stream Processor Event Types]/”响应属性中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts
已交
  • 在“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/”响应属性中添加了新的“CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY”枚举值
  • 在“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #14: Stream Processor Event Types]/”响应属性中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
已交
  • 在“/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/”响应属性中添加了新的“CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY”枚举值
  • 在“/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #14: Stream Processor Event Types]/”响应属性中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
已交
  • 在“/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/”响应属性中添加了新的“CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY”枚举值
  • 在“/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #14: Stream Processor Event Types]/”响应属性中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
已交
  • 在“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/”响应属性中添加了新的“CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY”枚举值
  • 将新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值添加到“results/items/oneOf[subschema #15: Stream Processor Alert Configuration]/eventTypeName”响应属性
  • 在“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #11: Stream Processor Event Types]/”响应属性中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值
POST /api/atlas/v2/groups/{groupId}/apiKeys
已交
  • 在请求属性“roles/items/”中添加了新的“GROUP_DATABASE_ACCESS_ADMIN, ORG_BILLING_READ_ONLY”枚举值
PATCH /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
已交
  • 已将新的“GROUP_BACKUP_MANAGER”、“GROUP_DATABASE_ACCESS_ADMIN”、“GROUP_OBSERVABILITY_VIEWER”枚举值添加到请求属性“roles/items/”
POST /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
已交
  • 将新的 'GROUP_DATABASE_ACCESS_ADMIN'枚举值添加到请求属性'/items/roles/items/'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/managedNamespaces
已交
  • 请求可选属性“isCustomShardKeyHashed”变为非只写属性
  • 请求可选属性“isShardKeyUnique”变为非只写属性
  • 请求可选属性“numInitialChunks”变为非只写属性
  • 请求可选属性“presplitHashedZones”变为非只写属性
  • 请求所需属性“customShardKey”变为非只读属性
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
已交
  • 在响应中添加了可选属性“results/items/oneOf[subschema #2: Amazon Web Services KMS EAR Private Endpoint]/privateEndpointConnectionName”
POST /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
已交
  • 在响应中添加了可选属性“/oneOf[subschema #2: Amazon Web Services KMS EAR Private Endpoint]/privateEndpointConnectionName”
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints/{endpointId}
已交
  • 在响应中添加了可选属性“/oneOf[subschema #2: Amazon Web Services KMS EAR Private Endpoint]/privateEndpointConnectionName”
GET /api/atlas/v2/groups/{groupId}/events
已交
  • 在“results/items/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #34: Version Audit Types]/”响应属性中添加了新的“ACME_PROVIDER_FIXED、ACME_PROVIDER_UNFIXED”枚举值
  • 在“results/items/oneOf[subschema #15: NDS Audits]/eventTypeName”响应属性中添加了新的“CLUSTER_INSTANCE_AGENT_API_KEY_ROTATED、MONGOT_LOGS_DOWNLOADED”枚举值
  • 在“results/items/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #5: Cps Backup Event Types]/”响应属性中添加了新的“CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY”枚举值
  • 在“results/items/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #30: Stream Processor Event Types]/”响应属性中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND、STREAM_PROCESSOR_KAFKA_LAG_CURRENT”枚举值
  • 在“results/items/oneOf[subschema #25: Stream Processor Events]/eventTypeName”响应属性中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND、STREAM_PROCESSOR_KAFKA_LAG_CURRENT”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
已交
  • 在“/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #34: Version Audit Types]/”响应属性中添加了新的“ACME_PROVIDER_FIXED、ACME_PROVIDER_UNFIXED”枚举值
  • 在“/oneOf[subschema #15: NDS Audits]/eventTypeName”响应属性中添加了新的“CLUSTER_INSTANCE_AGENT_API_KEY_ROTATED、MONGOT_LOGS_DOWNLOADED”枚举值
  • 在“/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #5: Cps Backup Event Types]/”响应属性中添加了新的“CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY”枚举值
  • 在“/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #30: Stream Processor Event Types]/”响应属性中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND、STREAM_PROCESSOR_KAFKA_LAG_CURRENT”枚举值
  • 在 '/oneOf[subschema #25: Stream Processor Events]/eventTypeName' 响应属性中添加了新的 'STREAM_PROCESSOR_KAFKA_LAG_BEHIND、STREAM_PROCESSOR_KAFKA_LAG_CURRENT'枚举值
PATCH /api/atlas/v2/groups/{groupId}/invites
已交
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、GROUP_SEARCH_INDEX_EDITOR、GROUP_STREAM_PROCESSING_OWNER”枚举值添加到请求属性“roles/items/”
POST /api/atlas/v2/groups/{groupId}/invites
已交
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、GROUP_SEARCH_INDEX_EDITOR、GROUP_STREAM_PROCESSING_OWNER”枚举值添加到请求属性“roles/items/”
PATCH /api/atlas/v2/groups/{groupId}/invites/{invitationId}
已交
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、GROUP_SEARCH_INDEX_EDITOR、GROUP_STREAM_PROCESSING_OWNER”枚举值添加到请求属性“roles/items/”
POST /api/atlas/v2/groups/{groupId}/serviceAccounts
已交
  • 已将新的“GROUP_DATABASE_ACCESS_ADMIN”枚举值添加到请求属性“roles/items/”
PATCH /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
已交
  • 已将新的“GROUP_DATABASE_ACCESS_ADMIN”枚举值添加到请求属性“roles/items/”
POST /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}:invite
已交
  • 将新的 'GROUP_DATABASE_ACCESS_ADMIN'枚举值添加到请求属性'/items/roles/items/'
GET /api/atlas/v2/groups/{groupId}/settings
已交
  • 在响应中添加了可选属性“isDataExplorerGenAIFeaturesEnabled、isDataExplorerGenAISampleDocumentPassingEnabled”
PATCH /api/atlas/v2/groups/{groupId}/settings
已交
  • 在响应中添加了可选属性“isDataExplorerGenAIFeaturesEnabled、isDataExplorerGenAISampleDocumentPassingEnabled”
  • 添加了新的可选请求属性“isDataExplorerGenAIFeaturesEnabled、isDataExplorerGenAISampleDocumentPassingEnabled”
GET /api/atlas/v2/groups/{groupId}/streams
已交
  • 将“AWSLambda”鉴别器映射键添加到“results/items/connections/items/”响应属性
  • 将“#/components/schemas/StreamsAWSLambdaConnection”添加到响应的“results/items/connections/items/”响应属性“oneOf”列表中
  • 将新的“AWSLambda”枚举值添加到“results/items/connections/items/type”响应属性中
POST /api/atlas/v2/groups/{groupId}/streams
已交
  • 将“AWSLambda”鉴别器映射键添加到“connections/items/”请求属性
  • 将“#/components/schemas/StreamsAWSLambdaConnection”添加到“connections/items/”请求属性“oneOf”列表
  • 将“AWSLambda”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/schemas/StreamsAWSLambdaConnection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 已将新的“AWSLambda”枚举值添加到“connections/items/type”响应属性中
  • 已将新的“AWSLambda”枚举值添加到请求属性“connections/items/type”
GET /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections
已交
  • 在响应中添加了可选属性“results/items/interfaceEndpointName”
POST /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections
已交
  • 在响应中添加了可选属性“interfaceEndpointName”
GET /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections/{connectionId}
已交
  • 在响应中添加了可选属性“interfaceEndpointName”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
已交
  • 将“AWSLambda”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/schemas/StreamsAWSLambdaConnection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 已将新的“AWSLambda”枚举值添加到“connections/items/type”响应属性中
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
已交
  • 将“AWSLambda”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/schemas/StreamsAWSLambdaConnection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 已将新的“AWSLambda”枚举值添加到“connections/items/type”响应属性中
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
已交
  • 将“AWSLambda”鉴别器映射键添加到“results/items/”响应属性
  • 将“#/components/schemas/StreamsAWSLambdaConnection”添加到响应的“results/items/”响应属性“oneOf”列表中
  • 已将新的“AWSLambda”枚举值添加到“results/items/type”响应属性中
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
已交
  • 将“AWSLambda”映射键添加到请求鉴别器
  • 将“#/components/schemas/StreamsAWSLambdaConnection”添加到请求正文“oneOf”列表
  • 已将“AWSLambda”映射键添加到响应状态“200”的响应鉴别器
  • 将“#/components/schemas/StreamsAWSLambdaConnection”添加到响应的响应正文“oneOf”列表中
  • 已将新的“AWSLambda”枚举值添加到“/type”响应属性
  • 在“type”响应属性中添加了新的“AWSLambda”枚举值
  • 已将新的“AWSLambda”枚举值添加到请求属性“/type”
  • 已将新的“AWSLambda”枚举值添加到请求属性“type”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
已交
  • 已将“AWSLambda”映射键添加到响应状态“200”的响应鉴别器
  • 将“#/components/schemas/StreamsAWSLambdaConnection”添加到响应的响应正文“oneOf”列表中
  • 已将新的“AWSLambda”枚举值添加到“/type”响应属性
  • 在“type”响应属性中添加了新的“AWSLambda”枚举值
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
已交
  • 将“AWSLambda”映射键添加到请求鉴别器
  • 将“#/components/schemas/StreamsAWSLambdaConnection”添加到请求正文“oneOf”列表
  • 已将“AWSLambda”映射键添加到响应状态“200”的响应鉴别器
  • 将“#/components/schemas/StreamsAWSLambdaConnection”添加到响应的响应正文“oneOf”列表中
  • 已将新的“AWSLambda”枚举值添加到“/type”响应属性
  • 在“type”响应属性中添加了新的“AWSLambda”枚举值
  • 已将新的“AWSLambda”枚举值添加到请求属性“/type”
  • 已将新的“AWSLambda”枚举值添加到请求属性“type”
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
已交
  • 将“AWSLambda”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/schemas/StreamsAWSLambdaConnection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 已将新的“AWSLambda”枚举值添加到“connections/items/type”响应属性中
POST /api/atlas/v2/groups/{groupId}/teams
已交
  • Added the new 'GROUP_BACKUP_MANAGER, GROUP_CLUSTER_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_DATA_ACCESS_ADMIN, GROUP_DATA_ACCESS_READ_ONLY, GROUP_DATA_ACCESS_READ_WRITE, GROUP_OBSERVABILITY_VIEWER, GROUP_OWNER, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 枚举 values to the 请求 属性 '/items/roleNames'
PATCH /api/atlas/v2/groups/{groupId}/teams/{teamId}
已交
  • Added the new 'GROUP_BACKUP_MANAGER, GROUP_CLUSTER_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_DATA_ACCESS_ADMIN, GROUP_DATA_ACCESS_READ_ONLY, GROUP_DATA_ACCESS_READ_WRITE, GROUP_OBSERVABILITY_VIEWER, GROUP_OWNER, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 枚举 values to the 请求 属性 'roleNames'
GET /api/atlas/v2/groups/{groupId}/users
已交
  • 针对状态“200”，“results/items/roles/items/”响应的属性类型/格式从“对象'/'' 更改为 'string'/''
  • 添加了API标签“MongoDB Cloud Users”
  • 添加了新的可选“查询”请求参数“orgMembershipStatus”
  • 添加了新的可选“查询”请求参数“用户名”
  • 已将鉴别器添加到 'results/items/' 响应属性
  • 将 '#/components/schemas/GroupPendingUserResponse, #/components/schemas/GroupActiveUserResponse' 添加到响应的 'results/items/' 响应属性'oneOf' 列表
  • Added the new 'GROUP_BACKUP_MANAGER, GROUP_CLUSTER_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_DATA_ACCESS_ADMIN, GROUP_DATA_ACCESS_READ_ONLY, GROUP_DATA_ACCESS_READ_WRITE, GROUP_OBSERVABILITY_VIEWER, GROUP_OWNER, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 枚举 values to the 'results/items/roles/items/' response 属性
  • 在响应中添加了必需的属性“results/items/orgMembershipStatus”
  • 从响应中删除了必需属性“results/items/country、results/items/emailAddress、results/items/firstName、results/items/lastName、results/items/mobileNumber、results/items/password”
  • 删除了可选属性 'results/items/createdAt、results/items/lastAuth、results/items/links、results/items/roles/items/groupId、results/items/roles/items/orgId、results/items/roles/items /roleName, results/items/teamIds' 来自响应
  • 响应属性 'results/items/ ID, results/items/roles' 变为必填项
POST /api/atlas/v2/groups/{groupId}/users
已交
  • 已添加端点
DELETE /api/atlas/v2/groups/{groupId}/users/{userId}
已交
  • 添加了API标签“MongoDB Cloud Users”
GET /api/atlas/v2/groups/{groupId}/users/{userId}
已交
  • 已添加端点
PUT /api/atlas/v2/groups/{groupId}/users/{userId}/roles
已交
  • 端点已弃用
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER”枚举值添加到请求属性“groupRoles/items/”
POST /api/atlas/v2/groups/{groupId}/users/{userId}:addRole
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/users/{userId}:removeRole
已交
  • 已添加端点
POST /api/atlas/v2/orgs
已交
  • 将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“apiKey/roles/items/”
POST /api/atlas/v2/orgs/{orgId}/apiKeys
已交
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“roles/items/”
PATCH /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}
已交
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“roles/items/”
GET /api/atlas/v2/orgs/{orgId}/invites
已交
  • 端点已弃用
PATCH /api/atlas/v2/orgs/{orgId}/invites
已交
  • 端点已弃用
  • 在请求属性“groupRoleAssignments/items/roles/items/”中添加了新的“GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、GROUP_SEARCH_INDEX_EDITOR、GROUP_STREAM_PROCESSING_OWNER”枚举值
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“roles/items/”
POST /api/atlas/v2/orgs/{orgId}/invites
已交
  • 端点已弃用
  • 在请求属性“groupRoleAssignments/items/roles/items/”中添加了新的“GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、GROUP_SEARCH_INDEX_EDITOR、GROUP_STREAM_PROCESSING_OWNER”枚举值
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“roles/items/”
DELETE /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
已交
  • 端点已弃用
GET /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
已交
  • 端点已弃用
PATCH /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
已交
  • 端点已弃用
  • 在请求属性“groupRoleAssignments/items/roles/items/”中添加了新的“GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、GROUP_SEARCH_INDEX_EDITOR、GROUP_STREAM_PROCESSING_OWNER”枚举值
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“roles/items/”
GET /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users
已交
  • 针对状态“200”，“results/items/roles”响应的属性类型/格式从“大量”/“更改为”对象“/”
  • 添加了API标签“MongoDB Cloud Users”
  • 添加了新的可选“查询”请求参数“orgMembershipStatus”
  • 添加了新的可选“查询”请求参数“用户名”
  • 已将鉴别器添加到 'results/items/' 响应属性
  • 将 '#/components/schemas/OrgPendingUserResponse, #/components/schemas/OrgActiveUserResponse' 添加到响应的 'results/items/' 响应属性'oneOf' 列表
  • 在响应中添加了必需的属性“results/items/orgMembershipStatus”
  • 从响应中删除了必需属性“results/items/country、results/items/emailAddress、results/items/firstName、results/items/lastName、results/items/mobileNumber、results/items/password”
  • 在响应中添加了可选属性“results/items/roles/groupRoleAssignments, results/items/roles/orgRoles”
  • 从响应中删除了可选属性“results/items/createdAt, results/items/lastAuth, results/items/links”
  • 响应属性 'results/items/ ID, results/items/roles' 变为必填项
POST /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users
已交
  • 端点已弃用
DELETE /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users/{userId}
已交
  • 端点已弃用
POST /api/atlas/v2/orgs/{orgId}/teams/{teamId}:addUser
已交
  • 已添加端点
POST /api/atlas/v2/orgs/{orgId}/teams/{teamId}:removeUser
已交
  • 已添加端点
GET /api/atlas/v2/orgs/{orgId}/users
已交
  • 针对状态“200”，“results/items/roles”响应的属性类型/格式从“大量”/“更改为”对象“/”
  • 添加了API标签“MongoDB Cloud Users”
  • 添加了新的可选“查询”请求参数“orgMembershipStatus”
  • 添加了新的可选“查询”请求参数“用户名”
  • 已将鉴别器添加到 'results/items/' 响应属性
  • 将 '#/components/schemas/OrgPendingUserResponse, #/components/schemas/OrgActiveUserResponse' 添加到响应的 'results/items/' 响应属性'oneOf' 列表
  • 在响应中添加了必需的属性“results/items/orgMembershipStatus”
  • 从响应中删除了必需属性“results/items/country、results/items/emailAddress、results/items/firstName、results/items/lastName、results/items/mobileNumber、results/items/password”
  • 在响应中添加了可选属性“results/items/roles/groupRoleAssignments, results/items/roles/orgRoles”
  • 从响应中删除了可选属性“results/items/createdAt, results/items/lastAuth, results/items/links”
  • 响应属性 'results/items/ ID, results/items/roles' 变为必填项
POST /api/atlas/v2/orgs/{orgId}/users
已交
  • 已添加端点
DELETE /api/atlas/v2/orgs/{orgId}/users/{userId}
已交
  • 添加了API标签“MongoDB Cloud Users”
GET /api/atlas/v2/orgs/{orgId}/users/{userId}
已交
  • 已添加端点
PATCH /api/atlas/v2/orgs/{orgId}/users/{userId}
已交
  • 已添加端点
PUT /api/atlas/v2/orgs/{orgId}/users/{userId}/roles
已交
  • 端点已弃用
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“orgRoles/items/”
POST /api/atlas/v2/orgs/{orgId}/users/{userId}:addRole
已交
  • 已添加端点
POST /api/atlas/v2/orgs/{orgId}/users/{userId}:removeRole
已交
  • 已添加端点
POST /api/atlas/v2/users
已交
  • 端点已弃用
  • 在请求属性“roles/items/roleName”中添加了新的“GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、ORG_BILLING_READ_ONLY”枚举值
GET /api/atlas/v2/users/byName/{userName}
已交
  • 端点已弃用
GET /api/atlas/v2/users/{userId}
已交
  • 端点已弃用

2025 年 2 月 18 日发布

GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/performanceAdvisor/dropIndexSuggestions
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/performanceAdvisor/schemaAdvice
已交
  • 已添加端点

2025 年 2 月 06 日发布

GET /api/atlas/v2/clusters
Updated
  • “results/items/groupId”响应的属性模式“^([af0-9]{24})$”已删除
  • “results/items/orgId”响应的属性模式“^([af0-9]{24})$”已删除
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
  • “results/items/dataAccessIdentityProviderIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • “dataAccessIdentityProviderIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • “dataAccessIdentityProviderIds/items/”请求属性的 minLength 从“24”减少到“0”
  • “identityProviderId”请求属性的 minLength 从“20”减少到“0”
  • “orgId”请求属性的 minLength 从“24”减少到“0”
  • “roleMappings/items/ ID”请求属性的 minLength 从“24”减少到“0”
  • “roleMappings/items/roleAssignments/items/groupId”请求属性的 minLength 从“24”减少到“0”
  • “roleMappings/items/roleAssignments/items/orgId”请求属性的 minLength 从“24”减少到“0”
  • “userConflicts/items/federationSettingsId”请求属性的 minLength 从“24”减少到“0”
  • “userConflicts/items/userId”请求属性的 minLength 从“24”减少到“0”
  • 从请求属性“dataAccessIdentityProviderIds/items/”中删除了模式“^([af0-9]{24})$”
  • “dataAccessIdentityProviderIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “roleAssignments/items/groupId”请求属性的 minLength 从“24”减少到“0”
  • “roleAssignments/items/orgId”请求属性的 minLength 从“24”减少到“0”
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings/{id}
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“ID”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings/{id}
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“ID”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
PUT /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings/{id}
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“ID”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “roleAssignments/items/groupId”请求属性的 minLength 从“24”减少到“0”
  • “roleAssignments/items/orgId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
  • “results/items/associatedOrgs/items/dataAccessIdentityProviderIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
  • “results/items/oneOf[subschema #1: SAML]/关联Orgs/items/dataAccessIdentityProviderIds/items/”响应的属性模式'^([af0-9]{24}) $' 已删除
  • “results/items/oneOf[subschema #2: OIDC WORKFORCE]/关联Orgs/items/dataAccessIdentityProviderIds/items/”响应的属性模式“^([af0-9]{24}” )$' 已删除
  • “results/items/oneOf[subschema #3: OIDC WORKLOAD]/关联Orgs/items/dataAccessIdentityProviderIds/items/”响应的属性模式“^([af0-9]{24}” )$' 已删除
POST /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
  • '/oneOf[subschema #1: OIDC WORKFORCE]/关联Orgs/items/dataAccessIdentityProviderIds/items/' 响应的属性模式'^([af0-9]{24})$'已删除
  • '/oneOf[subschema #2: OIDC WORKLOAD]/关联Orgs/items/dataAccessIdentityProviderIds/items/' 响应的属性模式'^([af0-9]{24})$'已删除
  • “关联Orgs/items/dataAccessIdentityProviderIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
  • '/oneOf[subschema #1: SAML]/关联Orgs/items/dataAccessIdentityProviderIds/items/' 响应的属性模式'^([af0-9]{24})$' 为已删除
  • '/oneOf[subschema #2: OIDC WORKFORCE]/关联Orgs/items/dataAccessIdentityProviderIds/items/' 响应的属性模式'^([af0-9]{24})$'已删除
  • '/oneOf[subschema #3: OIDC WORKLOAD]/关联Orgs/items/dataAccessIdentityProviderIds/items/' 响应的属性模式'^([af0-9]{24})$'已删除
  • “关联Orgs/items/dataAccessIdentityProviderIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
  • '/oneOf[subschema #1: SAML]/关联Orgs/items/dataAccessIdentityProviderIds/items/' 响应的属性模式'^([af0-9]{24})$' 为已删除
  • '/oneOf[subschema #2: OIDC WORKFORCE]/关联Orgs/items/dataAccessIdentityProviderIds/items/' 响应的属性模式'^([af0-9]{24})$'已删除
  • '/oneOf[subschema #3: OIDC WORKLOAD]/关联Orgs/items/dataAccessIdentityProviderIds/items/' 响应的属性模式'^([af0-9]{24})$'已删除
  • “关联Orgs/items/dataAccessIdentityProviderIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}/jwks
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}/metadata.xml
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“identityProviderId”，minLength 从“20”减少到“0”
POST /api/atlas/v2/groups
Updated
  • 对于“查询”请求参数“projectOwnerId”，minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “名称”请求属性的 minLength 从“1”减少到“0”
  • “orgId”请求属性的 minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/access
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “teamIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
GET /api/atlas/v2/groups/{groupId}/accessList
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/accessList
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “/items/groupId”请求属性的 minLength 已从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/accessList/{entryValue}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/accessList/{entryValue}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/accessList/{entryValue}/status
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ ID'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 已从 '24 ' 改为 '0'
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #11: Replica Set Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #12: 副本集阈值警报配置]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #13: Serverless Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #13: Serverless Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0 '
  • '/oneOf[subschema #14: Flex Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #14: Flex Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #14: Flex Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0 '
  • '/oneOf[subschema #15: Stream Processor Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #15: Stream Processor Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #15: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #1: Any other Alert Configurations]/groupId”请求属性的 minLength 从“24”减少到“0”
  • “/oneOf[subschema #1: Any other Alert Configurations]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #2: App Services Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #2: App Services Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #3: App Services Metric Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #4: Billing Threshold Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #5: Cluster Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #5: Cluster Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0 '
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #6: Cps 备份阈值警报配置]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 已从 '24' 减少到 '0'
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #7: Encryption Key Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #8: Host Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #8: Host Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0 '
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #9: Host Metric Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • 已将新的“HOST_EXPOSED、HOST_SECURITY_CHECKUP_NOT_MET、HOST_SSL_CERTIFICATE_STALE、HOST_VERSION_BEHIND、VERSION_BEHIND”枚举值添加到请求属性“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”
  • 在请求属性“/oneOf[subschema #12：副本集阈值警报配置]/eventTypeName”中添加了新的“TOO_FEW_HEALTHY_MEMBERS、TOO_MANY_UNHEALTHY_MEMBERS”枚举值
DELETE /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 对于“path”请求参数“alertConfigId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 对于“path”请求参数“alertConfigId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 对于“path”请求参数“alertConfigId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 对于“path”请求参数“alertConfigId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ ID'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 已从 '24 ' 改为 '0'
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #11: Replica Set Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #12: 副本集阈值警报配置]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #13: Serverless Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #13: Serverless Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0 '
  • '/oneOf[subschema #14: Flex Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #14: Flex Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #14: Flex Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0 '
  • '/oneOf[subschema #15: Stream Processor Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #15: Stream Processor Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #15: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #1: Any other Alert Configurations]/groupId”请求属性的 minLength 从“24”减少到“0”
  • “/oneOf[subschema #1: Any other Alert Configurations]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #2: App Services Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #2: App Services Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #3: App Services Metric Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #4: Billing Threshold Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #5: Cluster Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #5: Cluster Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0 '
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #6: Cps 备份阈值警报配置]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 已从 '24' 减少到 '0'
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #7: Encryption Key Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #8: Host Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #8: Host Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0 '
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #9: Host Metric Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • 已将新的“HOST_EXPOSED、HOST_SECURITY_CHECKUP_NOT_MET、HOST_SSL_CERTIFICATE_STALE、HOST_VERSION_BEHIND、VERSION_BEHIND”枚举值添加到请求属性“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”
  • 在请求属性“/oneOf[subschema #12：副本集阈值警报配置]/eventTypeName”中添加了新的“TOO_FEW_HEALTHY_MEMBERS、TOO_MANY_UNHEALTHY_MEMBERS”枚举值
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 对于“path”请求参数“alertConfigId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 对于“path”请求参数“alertId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 对于“path”请求参数“alertId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 对于“path”请求参数“alertId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/apiKeys
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/apiKeys
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
Updated
  • 对于“path”请求参数“apiUserId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
Updated
  • 对于“path”请求参数“apiUserId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
Updated
  • 对于“path”请求参数“apiUserId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “/items/userId”请求属性的 minLength 已从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/auditLog
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/auditLog
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/awsCustomDNS
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/awsCustomDNS
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/backup/exportBuckets
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/backup/exportBuckets
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “/iamRoleId”请求属性的 minLength 从“24”减少到“0”
  • “/roleId”请求属性的 minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/backup/exportBuckets/{exportBucketId}
Updated
  • 对于“path”请求参数“exportBucketId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/backup/exportBuckets/{exportBucketId}
Updated
  • 对于“path”请求参数“exportBucketId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/backupCompliancePolicy
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/backupCompliancePolicy
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PUT /api/atlas/v2/groups/{groupId}/backupCompliancePolicy
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “onDemandPolicyItem/ ID”请求属性的 minLength 从“24”减少到“0”
  • “projectId”请求属性的 minLength 从“24”减少到“0”
  • “scheduledPolicyItems/items/ ID”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/cloudProviderAccess
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/cloudProviderAccess
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “/roleId”请求属性的 minLength 从“24”减少到“0”
  • “/ _id”请求属性的 minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/cloudProviderAccess/{cloudProvider}/{roleId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“roleId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/cloudProviderAccess/{roleId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“roleId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/cloudProviderAccess/{roleId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“roleId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsAutoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/autoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/autoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/analyticsAutoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/autoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/autoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/analyticsAutoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/autoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/autoScaling/compute/minInstanceSize”变为只读
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “名称”请求属性的 minLength 从“1”减少到“0”
  • “replicationSpecs/items/ ID”请求属性的 minLength 从“24”减少到“0”
  • “replicationSpecs/items/zoneId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/provider/regions
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “名称”请求属性的 minLength 从“1”减少到“0”
  • “replicationSpecs/items/ ID”请求属性的 minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgradeToServerless
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “名称”请求属性的 minLength 从“1”减少到“0”
  • 在响应中添加了可选属性 'providerSettings/forcedDiskSizeGBLimit、providerSettings/forcedInstanceSizeName、providerSettings/forcedProviderName'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsAutoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/autoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/autoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/analyticsAutoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/autoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/autoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/analyticsAutoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/autoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/autoScaling/compute/minInstanceSize”变为只读
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “名称”请求属性的 minLength 从“1”减少到“0”
  • “replicationSpecs/items/ ID”请求属性的 minLength 从“24”减少到“0”
  • “replicationSpecs/items/zoneId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “exportBucketId”请求属性的 minLength 从“24”减少到“0”
  • “snapshotId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports/{exportId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“exportId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “components/items/privateDownloadDeliveryUrls/items/endpointId”请求属性的 minLength 从“22”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “privateDownloadDeliveryUrls/items/endpointId”请求属性的 minLength 从“22”减少到“0”
  • “snapshotId”请求属性的 minLength 从“24”减少到“0”
  • “targetClusterName”请求属性的 minLength 从“1”减少到“0”
  • “targetGroupId”请求属性的 minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs/{restoreJobId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“restoreJobId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs/{restoreJobId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“restoreJobId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “clusterId”请求属性的 minLength 从“24”减少到“0”
  • “clusterName”请求属性的 minLength 从“1”减少到“0”
  • “export/exportBucketId”请求属性的 minLength 从“24”减少到“0”
  • “policies/items/ ID”请求属性的 minLength 已从“24”减少到“0”
  • “policies/items/policyItems/items/ ID”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 在“results/items/snapshotType”响应属性中添加了新的“fallback”枚举值
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 已将新的 'fallback'枚举值添加到 'snapshotType' 响应属性
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/shardedCluster/{snapshotId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“snapshotId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/shardedCluster/{snapshotId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“snapshotId”，minLength 从“24”减少到“0”
  • 已将新的 'fallback'枚举值添加到 'snapshotType' 响应属性
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/shardedClusters
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 在“results/items/snapshotType”响应属性中添加了新的“fallback”枚举值
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“snapshotId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“snapshotId”，minLength 从“24”减少到“0”
  • 已将新的 'fallback'枚举值添加到 'snapshotType' 响应属性
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“snapshotId”，minLength 从“24”减少到“0”
  • 已将新的 'fallback'枚举值添加到 'snapshotType' 响应属性
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/download
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “clusterName”请求属性的 minLength 从“1”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “projectId”请求属性的 minLength 从“24”减少到“0”
  • “snapshotId”请求属性的 minLength 从“24”减少到“0”
  • “targetDeploymentItemName”请求属性的 minLength 从“1”减少到“0”
  • “targetProjectId”请求属性的 minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/restore
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “clusterName”请求属性的 minLength 从“1”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “projectId”请求属性的 minLength 从“24”减少到“0”
  • “snapshotId”请求属性的 minLength 从“24”减少到“0”
  • “targetDeploymentItemName”请求属性的 minLength 从“1”减少到“0”
  • “targetProjectId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/restores
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/restores/{restoreId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“restoreId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/snapshots
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/snapshots/{snapshotId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“snapshotId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backupCheckpoints
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backupCheckpoints/{checkpointId}
Updated
  • 对于“path”请求参数“checkpointId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PUT /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/unpin
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “indexID”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{databaseName}/{collectionName}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“indexId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“indexId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“indexId”，minLength 从“24”减少到“0”
  • “indexID”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/customZoneMapping
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/customZoneMapping
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/managedNamespaces
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/managedNamespaces
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/index
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “_id”请求属性的 minLength 从“24”减少到“0”
  • “clusterName”请求属性的 minLength 从“1”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/queryLogs.gz
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • 对于“path”请求参数“archiveId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • 对于“path”请求参数“archiveId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • 对于“path”请求参数“archiveId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “_id”请求属性的 minLength 从“24”减少到“0”
  • “clusterName”请求属性的 minLength 从“1”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/outageSimulation
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/outageSimulation
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/outageSimulation
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “clusterName”请求属性的 minLength 从“1”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/performanceAdvisor/suggestedIndexes
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “suggestedIndexes/items/ 影响/items/”响应的属性模式“^([af0-9]{24})$”已被删除
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restartPrimaries
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“查询”请求参数“batchId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “batchId”请求属性的 minLength 从“24”减少到“0”
  • “checkpointId”请求属性的 minLength 从“24”减少到“0”
  • “clusterId”请求属性的 minLength 从“24”减少到“0”
  • “clusterName”请求属性的 minLength 从“1”减少到“0”
  • “delivery/targetClusterId”请求属性的 minLength 已从“24”减少到“0”
  • “delivery/targetClusterName”请求属性的 minLength 从“1”减少到“0”
  • “delivery/targetGroupId”请求属性的 minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “snapshotId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs/{jobId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“jobId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“indexId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“indexId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“indexId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshotSchedule
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshotSchedule
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “clusterId”请求属性的 minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots/{snapshotId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“snapshotId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots/{snapshotId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“snapshotId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots/{snapshotId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“snapshotId”，minLength 从“24”减少到“0”
  • “clusterId”请求属性的 minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “parts/items/clusterId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/status
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/{clusterView}/collStats/namespaces
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/{clusterView}/{databaseName}/{collectionName}/collStats/measurements
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}:grantMongoDBEmployeeAccess
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}:pinFeatureCompatibilityVersion
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}:revokeMongoDBEmployeeAccess
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}:unpinFeatureCompatibilityVersion
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{hostName}/logs/{logName}.gz
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/collStats/metrics
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/containers
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “results/items/oneOf[subschema #1: Azure]/vnetName”响应的属性模式已从“^([-\w._()])+$”更改为“^([-\w._()])+$”。 _()])$'
  • 在“results/items/oneOf[subschema #1: Azure]/ 地区”响应属性中添加了新的“MEXICO_CENTRAL、NEW_ZEALAND_NORTH、SPAIN_CENTRAL”枚举值
POST /api/atlas/v2/groups/{groupId}/containers
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • '/oneOf[subschema #1: Azure]/ ID'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #1: Azure]/vnetName'请求属性的 minLength 从 '38' 减少到 '0'
  • '/oneOf[subschema #2: GCP]/gcpProjectId'请求属性的 minLength 从 '26' 减少到 '0'
  • “/oneOf[subschema #2: GCP]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #2: GCP]/networkName'请求属性的 minLength 从 '36' 减少到 '0'
  • “/oneOf[subschema #3: Amazon Web Services]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #3: Amazon Web Services]/vpcId'请求属性的 minLength 从 '5' 减少到 '0'
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • '/oneOf[subschema #1: Azure]/vnetName' 响应的属性模式已从 '^([-\w._()])+$' 更改为 '^([-\w._() ])$'
  • 在“/oneOf[subschema #1: Azure]/ 地区”响应属性中添加了新的“MEXICO_CENTRAL、NEW_ZEALAND_NORTH、SPAIN_CENTRAL”枚举值
  • 在请求属性“/oneOf[subschema #1: Azure]/ 地区 ”中添加了新的“MEXICO_CENTRAL、NEW_ZEALAND_NORTH、SPAIN_CENTRAL”枚举值
GET /api/atlas/v2/groups/{groupId}/containers/all
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “results/items/oneOf[subschema #1: Azure]/vnetName”响应的属性模式已从“^([-\w._()])+$”更改为“^([-\w._()])+$”。 _()])$'
  • 在“results/items/oneOf[subschema #1: Azure]/ 地区”响应属性中添加了新的“MEXICO_CENTRAL、NEW_ZEALAND_NORTH、SPAIN_CENTRAL”枚举值
DELETE /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 对于“path”请求参数“containerId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 对于“path”请求参数“containerId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • '/oneOf[subschema #1: Azure]/vnetName' 响应的属性模式已从 '^([-\w._()])+$' 更改为 '^([-\w._() ])$'
  • 在“/oneOf[subschema #1: Azure]/ 地区”响应属性中添加了新的“MEXICO_CENTRAL、NEW_ZEALAND_NORTH、SPAIN_CENTRAL”枚举值
PATCH /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 对于“path”请求参数“containerId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • '/oneOf[subschema #1: Azure]/ ID'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #1: Azure]/vnetName'请求属性的 minLength 从 '38' 减少到 '0'
  • '/oneOf[subschema #2: GCP]/gcpProjectId'请求属性的 minLength 从 '26' 减少到 '0'
  • “/oneOf[subschema #2: GCP]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #2: GCP]/networkName'请求属性的 minLength 从 '36' 减少到 '0'
  • “/oneOf[subschema #3: Amazon Web Services]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #3: Amazon Web Services]/vpcId'请求属性的 minLength 从 '5' 减少到 '0'
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • '/oneOf[subschema #1: Azure]/vnetName' 响应的属性模式已从 '^([-\w._()])+$' 更改为 '^([-\w._() ])$'
  • 在“/oneOf[subschema #1: Azure]/ 地区”响应属性中添加了新的“MEXICO_CENTRAL、NEW_ZEALAND_NORTH、SPAIN_CENTRAL”枚举值
  • 在请求属性“/oneOf[subschema #1: Azure]/ 地区 ”中添加了新的“MEXICO_CENTRAL、NEW_ZEALAND_NORTH、SPAIN_CENTRAL”枚举值
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/dataFederation
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/dataFederation
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/limits
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/limits/{limitName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/limits/{limitName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/limits/{limitName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/queryLogs.gz
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/databaseUsers
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “results/items/groupId”响应的属性模式“^([af0-9]{24})$”已删除
POST /api/atlas/v2/groups/{groupId}/databaseUsers
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
  • “scopes/items/name”请求属性的 minLength 从“1”减少到“0”
  • 已从请求属性“groupId”中删除模式“^([af0-9]{24})$”
  • “groupId”响应的属性模式“^([af0-9]{24})$”已删除
DELETE /api/atlas/v2/groups/{groupId}/databaseUsers/{databaseName}/{username}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/databaseUsers/{databaseName}/{username}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “groupId”响应的属性模式“^([af0-9]{24})$”已删除
PATCH /api/atlas/v2/groups/{groupId}/databaseUsers/{databaseName}/{username}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
  • “scopes/items/name”请求属性的 minLength 从“1”减少到“0”
  • 已从请求属性“groupId”中删除模式“^([af0-9]{24})$”
  • “groupId”响应的属性模式“^([af0-9]{24})$”已删除
GET /api/atlas/v2/groups/{groupId}/databaseUsers/{username}/certs
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/databaseUsers/{username}/certs
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/dbAccessHistory/clusters/{clusterName}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “accessLogs/items/groupId”响应的属性模式“^([af0-9]{24})$”已删除
GET /api/atlas/v2/groups/{groupId}/dbAccessHistory/processes/{hostname}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “accessLogs/items/groupId”响应的属性模式“^([af0-9]{24})$”已删除
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 在响应中添加了可选属性“awsKms/requirePrivateNetworking”
PATCH /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “awsKms/roleId”请求属性的 minLength 从“24”减少到“0”
  • 在响应中添加了可选属性“awsKms/requirePrivateNetworking”
  • 添加了新的可选请求属性“awsKms/requirePrivateNetworking”
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 将 '#/components/schemas/AWSKMSEARPrivateEndpoint' 添加到响应的 'results/items/' 响应属性'oneOf' 列表
  • 将“subschema #2: Amazon Web Services Regions”添加到“results/items/oneOf[subschema #1: Azure Key Vault EAR Private Endpoint]/regionName”响应属性“oneOf”列表中
  • 将“subschema #2: Amazon Web Services Regions”添加到“results/items/regionName”响应属性“oneOf”列表中
  • 将新的枚举值“Amazon Web Services”添加到“path”请求参数“cloudProvider”
POST /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
Updated
  • 将 '#/components/schemas/AWSKMSEARPrivateEndpoint' 添加到请求正文 'oneOf' 列表
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “/oneOf[subschema #1: Azure Key Vault EAR Private Endpoint]/ ID”请求属性的 minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • 将“subschema #2: Amazon Web Services Regions”添加到“/oneOf[subschema #1: Azure Key Vault EAR Private Endpoint]/regionName”请求属性“oneOf”列表
  • 将“subschema #2: Amazon Web Services Regions”添加到“regionName”请求属性“oneOf”列表中
  • 将 '#/components/schemas/AWSKMSEARPrivateEndpoint' 添加到响应的响应正文 'oneOf' 列表
  • 将“subschema #2: Amazon Web Services Regions”添加到“/oneOf[subschema #1: Azure Key Vault EAR Private Endpoint]/regionName”响应属性“oneOf”列表中
  • 将“subschema #2: Amazon Web Services Regions”添加到该响应的“regionName”响应属性“oneOf”列表中
  • 将新的枚举值“Amazon Web Services”添加到“path”请求参数“cloudProvider”
  • 将新的“Amazon Web Services”枚举值添加到请求属性“/oneOf[subschema #1: Azure Key Vault EAR Private Endpoint]/cloudProvider”
  • 已将新的“Amazon Web Services”枚举值添加到请求属性“cloudProvider”
DELETE /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints/{endpointId}
Updated
  • 对于“path”请求参数“endpointId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 将新的枚举值“Amazon Web Services”添加到“path”请求参数“cloudProvider”
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints/{endpointId}
Updated
  • 对于“path”请求参数“endpointId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 将 '#/components/schemas/AWSKMSEARPrivateEndpoint' 添加到响应的响应正文 'oneOf' 列表
  • 将“subschema #2: Amazon Web Services Regions”添加到“/oneOf[subschema #1: Azure Key Vault EAR Private Endpoint]/regionName”响应属性“oneOf”列表中
  • 将“subschema #2: Amazon Web Services Regions”添加到该响应的“regionName”响应属性“oneOf”列表中
  • 将新的枚举值“Amazon Web Services”添加到“path”请求参数“cloudProvider”
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 将“#/components/schemas/DataExplorerEvent”添加到响应的“results/items/”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 对于“path”请求参数“eventId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 将“#/components/schemas/DataExplorerEvent”添加到响应的响应正文“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/flexClusters
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 已添加“clusterType”响应的属性默认值“REPLICASET”
POST /api/atlas/v2/groups/{groupId}/flexClusters
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “名称”请求属性的 minLength 从“1”减少到“0”
  • 已添加“clusterType”响应的属性默认值“REPLICASET”
DELETE /api/atlas/v2/groups/{groupId}/flexClusters/{name}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“name”，minLength 从“1”减少到“0”
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“name”，minLength 从“1”减少到“0”
  • 已添加“clusterType”响应的属性默认值“REPLICASET”
PATCH /api/atlas/v2/groups/{groupId}/flexClusters/{name}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“name”，minLength 从“1”减少到“0”
  • 已添加“clusterType”响应的属性默认值“REPLICASET”
POST /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/download
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“name”，minLength 从“1”减少到“0”
  • “snapshotId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/restoreJobs
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“name”，minLength 从“1”减少到“0”
POST /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/restoreJobs
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“name”，minLength 从“1”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “instanceName”请求属性的 minLength 从“1”减少到“0”
  • “projectId”请求属性的 minLength 从“24”减少到“0”
  • “snapshotId”请求属性的 minLength 从“24”减少到“0”
  • “targetDeploymentItemName”请求属性的 minLength 从“1”减少到“0”
  • “targetProjectId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/restoreJobs/{restoreJobId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“name”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“restoreJobId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/snapshots
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“name”，minLength 从“1”减少到“0”
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/snapshots/{snapshotId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“name”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“snapshotId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/flexClusters:tenantUpgrade
Updated
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsAutoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/autoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/autoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/analyticsAutoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/autoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/autoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/analyticsAutoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/autoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/autoScaling/compute/minInstanceSize”变为只读
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “名称”请求属性的 minLength 从“1”减少到“0”
  • “replicationSpecs/items/ ID”请求属性的 minLength 从“24”减少到“0”
  • “replicationSpecs/items/zoneId”请求属性的 minLength 从“24”减少到“0”
  • 已添加“clusterType”响应的属性默认值“REPLICASET”
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics/indexes/{databaseName}/{collectionName}/measurements
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “indexIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics/indexes/{databaseName}/{collectionName}/{indexName}/measurements
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “indexIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics/measurements
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/integrations
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PUT /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/invites
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/invites
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/invites
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/invites/{invitationId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“invitationId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/invites/{invitationId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“invitationId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/invites/{invitationId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“invitationId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/ipAddresses
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/limits
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/limits/{limitName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/limits/{limitName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/limits/{limitName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/liveMigrations
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “_id”请求属性的 minLength 从“24”减少到“0”
  • “destination/groupId”请求属性的 minLength 从“24”减少到“0”
  • “source/groupId”请求属性的 minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/liveMigrations/validate
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “_id”请求属性的 minLength 从“24”减少到“0”
  • “destination/groupId”请求属性的 minLength 从“24”减少到“0”
  • “source/groupId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/liveMigrations/validate/{validationId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“validationId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/liveMigrations/{liveMigrationId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“liveMigrationId”，minLength 从“24”减少到“0”
PUT /api/atlas/v2/groups/{groupId}/liveMigrations/{liveMigrationId}/cutover
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“liveMigrationId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/maintenanceWindow
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/maintenanceWindow
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/maintenanceWindow
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/maintenanceWindow/autoDefer
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/maintenanceWindow/defer
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/managedSlowMs
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/managedSlowMs/disable
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/managedSlowMs/enable
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/mongoDBVersions
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/peers
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “results/items/oneOf[subschema #2: Azure]/vnetName”响应的属性模式已从“^([-\w._()])+$”更改为“^([-\w._()])+$”。 _()])$'
POST /api/atlas/v2/groups/{groupId}/peers
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • '/oneOf[subschema #1: Amazon Web Services]/awsAccountId'请求属性的 minLength 从 '12' 减少到 '0'
  • '/oneOf[subschema #1: Amazon Web Services]/containerId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #1: Amazon Web Services]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #1: Amazon Web Services]/vpcId'请求属性的 minLength 从 '5' 减少到 '0'
  • '/oneOf[subschema #2: Azure]/containerId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #2: Azure]/ ID'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #3: GCP]/containerId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #3: GCP]/gcpProjectId'请求属性的 minLength 从 '6' 减少到 '0'
  • “/oneOf[subschema #3: GCP]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #3: GCP]/networkName'请求属性的 minLength 从 '1' 减少到 '0'
  • “containerId”请求属性的 minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • '/oneOf[subschema #2: Azure]/vnetName' 响应的属性模式已从 '^([-\w._()])+$' 更改为 '^([-\w._() ])$'
DELETE /api/atlas/v2/groups/{groupId}/peers/{peerId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“peerId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/peers/{peerId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“peerId”，minLength 从“24”减少到“0”
  • '/oneOf[subschema #2: Azure]/vnetName' 响应的属性模式已从 '^([-\w._()])+$' 更改为 '^([-\w._() ])$'
PATCH /api/atlas/v2/groups/{groupId}/peers/{peerId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“peerId”，minLength 从“24”减少到“0”
  • '/oneOf[subschema #1: Amazon Web Services]/awsAccountId'请求属性的 minLength 从 '12' 减少到 '0'
  • '/oneOf[subschema #1: Amazon Web Services]/containerId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #1: Amazon Web Services]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #1: Amazon Web Services]/vpcId'请求属性的 minLength 从 '5' 减少到 '0'
  • '/oneOf[subschema #2: Azure]/containerId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #2: Azure]/ ID'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #3: GCP]/containerId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #3: GCP]/gcpProjectId'请求属性的 minLength 从 '6' 减少到 '0'
  • “/oneOf[subschema #3: GCP]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #3: GCP]/networkName'请求属性的 minLength 从 '1' 减少到 '0'
  • “containerId”请求属性的 minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • '/oneOf[subschema #2: Azure]/vnetName' 响应的属性模式已从 '^([-\w._()])+$' 更改为 '^([-\w._() ])$'
GET /api/atlas/v2/groups/{groupId}/pipelines
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/pipelines
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “_id”请求属性的 minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
  • “source/oneOf[subschema #1: On-Demand Cloud Provider Snapshot Source]/groupId”请求属性的 minLength 从“24”减少到“0”
  • “source/oneOf[subschema #2:Periodic Cloud Provider Snapshot Source]/groupId”请求属性的 minLength 从“24”减少到“0”
  • “source/oneOf[subschema #2: 定期云提供商快照源]/policyItemId”请求属性的 minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“pipelineName”，minLength 从“1”减少到“0”
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“pipelineName”，minLength 从“1”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“pipelineName”，minLength 从“1”减少到“0”
  • “_id”请求属性的 minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
  • “source/oneOf[subschema #1: On-Demand Cloud Provider Snapshot Source]/groupId”请求属性的 minLength 从“24”减少到“0”
  • “source/oneOf[subschema #2:Periodic Cloud Provider Snapshot Source]/groupId”请求属性的 minLength 从“24”减少到“0”
  • “source/oneOf[subschema #2: 定期云提供商快照源]/policyItemId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/availableSchedules
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“pipelineName”，minLength 从“1”减少到“0”
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/availableSnapshots
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“pipelineName”，minLength 从“1”减少到“0”
  • 在“results/items/snapshotType”响应属性中添加了新的“fallback”枚举值
POST /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/pause
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“pipelineName”，minLength 从“1”减少到“0”
POST /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/resume
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“pipelineName”，minLength 从“1”减少到“0”
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/runs
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“pipelineName”，minLength 从“1”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/runs/{pipelineRunId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“pipelineName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“pipelineRunId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/runs/{pipelineRunId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“pipelineName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“pipelineRunId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/trigger
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“pipelineName”，minLength 从“1”减少到“0”
  • “snapshotId”请求属性的 minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/privateEndpoint/endpointService
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/regionalMode
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/privateEndpoint/regionalMode
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint/{endpointId}
Updated
  • 对于“path”请求参数“endpointId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint/{endpointId}
Updated
  • 对于“path”请求参数“endpointId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint/{endpointId}
Updated
  • 对于“path”请求参数“endpointId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}
Updated
  • 对于“path”请求参数“endpointServiceId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}
Updated
  • 对于“path”请求参数“endpointServiceId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}/endpoint
Updated
  • 对于“path”请求参数“endpointServiceId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}/endpoint/{endpointId}
Updated
  • 对于“path”请求参数“endpointServiceId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}/endpoint/{endpointId}
Updated
  • 对于“path”请求参数“endpointServiceId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/privateIpMode
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/privateIpMode
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “endpointId”请求属性的 minLength 从“22”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds/{endpointId}
Updated
  • 对于“path”请求参数“endpointId”，minLength 从“22”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds/{endpointId}
Updated
  • 对于“path”请求参数“endpointId”，minLength 从“22”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/processes
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/collStats/namespaces
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/databases
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/databases/{databaseName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/databases/{databaseName}/measurements
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/disks
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/disks/{partitionName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/disks/{partitionName}/measurements
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/measurements
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/performanceAdvisor/namespaces
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/performanceAdvisor/slowQueryLogs
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/performanceAdvisor/suggestedIndexes
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “suggestedIndexes/items/ 影响/items/”响应的属性模式“^([af0-9]{24})$”已被删除
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/{databaseName}/{collectionName}/collStats/measurements
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/sampleDatasetLoad/{name}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“name”，minLength 从“1”减少到“0”
GET /api/atlas/v2/groups/{groupId}/sampleDatasetLoad/{sampleDatasetId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“sampleDatasetId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/serverless
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 在响应中添加了可选属性 'results/items/providerSettings/forcedDiskSizeGBLimit、results/items/providerSettings/forcedInstanceSizeName、results/items/providerSettings/forcedProviderName'
POST /api/atlas/v2/groups/{groupId}/serverless
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “名称”请求属性的 minLength 从“1”减少到“0”
  • 在响应中添加了可选属性 'providerSettings/forcedDiskSizeGBLimit、providerSettings/forcedInstanceSizeName、providerSettings/forcedProviderName'
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/restoreJobs
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/restoreJobs
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “snapshotId”请求属性的 minLength 从“24”减少到“0”
  • “targetClusterName”请求属性的 minLength 从“1”减少到“0”
  • “targetGroupId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/restoreJobs/{restoreJobId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“restoreJobId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/snapshots
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“snapshotId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/performanceAdvisor/autoIndexing
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/performanceAdvisor/autoIndexing
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/serverless/{name}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“name”，minLength 从“1”减少到“0”
GET /api/atlas/v2/groups/{groupId}/serverless/{name}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“name”，minLength 从“1”减少到“0”
  • 在响应中添加了可选属性 'providerSettings/forcedDiskSizeGBLimit、providerSettings/forcedInstanceSizeName、providerSettings/forcedProviderName'
PATCH /api/atlas/v2/groups/{groupId}/serverless/{name}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“name”，minLength 从“1”减少到“0”
  • 在响应中添加了可选属性 'providerSettings/forcedDiskSizeGBLimit、providerSettings/forcedInstanceSizeName、providerSettings/forcedProviderName'
GET /api/atlas/v2/groups/{groupId}/serviceAccounts
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/serviceAccounts
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/accessList
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/accessList
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/accessList/{ipAddress}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/secrets
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/secrets/{secretId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}:invite
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/settings
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/settings
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “_id”请求属性的 minLength 从“24”减少到“0”
  • “connections/items/networking/ 访问权限/connectionId”请求属性的 minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/streams/accountDetails
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/streams/activeVpcPeeringConnections
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 在响应中添加了可选属性 'results/items/arn、results/items/errorMessage、results/items/providerAccountId'
POST /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections
Updated
  • 请求可选属性“_id”变为只读
  • 请求可选属性“interfaceEndpointId”变为只读
  • 请求可选属性“state”变为只读
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 向响应添加了可选属性“arn、errorMessage、providerAccountId”
  • 添加了新的可选请求属性“arn”
DELETE /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections/{connectionId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections/{connectionId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 向响应添加了可选属性“arn、errorMessage、providerAccountId”
GET /api/atlas/v2/groups/{groupId}/streams/vpcPeeringConnections
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/streams/vpcPeeringConnections/{id}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/streams/vpcPeeringConnections/{id}:accept
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/streams/vpcPeeringConnections/{id}:reject
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/auditLogs
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “/networking/ 访问权限/connectionId”请求属性的 minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “/networking/ 访问权限/connectionId”请求属性的 minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “_id”请求属性的 minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}:start
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}:stop
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processors
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/teams
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/teams
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “/items/teamId”请求属性的 minLength 已从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/teams/{teamId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“teamId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/teams/{teamId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“teamId”，minLength 从“24”减少到“0”
  • “teamId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/userSecurity
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/userSecurity
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/userSecurity/customerX509
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/userSecurity/ldap/userToDNMapping
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/userSecurity/ldap/verify
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/userSecurity/ldap/verify/{requestId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“requestId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/users
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/users/{userId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“userId”，minLength 从“24”减少到“0”
PUT /api/atlas/v2/groups/{groupId}/users/{userId}/roles
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“userId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}:migrate
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “destinationOrgId”请求属性的 minLength 从“24”减少到“0”
POST /api/atlas/v2/orgs
Updated
  • “federationSettingsId”请求属性的 minLength 从“24”减少到“0”
  • “名称”请求属性的 minLength 从“1”减少到“0”
  • “orgOwnerId”请求属性的 minLength 从“24”减少到“0”
DELETE /api/atlas/v2/orgs/{orgId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/orgs/{orgId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “名称”请求属性的 minLength 从“1”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/apiKeys
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/orgs/{orgId}/apiKeys
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}
Updated
  • 对于“path”请求参数“apiUserId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}
Updated
  • 对于“path”请求参数“apiUserId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}
Updated
  • 对于“path”请求参数“apiUserId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList
Updated
  • 对于“path”请求参数“apiUserId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList
Updated
  • 对于“path”请求参数“apiUserId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList/{ipAddress}
Updated
  • 对于“path”请求参数“apiUserId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList/{ipAddress}
Updated
  • 对于“path”请求参数“apiUserId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/orgs/{orgId}/billing/costExplorer/usage
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/billing/costExplorer/usage/{token}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 对于“path”请求参数“eventId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/federationSettings
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/groups
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/invites
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • “/items/teamIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
PATCH /api/atlas/v2/orgs/{orgId}/invites
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • “groupRoleAssignments/items/groupId”请求属性的 minLength 从“24”减少到“0”
  • “teamIds/items/”请求属性的 minLength 从“24”减少到“0”
  • 从请求属性“teamIds/items/”中删除了模式“^([af0-9]{24})$”
  • “teamIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
POST /api/atlas/v2/orgs/{orgId}/invites
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • “groupRoleAssignments/items/groupId”请求属性的 minLength 从“24”减少到“0”
  • “teamIds/items/”请求属性的 minLength 从“24”减少到“0”
  • 从请求属性“teamIds/items/”中删除了模式“^([af0-9]{24})$”
  • “teamIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
DELETE /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
Updated
  • 对于“path”请求参数“invitationId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • “teamIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
PATCH /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
Updated
  • 对于“path”请求参数“invitationId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • “groupRoleAssignments/items/groupId”请求属性的 minLength 从“24”减少到“0”
  • “teamIds/items/”请求属性的 minLength 从“24”减少到“0”
  • 从请求属性“teamIds/items/”中删除了模式“^([af0-9]{24})$”
  • “teamIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
GET /api/atlas/v2/orgs/{orgId}/invoices
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
Updated
  • 对于“path”请求参数“invoiceId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}/csv
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}/lineItems:search
Updated
  • 对于“path”请求参数“invoiceId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/liveMigrations/availableProjects
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/orgs/{orgId}/liveMigrations/linkTokens
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/orgs/{orgId}/liveMigrations/linkTokens
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/nonCompliantResources
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/resourcePolicies
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • 在响应中添加了可选属性“/items/description”
POST /api/atlas/v2/orgs/{orgId}/resourcePolicies
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • 在响应中添加了可选属性“description”
  • 添加了新的可选请求属性“description”
DELETE /api/atlas/v2/orgs/{orgId}/resourcePolicies/{resourcePolicyId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“resourcePolicyId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/resourcePolicies/{resourcePolicyId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“resourcePolicyId”，minLength 从“24”减少到“0”
  • 在响应中添加了可选属性“description”
PATCH /api/atlas/v2/orgs/{orgId}/resourcePolicies/{resourcePolicyId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“resourcePolicyId”，minLength 从“24”减少到“0”
  • 在响应中添加了可选属性“description”
  • 添加了新的可选请求属性“description”
POST /api/atlas/v2/orgs/{orgId}/resourcePolicies:validate
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • 在响应中添加了可选属性“description”
  • 添加了新的可选请求属性“description”
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/orgs/{orgId}/serviceAccounts
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/accessList
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/accessList
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/accessList/{ipAddress}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/groups
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/secrets
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/secrets/{secretId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/settings
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/orgs/{orgId}/settings
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/teams
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/orgs/{orgId}/teams
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/teams/byName/{teamName}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/orgs/{orgId}/teams/{teamId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“teamId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/teams/{teamId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“teamId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/orgs/{orgId}/teams/{teamId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“teamId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“teamId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“teamId”，minLength 从“24”减少到“0”
  • “/items/ ID”请求属性的 minLength 已从“24”减少到“0”
DELETE /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users/{userId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“teamId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“userId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/users
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/orgs/{orgId}/users/{userId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“userId”，minLength 从“24”减少到“0”
PUT /api/atlas/v2/orgs/{orgId}/users/{userId}/roles
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“userId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/users
Updated
  • “ID”请求属性的 minLength 已从“24”减少到“0”
GET /api/atlas/v2/users/{userId}
Updated
  • 对于“path”请求参数“userId”，minLength 从“24”减少到“0”

2025 年 2 月 05 日发布

POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives
Updated
  • 已将新的“GCP”枚举值添加到请求属性“dataProcessRegion/cloudProvider”中

2025 年 1 月 24 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在“results/items/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”响应属性中添加了新的“PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED”枚举值
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 已将新的 'PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED'枚举值添加到 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName' 响应属性
  • 已将新的“PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED”枚举值添加到请求属性“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 已将新的 'PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED'枚举值添加到 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName' 响应属性
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 已将新的 'PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED'枚举值添加到 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName' 响应属性
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 已将新的 'PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED'枚举值添加到 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName' 响应属性
  • 已将新的“PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED”枚举值添加到请求属性“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 在“results/items/oneOf[subschema #3: Host Alerts]/eventTypeName”响应属性中添加了新的“PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED”枚举值
  • 在“results/items/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName”响应属性中添加了新的“PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 在“results/items/oneOf[subschema #3: Host Alerts]/eventTypeName”响应属性中添加了新的“PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED”枚举值
  • 在“results/items/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName”响应属性中添加了新的“PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 已将新的 'PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED'枚举值添加到 '/oneOf[subschema #3: Host Alerts]/eventTypeName' 响应属性
  • 将新的 'PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED'枚举值添加到 '/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName' 响应属性
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 已将新的 'PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED'枚举值添加到 '/oneOf[subschema #3: Host Alerts]/eventTypeName' 响应属性
  • 将新的 'PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED'枚举值添加到 '/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName' 响应属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 在“results/items/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”响应属性中添加了新的“PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED”枚举值
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 在“results/items/oneOf[subschema #12: Host Events]/eventTypeName”响应属性中添加了新的“PUSH_BASED_LOG_EXPORT_DROPPED_LOG”、“PUSH_BASED_LOG_EXPORT_RESUMED”和“PUSH_BASED_LOG_EXPORT_STOPPED”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 在 '/oneOf[subschema #12: Host Events]/eventTypeName' 响应属性中添加了新的 'PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_RESUMED、PUSH_BASED_LOG_EXPORT_STOPPED'枚举值

2025 年 1 月 22 日发布

GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 在“results/items/oneOf[subschema #14: NDS Audits]/eventTypeName”响应属性中添加了新的“CLUSTER_IP_MIGRATED_FINAL_ROUND、CLUSTER_IP_MIGRATED_FIRST_ROUND、CLUSTER_IP_MIGRATED_SECOND_ROUND、CLUSTER_IP_ROLLED_BACK”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 在 '/oneOf[subschema #14: NDS Audits]/eventTypeName' 响应属性中添加了新的 'CLUSTER_IP_MIGRATED_FINAL_ROUND、CLUSTER_IP_MIGRATED_FIRST_ROUND、CLUSTER_IP_MIGRATED_SECOND_ROUND、CLUSTER_IP_ROLLED_BACK'枚举值

2025 年 1 月 21 日发布

GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将新的 'CLUSTER_MIGRATE_BACK_TO_AWS_MANAGED_IP_REQUESTED'枚举值添加到 'results/items/oneOf[subschema #14: NDS Audits]/eventTypeName' 响应属性
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 将新的 'CLUSTER_MIGRATE_BACK_TO_AWS_MANAGED_IP_REQUESTED'枚举值添加到 '/oneOf[subschema #14: NDS Audits]/eventTypeName' 响应属性

2025 年 1 月 13 日发布

GET /api/atlas/v2/groups/{groupId}/users
Updated
  • 端点已重新激活

2025 年 1 月 10 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • “results/items/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret”响应的属性类型/格式已从将状态 '200' 的 'string'/'password' 更改为 'string'/''
  • “results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret”响应的属性类型/格式从“string”/ 更改为针对状态“200”，将“password”更改为“string”/“
  • “results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret”响应的属性类型/格式从“string”/ 'password' to 'string'/'' for status '200'
  • “results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret”响应的属性类型/格式从“string”/“password”更改为' 为 'string'/'' 以获取状态 '200'
  • 'results/items/oneOf[subschema #15: Stream Processor Alert Configuration -> subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'状态为“200”的响应的属性类型/格式从“字符串”/“密码”更改为“字符串”/“”
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/' 更改为针对状态“200”，将“password”更改为“string”/“
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret' 响应的属性类型/格式从 'string'/' 更改为针对状态“200”，将“password”更改为“string”/“
  • “results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret”响应的属性类型/格式从“string”/ 'password' to 'string'/'' for status '200'
  • “results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret”响应的属性类型/格式从“string”/ 更改为针对状态“200”，将“password”更改为“string”/“
  • “results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret”响应的属性类型/格式从“string”/“password”更改为' 为 'string'/'' 以获取状态 '200'
  • “results/items/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret”响应的属性类型/格式从“string”/ 'password' to 'string'/'' for status '200'
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/ 更改为针对状态“200”，将“password”更改为“string”/“
  • “results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret”响应的属性类型/格式从“string”/“password”更改为' 为 'string'/'' 以获取状态 '200'
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/' 更改为针对状态“200”，将“password”更改为“string”/“
  • 已从响应的“results/items/”响应属性“oneOf”列表中删除“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到响应的“results/items/”响应属性“oneOf”列表中
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 已从请求正文“oneOf”列表中删除“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”
  • '/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'请求属性类型/格式从 'string' 变更/'password' to 'string'/''
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为'string'/''
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'请求属性类型/格式从 'string'/'password' 变更to 'string'/''
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为 ' string'/''
  • '/oneOf[subschema #15: Stream Processor Alert Configuration -> subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'请求属性类型/format 从 'string'/'password' 更改为 'string'/''
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为'string'/''
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为'string'/''
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret'请求属性类型/格式从 'string'/'password' 变更为to 'string'/''
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为'string'/''
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为 ' string'/''
  • “/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret”请求属性类型/格式从“string”/“password”更改为to 'string'/''
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为'string'/''
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为 ' string'/''
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为'string'/''
  • '/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string' 变更/'password' to 'string'/'' for status '200'
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 'string'/'password'为 'string'/'' 以获取状态 '200'
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 ' string'/'' for status '200'
  • '/oneOf[subschema #15: Stream Processor Alert Configuration -> subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/format 已从 'string'/'password' 更改为 'string'/''（状态为 '200'）
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 'string'/'password'为 'string'/'' 以获取状态 '200'
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 ' string'/'' for status '200'
  • '/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 'string'/'password'为 'string'/'' 以获取状态 '200'
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 ' string'/'' for status '200'
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • 已从响应的响应正文“oneOf”列表中删除“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到请求正文“oneOf”列表
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • '/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string' 变更/'password' to 'string'/'' for status '200'
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 'string'/'password'为 'string'/'' 以获取状态 '200'
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 ' string'/'' for status '200'
  • '/oneOf[subschema #15: Stream Processor Alert Configuration -> subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/format 已从 'string'/'password' 更改为 'string'/''（状态为 '200'）
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 'string'/'password'为 'string'/'' 以获取状态 '200'
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 ' string'/'' for status '200'
  • '/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 'string'/'password'为 'string'/'' 以获取状态 '200'
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 ' string'/'' for status '200'
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • 已从响应的响应正文“oneOf”列表中删除“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • '/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string' 变更/'password' to 'string'/'' for status '200'
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 'string'/'password'为 'string'/'' 以获取状态 '200'
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 ' string'/'' for status '200'
  • '/oneOf[subschema #15: Stream Processor Alert Configuration -> subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/format 已从 'string'/'password' 更改为 'string'/''（状态为 '200'）
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 'string'/'password'为 'string'/'' 以获取状态 '200'
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 ' string'/'' for status '200'
  • '/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 'string'/'password'为 'string'/'' 以获取状态 '200'
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 ' string'/'' for status '200'
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • 已从响应的响应正文“oneOf”列表中删除“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 已从请求正文“oneOf”列表中删除“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”
  • '/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'请求属性类型/格式从 'string' 变更/'password' to 'string'/''
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为'string'/''
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'请求属性类型/格式从 'string'/'password' 变更to 'string'/''
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为 ' string'/''
  • '/oneOf[subschema #15: Stream Processor Alert Configuration -> subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'请求属性类型/format 从 'string'/'password' 更改为 'string'/''
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为'string'/''
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为'string'/''
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret'请求属性类型/格式从 'string'/'password' 变更为to 'string'/''
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为'string'/''
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为 ' string'/''
  • “/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret”请求属性类型/格式从“string”/“password”更改为to 'string'/''
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为'string'/''
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为 ' string'/''
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为'string'/''
  • '/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string' 变更/'password' to 'string'/'' for status '200'
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 'string'/'password'为 'string'/'' 以获取状态 '200'
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 ' string'/'' for status '200'
  • '/oneOf[subschema #15: Stream Processor Alert Configuration -> subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/format 已从 'string'/'password' 更改为 'string'/''（状态为 '200'）
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 'string'/'password'为 'string'/'' 以获取状态 '200'
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 ' string'/'' for status '200'
  • '/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 'string'/'password'为 'string'/'' 以获取状态 '200'
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 ' string'/'' for status '200'
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • 已从响应的响应正文“oneOf”列表中删除“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到请求正文“oneOf”列表
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 从响应的“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表中删除了“subschema #11: Flex Metric Event Types”
  • 将“subschema #11: Flex Metric Event Types”添加到“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 从响应的“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表中删除了“subschema #11: Flex Metric Event Types”
  • 将“subschema #11: Flex Metric Event Types”添加到“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 从响应的“/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表中删除了“subschema #11: Flex Metric Event Types”
  • 将“subschema #11: Flex Metric Event Types”添加到“/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表中
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 从响应的“/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表中删除了“subschema #11: Flex Metric Event Types”
  • 将“subschema #11: Flex Metric Event Types”添加到“/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • “results/items/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret”响应的属性类型/格式已从将状态 '200' 的 'string'/'password' 更改为 'string'/''
  • “results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret”响应的属性类型/格式从“string”/ 更改为针对状态“200”，将“password”更改为“string”/“
  • “results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret”响应的属性类型/格式从“string”/ 'password' to 'string'/'' for status '200'
  • “results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret”响应的属性类型/格式从“string”/“password”更改为' 为 'string'/'' 以获取状态 '200'
  • 'results/items/oneOf[subschema #15: Stream Processor Alert Configuration -> subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'状态为“200”的响应的属性类型/格式从“字符串”/“密码”更改为“字符串”/“”
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/' 更改为针对状态“200”，将“password”更改为“string”/“
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret' 响应的属性类型/格式从 'string'/' 更改为针对状态“200”，将“password”更改为“string”/“
  • “results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret”响应的属性类型/格式从“string”/ 'password' to 'string'/'' for status '200'
  • “results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret”响应的属性类型/格式从“string”/ 更改为针对状态“200”，将“password”更改为“string”/“
  • “results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret”响应的属性类型/格式从“string”/“password”更改为' 为 'string'/'' 以获取状态 '200'
  • “results/items/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret”响应的属性类型/格式从“string”/ 'password' to 'string'/'' for status '200'
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/ 更改为针对状态“200”，将“password”更改为“string”/“
  • “results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret”响应的属性类型/格式从“string”/“password”更改为' 为 'string'/'' 以获取状态 '200'
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/' 更改为针对状态“200”，将“password”更改为“string”/“
  • 已从响应的“results/items/”响应属性“oneOf”列表中删除“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到响应的“results/items/”响应属性“oneOf”列表中
POST /api/atlas/v2/groups/{groupId}/apiKeys
Updated
  • 删除了请求属性“roles/items/”的枚举值“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值添加到请求属性“roles/items/”
POST /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
Updated
  • 删除了请求属性“/items/roles/items/”的枚举值“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值添加到请求属性“/items/roles/items/”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 删除了“specs/items/instanceSize”响应属性中的“S40_STORAGE_NVME、S50_STORAGE_NVME、S60_STORAGE_NVME、S80_STORAGE_NVME、S90_STORAGE_NVME”枚举值
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 删除了“specs/items/instanceSize”响应属性中的“S40_STORAGE_NVME、S50_STORAGE_NVME、S60_STORAGE_NVME、S80_STORAGE_NVME、S90_STORAGE_NVME”枚举值
  • 删除了请求属性“specs/items/instanceSize”的枚举值“S40_STORAGE_NVME、S50_STORAGE_NVME、S60_STORAGE_NVME、S80_STORAGE_NVME、S90_STORAGE_NVME”
  • 在请求属性“specs/items/instanceSize”中添加了新的“S40_STORAGE_NVME、S50_STORAGE_NVME、S60_STORAGE_NVME、S80_STORAGE_NVME、S90_STORAGE_NVME”枚举值
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 删除了“specs/items/instanceSize”响应属性中的“S40_STORAGE_NVME、S50_STORAGE_NVME、S60_STORAGE_NVME、S80_STORAGE_NVME、S90_STORAGE_NVME”枚举值
  • 删除了请求属性“specs/items/instanceSize”的枚举值“S40_STORAGE_NVME、S50_STORAGE_NVME、S60_STORAGE_NVME、S80_STORAGE_NVME、S90_STORAGE_NVME”
  • 在“specs/items/instanceSize”响应属性中添加了新的“S40_STORAGE_NVME、S50_STORAGE_NVME、S60_STORAGE_NVME、S80_STORAGE_NVME、S90_STORAGE_NVME”枚举值
  • 在请求属性“specs/items/instanceSize”中添加了新的“S40_STORAGE_NVME、S50_STORAGE_NVME、S60_STORAGE_NVME、S80_STORAGE_NVME、S90_STORAGE_NVME”枚举值
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 从响应的“results/items/oneOf[subschema #1: Any other Events]/eventTypeName”响应属性“oneOf”列表中删除了“subschema #27: Flex Metric Event Types”
  • 从“results/items/oneOf[subschema #12: Host Events]/eventTypeName”响应属性中删除了“HOST_X509_CERTIFICATE_CERTIFICATE_GENERATED_FOR_SUPPORT_ACCESS”枚举值
  • 将“subschema #27: Flex Metric Event Types”添加到“results/items/oneOf[subschema #1: Any other Events]/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 从响应的“/oneOf[subschema #1: Any other Events]/eventTypeName”响应属性“oneOf”列表中删除了“subschema #27: Flex Metric Event Types”
  • 从“/oneOf[subschema #12: Host Events]/eventTypeName”响应属性中删除了“HOST_X509_CERTIFICATE_CERTIFICATE_GENERATED_FOR_SUPPORT_ACCESS”枚举值
  • 将“subschema #27: Flex Metric Event Types”添加到“/oneOf[subschema #1: Any other Events]/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/serviceAccounts
Updated
  • 删除了“results/items/roles/items/”响应属性中的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值
  • 在 'results/items/roles/items/' 响应属性中添加了新的 'GROUP_BACKUP_MANAGER, GROUP_OBSERVABILITY_VIEWER'枚举值
POST /api/atlas/v2/groups/{groupId}/serviceAccounts
Updated
  • 删除了“roles/items/”响应属性中的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值
  • 删除了请求属性“roles/items/”的枚举值“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”
  • 在“roles/items/”响应属性中添加了新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值添加到请求属性“roles/items/”
GET /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
Updated
  • 删除了“roles/items/”响应属性中的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值
  • 在“roles/items/”响应属性中添加了新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值
PATCH /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
Updated
  • 删除了“roles/items/”响应属性中的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值
  • 删除了请求属性“roles/items/”的枚举值“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”
  • 在“roles/items/”响应属性中添加了新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值添加到请求属性“roles/items/”
POST /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}:invite
Updated
  • 删除了“roles/items/”响应属性中的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值
  • 删除了请求属性“/items/roles/items/”的枚举值“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”
  • 在“roles/items/”响应属性中添加了新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值添加到请求属性“/items/roles/items/”
GET /api/atlas/v2/groups/{groupId}/streams/activeVpcPeeringConnections
已交
  • API路径已删除但未弃用
  • 已添加端点

2025 年 1 月 08 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到响应的“results/items/”响应属性“oneOf”列表中
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到请求正文“oneOf”列表
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到请求正文“oneOf”列表
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 将“subschema #11: Flex Metric Event Types”添加到“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 将“subschema #11: Flex Metric Event Types”添加到“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“subschema #11: Flex Metric Event Types”添加到“/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表中
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“subschema #11: Flex Metric Event Types”添加到“/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到响应的“results/items/”响应属性“oneOf”列表中
POST /api/atlas/v2/groups/{groupId}/apiKeys
Updated
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值添加到请求属性“roles/items/”
POST /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
Updated
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值添加到请求属性“/items/roles/items/”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 在请求属性“specs/items/instanceSize”中添加了新的“S40_STORAGE_NVME、S50_STORAGE_NVME、S60_STORAGE_NVME、S80_STORAGE_NVME、S90_STORAGE_NVME”枚举值
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 在“specs/items/instanceSize”响应属性中添加了新的“S40_STORAGE_NVME、S50_STORAGE_NVME、S60_STORAGE_NVME、S80_STORAGE_NVME、S90_STORAGE_NVME”枚举值
  • 在请求属性“specs/items/instanceSize”中添加了新的“S40_STORAGE_NVME、S50_STORAGE_NVME、S60_STORAGE_NVME、S80_STORAGE_NVME、S90_STORAGE_NVME”枚举值
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将“subschema #27: Flex Metric Event Types”添加到“results/items/oneOf[subschema #1: Any other Events]/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 将“subschema #27: Flex Metric Event Types”添加到“/oneOf[subschema #1: Any other Events]/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/serviceAccounts
Updated
  • 在 'results/items/roles/items/' 响应属性中添加了新的 'GROUP_BACKUP_MANAGER, GROUP_OBSERVABILITY_VIEWER'枚举值
POST /api/atlas/v2/groups/{groupId}/serviceAccounts
Updated
  • 在“roles/items/”响应属性中添加了新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值添加到请求属性“roles/items/”
GET /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
Updated
  • 在“roles/items/”响应属性中添加了新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值
PATCH /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
Updated
  • 在“roles/items/”响应属性中添加了新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值添加到请求属性“roles/items/”
POST /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}:invite
Updated
  • 在“roles/items/”响应属性中添加了新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值添加到请求属性“/items/roles/items/”
GET /api/atlas/v2/groups/{groupId}/streams/activeVpcPeeringConnections
已交
  • 已添加端点

2025 年 1 月 03 日发布

GET /api/atlas/v2/groups/{groupId}/ipAddresses
Updated
  • 在响应中添加了可选属性“services/clusters/items/futureInbound, services/clusters/items/futureOutbound”

2025 年 1 月 01 日发布

GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2025-01-01”
PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2025-01-01”

2024 年 12 月 19 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“QUERY_SPILL_TO_DISK_DURING_SORT”鉴别器映射键添加到“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([ af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([ af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId”响应的属性模式'^(已添加 [af0-9]{24})$'
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: 副本集阈值警报配置]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: 副本集阈值警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #12: 副本集阈值警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId”响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • “results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId”响应的属性模式“^([af0- 9]{24})$' 已添加
  • “results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId”响应的属性模式“^([af0- 9]{24})$' 已添加
  • “results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId”响应的属性模式“^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • “results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId”响应的属性模式“^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • “results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • “results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • “results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: 账单阈值警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: 账单阈值警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • “results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • “results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #12: User notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • “results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • “results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • “results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 在“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #3: Data Protection Event Types]/”响应属性中添加了新的“CPS_DATA_PROTECTION_APPROVED_FOR_DISABLEMENT”枚举值
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema#10:SMSNotification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema #11: Team notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema#12:UserNotification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema #13: VictorOpsNotification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema #14: Webhook notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema#1:DatadogNotification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema#2:EmailNotification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema#3:GroupNotification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema #4: HipChat notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema#7:OrgNotification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema#9: Slack ]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #10: SMS notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #11: Team notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #12: User notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #13: VictorOps notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #14: Webhook notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #1: Datadog notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #2: Email notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #3: Group notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #4: HipChat 通知]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #7: 组织通知]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #10: 短信通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #11: Team notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #12: User notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #13: VictorOps 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #14: Webhook 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #1: Datadog 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #2: 电子邮件通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #3: 群组通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #5: Microsoft Teams 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #8: PagerDuty 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #10: 短信通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #11: 团队通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #12: 用户通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #13: VictorOps 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #14: Webhook 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #1: Datadog 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #2: 电子邮件通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #3: 群组通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #4: HipChat 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #5: Microsoft Teams 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #6: OpsGenie notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #7: 组织通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #8: PagerDuty 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #9: Slack notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #10: SMS notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #11: Team notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #12: User notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #13: VictorOps notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #14: Webhook notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #1: Datadog notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #2: Email notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #3: Group notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #9: Slack notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #10: SMS notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #11: Team notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #12: User notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #13: VictorOps notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #14: Webhook notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #1: Datadog notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #2: Email notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #3: Group notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #4: HipChat 通知]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #7: 组织通知]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #10: SMS notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #11: Team notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #12: User notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #13: VictorOps notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #14: Webhook notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #1: Datadog notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #2: Email notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #3: Group notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #10: 短信通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #11: Team notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #12: User notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #13: VictorOps 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #14: Webhook 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #1: Datadog 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #2: 电子邮件通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #3: 群组通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #5: Microsoft Teams 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #8: PagerDuty 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #10: SMS notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #11: Team notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #12: User notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #13: VictorOps notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #14: Webhook notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #1: Datadog notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #2: Email notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #3: Group notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #10: 短信通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #11: 团队通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #12: 用户通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #13: VictorOps 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #14: Webhook 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #1: Datadog 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #2: 电子邮件通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #3: 群组通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #4: HipChat 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #5: Microsoft Teams 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #6: OpsGenie notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #7: 组织通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #8: PagerDuty 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #9: Slack notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #10: 短信通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #11: Team notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #12: User notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #13: VictorOps 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #14: Webhook 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #1: Datadog 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #2: 电子邮件通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #3: 群组通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #5: Microsoft Teams 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #8: PagerDuty 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #10: SMS notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #11: Team notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #12: User notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #13: VictorOps notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #14: Webhook notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #1: Datadog notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #2: Email notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #3: Group notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #10: 短信通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #11: 团队通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #12: 用户通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #13: VictorOps 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #14: Webhook 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #1: Datadog 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #2: 电子邮件通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #3: 群组通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #4: HipChat 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #5: Microsoft Teams 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #6: OpsGenie notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #7: 组织通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #8: PagerDuty 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #9: Slack notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #10: SMS notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #11: Team notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #12: User notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #13: VictorOps notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #14: Webhook notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #1: Datadog notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #2: Email notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #3: Group notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #9: Slack notification]/notifierId'
  • 将“QUERY_SPILL_TO_DISK_DURING_SORT”鉴别器映射键添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性
  • 将“QUERY_SPILL_TO_DISK_DURING_SORT”鉴别器映射键添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: 副本集阈值警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #3: Data Protection Event Types]/”响应属性中添加了新的“CPS_DATA_PROTECTION_APPROVED_FOR_DISABLEMENT”枚举值
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #3: Data Protection Event Types]/' 中添加了新的 'CPS_DATA_PROTECTION_APPROVED_FOR_DISABLEMENT'枚举值
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“QUERY_SPILL_TO_DISK_DURING_SORT”鉴别器映射键添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: 副本集阈值警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #3: Data Protection Event Types]/”响应属性中添加了新的“CPS_DATA_PROTECTION_APPROVED_FOR_DISABLEMENT”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“QUERY_SPILL_TO_DISK_DURING_SORT”鉴别器映射键添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: 副本集阈值警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #3: Data Protection Event Types]/”响应属性中添加了新的“CPS_DATA_PROTECTION_APPROVED_FOR_DISABLEMENT”枚举值
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema#10:SMSNotification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema #11: Team notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema#12:UserNotification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema #13: VictorOpsNotification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema #14: Webhook notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema#1:DatadogNotification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema#2:EmailNotification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema#3:GroupNotification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema #4: HipChat notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema#7:OrgNotification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema#9: Slack ]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #10: SMS notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #11: Team notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #12: User notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #13: VictorOps notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #14: Webhook notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #1: Datadog notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #2: Email notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #3: Group notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #4: HipChat 通知]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #7: 组织通知]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #10: 短信通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #11: Team notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #12: User notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #13: VictorOps 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #14: Webhook 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #1: Datadog 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #2: 电子邮件通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #3: 群组通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #5: Microsoft Teams 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #8: PagerDuty 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #10: 短信通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #11: 团队通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #12: 用户通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #13: VictorOps 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #14: Webhook 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #1: Datadog 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #2: 电子邮件通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #3: 群组通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #4: HipChat 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #5: Microsoft Teams 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #6: OpsGenie notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #7: 组织通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #8: PagerDuty 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #9: Slack notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #10: SMS notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #11: Team notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #12: User notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #13: VictorOps notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #14: Webhook notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #1: Datadog notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #2: Email notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #3: Group notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #9: Slack notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #10: SMS notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #11: Team notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #12: User notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #13: VictorOps notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #14: Webhook notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #1: Datadog notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #2: Email notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #3: Group notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #4: HipChat 通知]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #7: 组织通知]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #10: SMS notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #11: Team notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #12: User notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #13: VictorOps notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #14: Webhook notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #1: Datadog notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #2: Email notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #3: Group notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #10: 短信通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #11: Team notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #12: User notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #13: VictorOps 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #14: Webhook 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #1: Datadog 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #2: 电子邮件通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #3: 群组通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #5: Microsoft Teams 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #8: PagerDuty 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #10: SMS notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #11: Team notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #12: User notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #13: VictorOps notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #14: Webhook notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #1: Datadog notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #2: Email notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #3: Group notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #10: 短信通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #11: 团队通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #12: 用户通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #13: VictorOps 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #14: Webhook 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #1: Datadog 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #2: 电子邮件通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #3: 群组通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #4: HipChat 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #5: Microsoft Teams 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #6: OpsGenie notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #7: 组织通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #8: PagerDuty 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #9: Slack notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #10: 短信通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #11: Team notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #12: User notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #13: VictorOps 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #14: Webhook 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #1: Datadog 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #2: 电子邮件通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #3: 群组通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #5: Microsoft Teams 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #8: PagerDuty 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #10: SMS notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #11: Team notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #12: User notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #13: VictorOps notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #14: Webhook notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #1: Datadog notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #2: Email notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #3: Group notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #10: 短信通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #11: 团队通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #12: 用户通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #13: VictorOps 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #14: Webhook 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #1: Datadog 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #2: 电子邮件通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #3: 群组通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #4: HipChat 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #5: Microsoft Teams 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #6: OpsGenie notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #7: 组织通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #8: PagerDuty 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #9: Slack notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #10: SMS notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #11: Team notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #12: User notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #13: VictorOps notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #14: Webhook notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #1: Datadog notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #2: Email notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #3: Group notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #9: Slack notification]/notifierId'
  • 将“QUERY_SPILL_TO_DISK_DURING_SORT”鉴别器映射键添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性
  • 将“QUERY_SPILL_TO_DISK_DURING_SORT”鉴别器映射键添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: 副本集阈值警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #3: Data Protection Event Types]/”响应属性中添加了新的“CPS_DATA_PROTECTION_APPROVED_FOR_DISABLEMENT”枚举值
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #3: Data Protection Event Types]/' 中添加了新的 'CPS_DATA_PROTECTION_APPROVED_FOR_DISABLEMENT'枚举值
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 将“QUERY_SPILL_TO_DISK_DURING_SORT”鉴别器映射键添加到“results/items/oneOf[subschema #4: Host Metric Alerts]/”响应属性
  • 在“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #15: Data Protection Event Types]/”响应属性中添加了新的“CPS_DATA_PROTECTION_APPROVED_FOR_DISABLEMENT”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 将“QUERY_SPILL_TO_DISK_DURING_SORT”鉴别器映射键添加到“results/items/oneOf[subschema #4: Host Metric Alerts]/”响应属性
  • 在“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #15: Data Protection Event Types]/”响应属性中添加了新的“CPS_DATA_PROTECTION_APPROVED_FOR_DISABLEMENT”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“QUERY_SPILL_TO_DISK_DURING_SORT”鉴别器映射键添加到“/oneOf[subschema #4: Host Metric Alerts]/”响应属性
  • 在“/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #15: Data Protection Event Types]/”响应属性中添加了新的“CPS_DATA_PROTECTION_APPROVED_FOR_DISABLEMENT”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“QUERY_SPILL_TO_DISK_DURING_SORT”鉴别器映射键添加到“/oneOf[subschema #4: Host Metric Alerts]/”响应属性
  • 在“/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #15: Data Protection Event Types]/”响应属性中添加了新的“CPS_DATA_PROTECTION_APPROVED_FOR_DISABLEMENT”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 将“QUERY_SPILL_TO_DISK_DURING_SORT”鉴别器映射键添加到“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([ af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([ af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId”响应的属性模式'^(已添加 [af0-9]{24})$'
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: 副本集阈值警报配置]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: 副本集阈值警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #12: 副本集阈值警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId”响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • “results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId”响应的属性模式“^([af0- 9]{24})$' 已添加
  • “results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId”响应的属性模式“^([af0- 9]{24})$' 已添加
  • “results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId”响应的属性模式“^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • “results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId”响应的属性模式“^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • “results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • “results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • “results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: 账单阈值警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: 账单阈值警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • “results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • “results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #12: User notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • “results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • “results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • “results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 在“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #3: Data Protection Event Types]/”响应属性中添加了新的“CPS_DATA_PROTECTION_APPROVED_FOR_DISABLEMENT”枚举值
GET /api/atlas/v2/groups/{groupId}/backup/exportBuckets
Updated
  • “results/items/tenantId”响应的属性模式为“^[0-9a-fA-F]{8}\b-[0-9a-fA-F” ]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{12}$' 已删除
POST /api/atlas/v2/groups/{groupId}/backup/exportBuckets
Updated
  • “/tenantId”请求属性的 minLength 从“36”减少到“0”
  • 删除了模式'^[0-9a-fA-F]{8}\b-[0-9a-fA-F]{4} \b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b -[0-9a-fA-F]{12}$'（来自请求属性“/tenantId”）
  • “/tenantId”响应的属性模式“^[0-9a-fA-F]{8}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{12}$' 已删除
GET /api/atlas/v2/groups/{groupId}/backup/exportBuckets/{exportBucketId}
Updated
  • “/tenantId”响应的属性模式“^[0-9a-fA-F]{8}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{12}$' 已删除
DELETE /api/atlas/v2/groups/{groupId}/backupCompliancePolicy
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/backupCompliancePolicy
Updated
  • 在响应中添加了可选属性“deletable”
PUT /api/atlas/v2/groups/{groupId}/backupCompliancePolicy
Updated
  • 在响应中添加了可选属性“deletable”
GET /api/atlas/v2/groups/{groupId}/cloudProviderAccess
Updated
  • “azureServicePrincipals/items/atlasAzureAppId”响应的属性模式“^[0-9a-fA-F]{8}\b-[0-9a-fA-F” ]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{12}$' 已删除
  • “azureServicePrincipals/items/servicePrincipalId”响应的属性模式为“^[0-9a-fA-F]{8}\b-[0-9a-fA-F” ]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{12}$' 已删除
  • “azureServicePrincipals/items/tenantId”响应的属性模式为“^[0-9a-fA-F]{8}\b-[0-9a-fA-F” ]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{12}$' 已删除
POST /api/atlas/v2/groups/{groupId}/cloudProviderAccess
Updated
  • 将模式“^([af0-9]{24})$”添加到请求属性“/roleId”
  • “/atlasAzureAppId”请求属性的 minLength 已从“32”减少到“0”
  • “/servicePrincipalId”请求属性的 minLength 已从“32”减少到“0”
  • “/tenantId”请求属性的 minLength 从“32”减少到“0”
  • 删除了模式'^[0-9a-fA-F]{8}\b-[0-9a-fA-F]{4} \b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b -[0-9a-fA-F]{12}$'（来自请求属性“/atlasAzureAppId”）
  • 删除了模式'^[0-9a-fA-F]{8}\b-[0-9a-fA-F]{4} \b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b -[0-9a-fA-F]{12}$'（来自请求属性“/servicePrincipalId”）
  • 删除了模式'^[0-9a-fA-F]{8}\b-[0-9a-fA-F]{4} \b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b -[0-9a-fA-F]{12}$'（来自请求属性“/tenantId”）
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 已添加“copySettings/items/zoneId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“deleteCopiedBackups/items/zoneId”响应的属性模式“^([af0-9]{24})$”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 已添加“copySettings/items/zoneId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“deleteCopiedBackups/items/zoneId”响应的属性模式“^([af0-9]{24})$”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 已将模式“^([af0-9]{24})$”添加到请求属性“copySettings/items/zoneId”
  • 已将模式“^([af0-9]{24})$”添加到请求属性“deleteCopiedBackups/items/zoneId”
  • 已添加“copySettings/items/zoneId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“deleteCopiedBackups/items/zoneId”响应的属性模式“^([af0-9]{24})$”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • 已添加“clusterId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“groupId”响应的属性模式“^([af0-9]{24})$”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • 已添加“clusterId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“clusterId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“groupId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“groupId”响应的属性模式“^([af0-9]{24})$”
PUT /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • 已添加“clusterId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“clusterId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“groupId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“groupId”响应的属性模式“^([af0-9]{24})$”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/unpin
Updated
  • 已添加“clusterId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“groupId”响应的属性模式“^([af0-9]{24})$”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites
Updated
  • 已添加“customZoneMapping/additionalProperties/”响应的属性模式“^([af0-9]{24})$”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/customZoneMapping
Updated
  • 已添加“customZoneMapping/additionalProperties/”响应的属性模式“^([af0-9]{24})$”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/customZoneMapping
Updated
  • 已添加“customZoneMapping/additionalProperties/”响应的属性模式“^([af0-9]{24})$”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/managedNamespaces
Updated
  • 已添加“customZoneMapping/additionalProperties/”响应的属性模式“^([af0-9]{24})$”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/managedNamespaces
Updated
  • 已添加“customZoneMapping/additionalProperties/”响应的属性模式“^([af0-9]{24})$”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/{clusterView}/collStats/namespaces
Updated
  • 已添加“groupId”响应的属性模式“^([af0-9]{24})$”
GET /api/atlas/v2/groups/{groupId}/dataFederation
Updated
  • 已添加“/items/cloudProviderConfig/ Amazon Web Services/roleId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“/items/cloudProviderConfig/ Azure/roleId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“/items/cloudProviderConfig/ GCP/roleId”响应的属性模式“^([af0-9]{24})$”
POST /api/atlas/v2/groups/{groupId}/dataFederation
Updated
  • 将模式“^([af0-9]{24})$”添加到请求属性“cloudProviderConfig/ Amazon Web Services/roleId”
  • 已将模式“^([af0-9]{24})$”添加到请求属性“cloudProviderConfig/ Azure/roleId”
  • 已将模式“^([af0-9]{24})$”添加到请求属性“cloudProviderConfig/ GCP/roleId”
  • 已添加“cloudProviderConfig/ Amazon Web Services/roleId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“cloudProviderConfig/ Azure/roleId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“cloudProviderConfig/ GCP/roleId”响应的属性模式“^([af0-9]{24})$”
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 已添加“cloudProviderConfig/ Amazon Web Services/roleId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“cloudProviderConfig/ Azure/roleId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“cloudProviderConfig/ GCP/roleId”响应的属性模式“^([af0-9]{24})$”
PATCH /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 将模式“^([af0-9]{24})$”添加到请求属性“cloudProviderConfig/ Amazon Web Services/roleId”
  • 已将模式“^([af0-9]{24})$”添加到请求属性“cloudProviderConfig/ Azure/roleId”
  • 已将模式“^([af0-9]{24})$”添加到请求属性“cloudProviderConfig/ GCP/roleId”
  • 已添加“cloudProviderConfig/ Amazon Web Services/roleId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“cloudProviderConfig/ Azure/roleId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“cloudProviderConfig/ GCP/roleId”响应的属性模式“^([af0-9]{24})$”
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将“QUERY_SPILL_TO_DISK_DURING_SORT”鉴别器映射键添加到“results/items/oneOf[subschema #13: Host Metric Events]/”响应属性
  • Added the new 'ATLAS_MAINTENANCE_PROTECTED_HOURS_CREATED, ATLAS_MAINTENANCE_PROTECTED_HOURS_MODIFIED, ATLAS_MAINTENANCE_PROTECTED_HOURS_REMOVED, CLUSTER_CANCELING_SHARD_DRAIN_REQUESTED, PROJECT_SCHEDULED_MAINTENANCE_OUTSIDE_OF_PROTECTED_HOURS' 枚举 values to the 'results/items/oneOf[subschema #14: NDS Audits]/eventTypeName' response 属性
  • 在“results/items/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #6: CPS Backup Compliance Policy Event Types]/”响应属性中添加了新的“CPS_DATA_PROTECTION_APPROVED_FOR_DISABLEMENT”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 将“QUERY_SPILL_TO_DISK_DURING_SORT”鉴别器映射键添加到“/oneOf[subschema #13: Host Metric Events]/”响应属性
  • Added the new 'ATLAS_MAINTENANCE_PROTECTED_HOURS_CREATED, ATLAS_MAINTENANCE_PROTECTED_HOURS_MODIFIED, ATLAS_MAINTENANCE_PROTECTED_HOURS_REMOVED, CLUSTER_CANCELING_SHARD_DRAIN_REQUESTED, PROJECT_SCHEDULED_MAINTENANCE_OUTSIDE_OF_PROTECTED_HOURS' 枚举 values to the '/oneOf[subschema #14: NDS Audits]/eventTypeName' response 属性
  • 在“/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #6: CPS Backup Compliance Policy Event Types]/”响应属性中添加了新的“CPS_DATA_PROTECTION_APPROVED_FOR_DISABLEMENT”枚举值
POST /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/restoreJobs
Updated
  • 添加了新的可选请求属性“targetProjectId”
GET /api/atlas/v2/groups/{groupId}/peers
Updated
  • “results/items/oneOf[subschema #2: Azure]/azureDirectoryId”响应的属性模式“^[0-9a-fA-F]{8}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0 -9a-fA-F]{4}\b-[0-9a-fA-F]{12}$' 已删除
  • “results/items/oneOf[subschema #2: Azure]/azureSubscriptionId”响应的属性模式“^[0-9a-fA-F]{8}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0 -9a-fA-F]{4}\b-[0-9a-fA-F]{12}$' 已删除
POST /api/atlas/v2/groups/{groupId}/peers
Updated
  • '/oneOf[subschema #2: Azure]/azureDirectoryId'请求属性的 minLength 从 '32' 减少到 '0'
  • '/oneOf[subschema #2: Azure]/azureSubscriptionId'请求属性的 minLength 从 '32' 减少到 '0'
  • 删除了模式'^[0-9a-fA-F]{8}\b-[0-9a-fA-F]{4} \b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b -[0-9a-fA-F]{12}$'（来自请求属性'/oneOf[subschema #2: Azure]/azureDirectoryId'）
  • 删除了模式'^[0-9a-fA-F]{8}\b-[0-9a-fA-F]{4} \b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b -[0-9a-fA-F]{12}$'（来自请求属性'/oneOf[subschema #2: Azure]/azureSubscriptionId'）
  • “/oneOf[subschema #2: Azure]/azureDirectoryId”响应的属性模式“^[0-9a-fA-F]{8}\b-[0-” 9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{12}$' 已删除
  • “/oneOf[subschema #2: Azure]/azureSubscriptionId”响应的属性模式“^[0-9a-fA-F]{8}\b-[0-” 9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{12}$' 已删除
GET /api/atlas/v2/groups/{groupId}/peers/{peerId}
Updated
  • “/oneOf[subschema #2: Azure]/azureDirectoryId”响应的属性模式“^[0-9a-fA-F]{8}\b-[0-” 9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{12}$' 已删除
  • “/oneOf[subschema #2: Azure]/azureSubscriptionId”响应的属性模式“^[0-9a-fA-F]{8}\b-[0-” 9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{12}$' 已删除
PATCH /api/atlas/v2/groups/{groupId}/peers/{peerId}
Updated
  • '/oneOf[subschema #2: Azure]/azureDirectoryId'请求属性的 minLength 从 '32' 减少到 '0'
  • '/oneOf[subschema #2: Azure]/azureSubscriptionId'请求属性的 minLength 从 '32' 减少到 '0'
  • 删除了模式'^[0-9a-fA-F]{8}\b-[0-9a-fA-F]{4} \b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b -[0-9a-fA-F]{12}$'（来自请求属性'/oneOf[subschema #2: Azure]/azureDirectoryId'）
  • 删除了模式'^[0-9a-fA-F]{8}\b-[0-9a-fA-F]{4} \b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b -[0-9a-fA-F]{12}$'（来自请求属性'/oneOf[subschema #2: Azure]/azureSubscriptionId'）
  • “/oneOf[subschema #2: Azure]/azureDirectoryId”响应的属性模式“^[0-9a-fA-F]{8}\b-[0-” 9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{12}$' 已删除
  • “/oneOf[subschema #2: Azure]/azureSubscriptionId”响应的属性模式“^[0-9a-fA-F]{8}\b-[0-” 9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{12}$' 已删除
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/collStats/namespaces
Updated
  • 已添加“groupId”响应的属性模式“^([af0-9]{24})$”
GET /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 已添加“iamRoleId”响应的属性模式“^([af0-9]{24})$”
PATCH /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 已将模式“^([af0-9]{24})$”添加到请求属性“iamRoleId”
POST /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 已将模式“^([af0-9]{24})$”添加到请求属性“iamRoleId”
GET /api/atlas/v2/groups/{groupId}/serviceAccounts
Updated
  • “results/items/secrets/items/secret”响应的属性模式“^mdb_sa_sk_[0-9a-zA-Z_-]{40}$”已删除
POST /api/atlas/v2/groups/{groupId}/serviceAccounts
Updated
  • “secrets/items/secret”响应的属性模式“^mdb_sa_sk_[0-9a-zA-Z_-]{40}$”已删除
GET /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
Updated
  • “secrets/items/secret”响应的属性模式“^mdb_sa_sk_[0-9a-zA-Z_-]{40}$”已删除
PATCH /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
Updated
  • “secrets/items/secret”响应的属性模式“^mdb_sa_sk_[0-9a-zA-Z_-]{40}$”已删除
POST /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/secrets
Updated
  • “秘密”响应的属性模式“^mdb_sa_sk_[0-9a-zA-Z_-]{40}$”已删除
POST /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}:invite
Updated
  • “secrets/items/secret”响应的属性模式“^mdb_sa_sk_[0-9a-zA-Z_-]{40}$”已删除
GET /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections
Updated
  • 已添加“results/items/ _id”响应的属性模式“^([af0-9]{24})$”
POST /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections
Updated
  • 已将模式“^([af0-9]{24})$”添加到请求属性“_id”
  • 已添加“_id”响应的属性模式'^([af0-9]{24})$'
GET /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections/{connectionId}
Updated
  • 已添加“_id”响应的属性模式'^([af0-9]{24})$'
DELETE /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 添加了状态为“ 409 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 添加了状态为“ 409 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/users
Updated
  • 端点已弃用
  • 添加了新的可选“查询”请求参数“orgMembershipStatus”
GET /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList
Updated
  • “results/items/cidrBlock”响应的属性模式已从“^((([0-9]{1,3}\.){3}[ 0-9]{1,3})|([\:]{0,2}([0-9af]{1,4}\:){0,7}[0-9af]{1,4}[\:]{0,2}))((%2[fF]|\/)[0-9]{1,3})+$' to ' ^((([0-9]{1,3}\.){3}[0-9]{1,3})|(:{0,2}([0-9af]{1,4}:){0,7}[0-9af]{1,4}[:]{0,2}))((%2[fF] |/)[0-9]{1,3})+$'
  • “results/items/ipAddress”响应的属性模式已从“^((([0-9]{1,3}\.){3}[ 0-9]{1,3})|([\:]{0,2}([0-9af]{1,4}\:){0,7}[0-9af]{1,4}[\:]{0,2}))$' 为 '^((25[0-5]|(2[0-4]|1\d |[1-9]|)\d)(\.(?!$)|$)){4}|([0-9af]{1,4}:){7}[0-9af]{1,4}$'
  • “results/items/lastUsedAddress”响应的属性模式“^((([0-9]{1,3}\.){3}[0 -9]{1,3})|([\:]{0,2}([0-9af]{1 ,4}\:){0,7}[0-9af]{1,4}[\:]{0 ,2}))$' 已删除
POST /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList
Updated
  • “results/items/cidrBlock”响应的属性模式已从“^((([0-9]{1,3}\.){3}[ 0-9]{1,3})|([\:]{0,2}([0-9af]{1,4}\:){0,7}[0-9af]{1,4}[\:]{0,2}))((%2[fF]|\/)[0-9]{1,3})+$' to ' ^((([0-9]{1,3}\.){3}[0-9]{1,3})|(:{0,2}([0-9af]{1,4}:){0,7}[0-9af]{1,4}[:]{0,2}))((%2[fF] |/)[0-9]{1,3})+$'
  • “results/items/ipAddress”响应的属性模式已从“^((([0-9]{1,3}\.){3}[ 0-9]{1,3})|([\:]{0,2}([0-9af]{1,4}\:){0,7}[0-9af]{1,4}[\:]{0,2}))$' 为 '^((25[0-5]|(2[0-4]|1\d |[1-9]|)\d)(\.(?!$)|$)){4}|([0-9af]{1,4}:){7}[0-9af]{1,4}$'
  • “results/items/lastUsedAddress”响应的属性模式“^((([0-9]{1,3}\.){3}[0 -9]{1,3})|([\:]{0,2}([0-9af]{1 ,4}\:){0,7}[0-9af]{1,4}[\:]{0 ,2}))$' 已删除
GET /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList/{ipAddress}
Updated
  • “cidrBlock”响应的属性模式已从 '^((([0-9]{1,3}\.){3}[0- 9]{1,3})|([\:]{0,2}([0-9af]{1, 4}\:){0,7}[0-9af]{1,4}[\:]{0, 2}))((%2[fF]|\/)[0-9]{1,3})+$' to '^((( [0-9]{1,3}\.){3}[0-9]{1,3} )|(:{0,2}([0-9af]{1,4}:){0,7} [0-9af]{1,4}[:]{0,2}))((%2[fF]|/)[ 0-9]{1,3})+$'
  • “ipAddress”响应的属性模式已从 '^((([0-9]{1,3}\.){3}[0- 9]{1,3})|([\:]{0,2}([0-9af]{1, 4}\:){0,7}[0-9af]{1,4}[\:]{0, 2}))$' 为 '^((25[0-5]|(2[0-4]|1\d|[1-9]|)\d)(\.(?!$)|$)){4}|([0-9af]{1,4}:){7}[0-9af]{1,4}$'
  • “lastUsedAddress”响应的属性模式“^((([0-9]{1,3}\.){3}[0-9 ]{1,3})|([\:]{0,2}([0-9af]{1,4}\:){0,7}[0-9af]{1,4}[\:]{0,2}))$' 已删除
POST /api/atlas/v2/orgs/{orgId}/billing/costExplorer/usage
Updated
  • 将模式“^([af0-9]{24})$”添加到请求属性“clusters/items/”
  • 已将模式“^([af0-9]{24})$”添加到请求属性“organizations/items/”
  • 已将模式“^([af0-9]{24})$”添加到请求属性“projects/items/”
GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • 在“results/items/lineItems/items/sku”响应属性中添加了新的“ATLAS_NDS_AWS_CMK_PRIVATE_NETWORKING、ATLAS_NDS_AZURE_CMK_PRIVATE_NETWORKING”枚举值
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
Updated
  • 在“lineItems/items/sku”响应属性中添加了新的“ATLAS_NDS_AWS_CMK_PRIVATE_NETWORKING、ATLAS_NDS_AZURE_CMK_PRIVATE_NETWORKING”枚举值
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}/lineItems:search
Updated
  • 将模式“^([af0-9]{24})$”添加到请求属性“filters/clusterIds/items/”
  • 将模式“^([af0-9]{24})$”添加到请求属性“filters/groupIds/items/”
  • 已添加“results/items/groupId”响应的属性模式“^([af0-9]{24})$”
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts
Updated
  • “results/items/secrets/items/secret”响应的属性模式“^mdb_sa_sk_[0-9a-zA-Z_-]{40}$”已删除
POST /api/atlas/v2/orgs/{orgId}/serviceAccounts
Updated
  • “secrets/items/secret”响应的属性模式“^mdb_sa_sk_[0-9a-zA-Z_-]{40}$”已删除
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}
Updated
  • “secrets/items/secret”响应的属性模式“^mdb_sa_sk_[0-9a-zA-Z_-]{40}$”已删除
PATCH /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}
Updated
  • “secrets/items/secret”响应的属性模式“^mdb_sa_sk_[0-9a-zA-Z_-]{40}$”已删除
POST /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/secrets
Updated
  • “秘密”响应的属性模式“^mdb_sa_sk_[0-9a-zA-Z_-]{40}$”已删除
PATCH /api/atlas/v2/orgs/{orgId}/settings
Updated
  • “maxServiceAccountSecretValidityInHours”请求属性的最大值已设立为“8760.00”
  • “maxServiceAccountSecretValidityInHours”请求属性的最小值已设立为“8.00”
POST /api/atlas/v2/users
Updated
  • “teamIds/items/”请求属性的 minLength 从“24”减少到“0”

2024 年 12 月 09 日发布

GET /api/atlas/v2/clusters
Updated
  • “results/items/clusters/items/name”响应的属性模式已从“^([a-zA-Z0-9][a-zA-Z0-9-] *)?[a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9 -]*$'
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • “results/items/oneOf[subschema #2: Cluster Alerts]/clusterName”响应的属性模式已从“^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' 为 '^[a-zA-Z0-9][a-zA- Z0-9-]*$'
  • “results/items/oneOf[subschema #3: Host Alerts]/clusterName”响应的属性模式已从“^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' 为 '^[a-zA-Z0-9][a-zA- Z0-9-]*$'
  • “results/items/oneOf[subschema #4: Host Metric Alerts]/clusterName”响应的属性模式已从“^([a-zA-Z0-9][a-zA-Z 0-9-]*)?[a-zA-Z0-9]+$' 为 '^[a-zA-Z0-9][a-zA -Z0-9-]*$'
  • “results/items/oneOf[subschema #5: ReplicaSet Alerts]/clusterName”响应的属性模式已从“^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' 为 '^[a-zA-Z0-9][a-zA- Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • “results/items/oneOf[subschema #2: Cluster Alerts]/clusterName”响应的属性模式已从“^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' 为 '^[a-zA-Z0-9][a-zA- Z0-9-]*$'
  • “results/items/oneOf[subschema #3: Host Alerts]/clusterName”响应的属性模式已从“^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' 为 '^[a-zA-Z0-9][a-zA- Z0-9-]*$'
  • “results/items/oneOf[subschema #4: Host Metric Alerts]/clusterName”响应的属性模式已从“^([a-zA-Z0-9][a-zA-Z 0-9-]*)?[a-zA-Z0-9]+$' 为 '^[a-zA-Z0-9][a-zA -Z0-9-]*$'
  • “results/items/oneOf[subschema #5: ReplicaSet Alerts]/clusterName”响应的属性模式已从“^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' 为 '^[a-zA-Z0-9][a-zA- Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • '/oneOf[subschema #2: Cluster Alerts]/clusterName' 响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0- 9-]*)?[a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • '/oneOf[subschema #3: Host Alerts]/clusterName' 响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0- 9-]*)?[a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • '/oneOf[subschema #4: Host Metric Alerts]/clusterName' 响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0 -9-]*)?[a-zA-Z0-9]+$' 为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • '/oneOf[subschema #5: ReplicaSet Alerts]/clusterName' 响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0- 9-]*)?[a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • '/oneOf[subschema #2: Cluster Alerts]/clusterName' 响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0- 9-]*)?[a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • '/oneOf[subschema #3: Host Alerts]/clusterName' 响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0- 9-]*)?[a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • '/oneOf[subschema #4: Host Metric Alerts]/clusterName' 响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0 -9-]*)?[a-zA-Z0-9]+$' 为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • '/oneOf[subschema #5: ReplicaSet Alerts]/clusterName' 响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0- 9-]*)?[a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • “results/items/name”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 已将请求属性“名称”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “名称”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 已将请求属性“名称”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “名称”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgradeToServerless
Updated
  • 已将请求属性“名称”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “名称”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “名称”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • 已将请求属性“名称”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “名称”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports/{exportId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “results/items/targetClusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • 已将请求属性“targetClusterName”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “targetClusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs/{restoreJobId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs/{restoreJobId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “targetClusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • 已将请求属性“clusterName”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/shardedCluster/{snapshotId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/shardedCluster/{snapshotId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/shardedClusters
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/download
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • 已将请求属性“clusterName”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/restore
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • 已将请求属性“clusterName”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/restores
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “results/items/clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/restores/{restoreId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/snapshots
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/snapshots/{snapshotId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backupCheckpoints
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backupCheckpoints/{checkpointId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
PUT /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/unpin
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{databaseName}/{collectionName}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/customZoneMapping
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/customZoneMapping
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/managedNamespaces
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/managedNamespaces
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/index
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “results/items/clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • 已将请求属性“clusterName”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/queryLogs.gz
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • 已将请求属性“clusterName”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/outageSimulation
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/outageSimulation
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/outageSimulation
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • 已将请求属性“clusterName”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/performanceAdvisor/suggestedIndexes
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restartPrimaries
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “results/items/clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
  • “results/items/delivery/targetClusterName”响应的属性模式已从“^([a-zA-Z0-9][a-zA-Z0-9-]*)”更改?[a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-] *$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • 已将请求属性“clusterName”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • 已将请求属性“delivery/targetClusterName”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a -zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “results/items/clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
  • “results/items/delivery/targetClusterName”响应的属性模式已从“^([a-zA-Z0-9][a-zA-Z0-9-]*)”更改?[a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-] *$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs/{jobId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “delivery/targetClusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a- zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'