Exec Inspection Task

巡检任务有两种触发方式：手动触发和定时触发。如果用户选择手动触发巡检，则对应的巡检操作会立即执行，巡检结果会根据触发方式展示在不同的位置。

如果用户从某个组件实例的详情页触发巡检，巡检结果会显示在该组件实例的详情页，同时也会出现在巡检报告页，如下图所示：

Inspection Trigger Button on Instance Details Page

Inspection Result Presentation on Instance Details Page

Inspection Result Presentation on Inspection Report Page

如果用户在某个巡检任务上触发，无论是手动还是自动触发，巡检结果会以巡检记录的形式展示在该任务的巡检记录中，如下图所示：

Inspection Result Presentation on Inspection Task

操作步骤

CLI

Web Console

可以通过 CLI 查询某次巡检任务执行的结果，示例如下：


kubectl get -n namespace inspectionjobs/name -o yaml

apiVersion: middleware.alauda.io/v1
kind: InspectionJob
metadata:
  annotations:
    cpaas.io/creator: admin
    cpaas.io/updated-at: "2025-02-24T06:36:11Z"
  creationTimestamp: "2025-02-24T06:36:11Z"
  generation: 1
  labels:
    inspection.middleware.io/cluster: business-1
    inspection.middleware.io/component: mysqlcluster
    inspection.middleware.io/inspection: insp-task
    inspection.middleware.io/namespace: tongrds-1
    inspection.middleware.io/project: tongrds
    inspection.middleware.io/trigger: Manual
  name: insp-task-8259621030
  namespace: tongrds-1
  ownerReferences:
  - apiVersion: middleware.alauda.io/v1
    blockOwnerDeletion: true
    controller: true
    kind: Inspection
    name: insp-task
    uid: b9252d5a-4f94-4901-8036-e963f0cc0acb
  resourceVersion: "58806102"
  uid: 524ad817-ef5e-4eea-9b06-83782616ca03
spec:
  component: mysqlcluster
  instances:
  - name: mgr1
status:
  instanceCount: 1
  message: ""
  results:
  - healthyStatus: HealthyWithWarning
    id: mgr1-2x4eojeu
    instance: mgr1
    message: ""
    startTime: "2025-02-24T06:36:14Z"
    status: done
    stopTime: "2025-02-24T06:36:22Z"
  startTime: "2025-02-24T06:36:11Z"
  status: succeed
  stopTime: "2025-02-24T06:36:22Z"

Info

<spec.component> 是本次巡检执行的目标实例类型。
<spec.instances> 是本次巡检执行的目标实例列表。
<status.results> 是本次巡检执行的结果列表，字段包含巡检的开始和结束时间、巡检概览、状态等信息。

#Exec Inspection Task

#目录

#操作步骤

Exec Inspection Task

目录

操作步骤