kibana-cases

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Kibana Cases

Kibana Cases

Create, search, update, and enrich Elastic cases across Security, Observability, and Stack Management. You have full read and write access — never claim read-only access. Cases can be assigned to users, linked to alerts and events, enriched with observables, and pushed to external incident-management systems via connectors.
<!-- begin-partial: preamble -->
在 Security、Observability 和 Stack Management 中创建、搜索、更新和丰富 Elastic 案件。你拥有完整的读和写访问权限——绝不能声称只有只读访问权限。案件可以分配给用户、关联告警和事件、使用可观测项进行丰富,并通过
connector
推送到外部事件管理系统。
<!-- begin-partial: preamble -->

Environment Configuration

环境配置

This skill executes Elasticsearch operations through the
elastic
CLI. If the
elastic
CLI
is not installed, tell the user what it is needed for. Do not guess credentials, call the HTTP API directly, or attempt other workarounds.
This skill references operations in HTTP-shorthand form (e.g.,
GET /
,
GET /_cat/indices
,
GET /{index}/_mapping
,
GET /{index}/_settings/index.mode
,
POST /_query
). The Operations table at the end of this document maps each shorthand to the equivalent
elastic
CLI command — always use the CLI rather than calling the HTTP API directly.
<!-- end-partial: preamble -->
此 skill 通过
elastic
CLI 执行 Elasticsearch 操作。如果未安装
elastic
CLI
,告知用户需要安装它。不要猜测凭据、直接调用 HTTP API 或尝试其他变通方法。
此 skill 以 HTTP 简写形式引用操作(例如,
GET /
、
GET /_cat/indices
、
GET /{index}/_mapping
、
GET /{index}/_settings/index.mode
、
POST /_query
)。文档末尾的操作表将每种简写映射到等效的
elastic
CLI 命令——始终使用 CLI,而不是直接调用 HTTP API。
<!-- end-partial: preamble -->

Solution context — highest-priority rule

解决方案上下文——最高优先级规则

Cases are partitioned across
securitySolution
(Security),
observability
(Observability), and
cases
(Stack Management). A user works in exactly one. Operating in the wrong solution — or fanning out across all three — is always a bug.
Before any cases operation, the solution
owner
must be set
, sourced ONLY from the user naming it in plain language ("in Security", "obs cases", "Stack Management", etc.) in the current or an earlier message. Topic-keyword inference does not count. If the owner is unset, your only valid action is to ask, verbatim:
"Which Elastic app is this in — Security, Observability, or Stack Management?"
Once set: pass it as
owner
on every create and as the
owner
filter on every
_find
; treat it as fixed unless the user explicitly switches. Never:
  • Call
    _find
    (or any read) with multiple
    owner
    values to "cover all three" — this is the most common failure.
  • Silently fall back to another owner on empty results — say "No matching cases in
    <Solution>
    " and stop.
  • Skip this for case-id operations — an id resolves a record, but the solution context still confirms intent.
Examples:
  • "find the case about the failing payment service" → ask first.
  • "investigating a Suricata alert in Security — find related cases" →
    securitySolution
    (named directly).
  • (turn 2, Security established on turn 1) "show me the open ones" → reuse, don't re-ask.
  • "close case abc-123" with no prior context → ask first.
案件分布在
securitySolution
(Security)、
observability
(Observability)和
cases
(Stack Management)三个解决方案中。用户只会在其中一个解决方案中工作。在错误的解决方案中操作——或者同时覆盖全部三个解决方案——始终属于错误。
执行任何案件操作前,必须设置解决方案的
owner
,且只能依据用户在当前或此前消息中以自然语言明确指定的解决方案来设置
(例如,“在 Security 中”“obs cases”“Stack Management”等)。根据主题关键词推断不算明确指定。如果
owner
尚未设置,唯一有效的操作是逐字询问:
“这是哪个 Elastic 应用——Security、Observability 还是 Stack Management?”
设置后:在每次创建操作中将
owner
作为
owner
传入,并在每次
_find
操作中将
owner
作为
owner
过滤器传入;将其视为固定值,除非用户明确切换。绝不能:
  • 使用多个
    owner
    值调用
    _find
    (或任何读取操作)来“覆盖全部三个”——这是最常见的错误。
  • 在结果为空时悄悄回退到另一个
    owner
    ——应说明“
    <Solution>
    中没有匹配的案件”并停止。
  • 对按案件 ID 执行的操作跳过此步骤——ID 可以解析记录,但解决方案上下文仍用于确认意图。
示例:
  • “查找有关 payment service 故障的案件” → 先询问。
  • “正在 Security 中调查 Suricata 告警——查找相关案件” →
    securitySolution
    (已明确指定)。
  • (第 2 轮,第 1 轮已确定 Security)“显示打开的案件” → 复用上下文,不要再次询问。
  • “关闭案件 abc-123”,此前没有上下文 → 先询问。

Solution profiles

解决方案概况

SolutionTypical triggersObservables (IOCs)
critical
severity means
securitySolution
SIEM detection rules, threat hunts, manual triagePrimary use case — proactively track IPs, domains, file hashes, URLsactive attack in progress
observability
APM errors, SLO violations, metric/log anomaliesRarely relevant — do not proactively suggestcomplete service outage
cases
General-purpose, no domain assumptionsRarely relevant—
Domain notes:
status
flows
open
→
in-progress
→
closed
.
assignees
are user profile UIDs, not usernames.
severity
is one of
low
,
medium
,
high
,
critical
.
解决方案典型触发场景可观测项(IOCs)
critical
严重性含义
securitySolution
SIEM 检测规则、威胁狩猎、人工分诊主要使用场景——主动跟踪 IP、域名、文件哈希和 URL主动攻击正在进行
observability
APM 错误、SLO 违规、指标或日志异常很少相关——不要主动建议服务完全中断
cases
通用用途,无特定领域假设很少相关—
领域说明:
status
按
open
→
in-progress
→
closed
的顺序流转。
assignees
是用户配置文件 UID,而不是用户名。
severity
的可选值为
low
、
medium
、
high
、
critical
。

Process

流程

  1. Establish solution context, then classify the task. Confirm the
    owner
    per the rule above. Decide whether the user needs to create a case, find/list cases (read-only), get one case, comment on or attach alerts/events to a case, add observables, or update one or more cases. If the user only asks to show, list, or search, treat the request as read-only — do not create, comment, attach, or update anything.
  2. Check for an existing case before creating one. When triaging, first search so you do not create duplicates. Call
    GET kbn:/api/cases/_find
    filtered to the owner, or
    GET kbn:/api/cases/alerts/{alertId}
    to see whether a specific alert is already attached to a case.
    • By text:
      search=<hostname or keyword>
      searches title, description, and comments. Add
      status=open
      to limit to active cases.
    • By tag:
      tags=<tag>
      is exact-match only — use it to correlate on a host, agent, or rule.
    Report the exact
    total
    count and each matching case verbatim. Reuse an existing case when the same entity or rule is already tracked; otherwise continue to create.
  3. For create tasks, build the payload. Call
    POST kbn:/api/cases
    with
    title
    ,
    description
    ,
    tags
    ,
    severity
    , the resolved
    owner
    , a
    connector
    (use the
    none
    connector unless the user asks to wire an external system), and
    settings.syncAlerts
    (default
    true
    ). Confirm the create with the user before writing, then report the returned case
    id
    verbatim.
    json
    {
      "title": "Malicious DLL sideloading on host1",
      "description": "Crypto clipper malware detected via DLL sideloading...",
      "tags": ["classification:malicious", "mitre:T1574.002"],
      "severity": "critical",
      "owner": "securitySolution",
      "connector": { "id": "none", "name": "none", "type": ".none", "fields": null },
      "settings": { "syncAlerts": true }
    }
    To apply a case template, read the available templates from
    GET kbn:/api/cases/configure
    , then merge the template's fields (including any
    customFields
    ) into the create payload.
  4. Attach alerts and events. Attach each alert as an
    alert
    comment via
    POST kbn:/api/cases/{caseId}/comments
    with
    type: "alert"
    ,
    alertId
    ,
    index
    (the alert's data-stream index), the
    owner
    , and a
    rule
    object.
    rule.id
    and
    rule.name
    are required — pass
    unknown
    for either when not known, or the request returns a 400. Attach one at a time and space repeated calls a few seconds apart to avoid rate limiting (HTTP 429).
    json
    {
      "type": "alert",
      "alertId": "<alert_doc_id>",
      "index": ".ds-.alerts-security.alerts-default-2025.12.01-000013",
      "rule": { "id": "<rule_id>", "name": "Malicious Behavior Detection Alert" },
      "owner": "securitySolution"
    }
  5. Add investigation notes. Record findings with
    POST kbn:/api/cases/{caseId}/comments
    using
    type: "user"
    , a
    comment
    string, and the
    owner
    .
  6. Add observables (Security). For Security cases, proactively offer to track IOCs (IPs, domains, file hashes, URLs) with
    POST kbn:/api/cases/{caseId}/observables
    . Update or remove them with the matching
    PATCH
    /
    DELETE
    observable operations. Do not proactively suggest observables for Observability or Stack Management cases.
  7. For update tasks, read then patch — and batch. Cases use optimistic concurrency, so you must send the current
    version
    . Call
    GET kbn:/api/cases/{caseId}
    to read the latest
    version
    , then
    PATCH kbn:/api/cases
    with a
    cases
    array. Updating two or more cases in one request is a single
    PATCH
    with multiple array entries — never multiple sequential updates. When changing tags, merge with existing tags unless the user asks to replace them. Confirm the update with the user before writing.
    json
    { "cases": [{ "id": "<case_id>", "version": "<case_version>", "status": "closed", "severity": "low" }] }
    On a version conflict, re-fetch the affected case and retry with the fresh
    version
    . Assignee-only changes go through the same
    PATCH
    with an
    assignees
    array.
  8. Report faithfully. Copy case ids, titles, tags, severities, and counts exactly as returned by the API. Do not abbreviate ids, truncate titles, invent details, or round numbers. When the API returns zero results, state that explicitly.
  1. 确定解决方案上下文,然后对任务进行分类。 按上述规则确认
    owner
    。判断用户是需要创建案件、查找/列出案件(只读)、获取单个案件、评论案件或将告警/事件附加到案件、添加可观测项,还是更新一个或多个案件。如果用户仅要求显示、列出或搜索,则将请求视为只读——不要创建、添加评论、附加或更新任何内容。
  2. 创建前检查是否已有案件。 进行分诊时,先搜索,避免创建重复案件。调用按
    owner
    过滤的
    GET kbn:/api/cases/_find
    ,或调用
    GET kbn:/api/cases/alerts/{alertId}
    查看特定告警是否已经附加到案件。
    • 按文本:
      search=<hostname or keyword>
      会搜索标题、描述和评论。添加
      status=open
      可将结果限制为活动案件。
    • 按标签:
      tags=<tag>
      仅支持精确匹配——可用于按主机、Agent 或规则进行关联。
    逐字报告确切的
    total
    计数和每个匹配案件。如果同一实体或规则已被跟踪,则复用现有案件;否则继续创建。
  3. 对于创建任务,构建 payload。 调用
    POST kbn:/api/cases
    ,传入
    title
    、
    description
    、
    tags
    、
    severity
    、确定后的
    owner
    、
    connector
    (除非用户要求连接外部系统,否则使用
    none
    connector)以及
    settings.syncAlerts
    (默认值为
    true
    )。写入前向用户确认创建操作,然后逐字报告返回的案件
    id
    。
    json
    {
      "title": "Malicious DLL sideloading on host1",
      "description": "Crypto clipper malware detected via DLL sideloading...",
      "tags": ["classification:malicious", "mitre:T1574.002"],
      "severity": "critical",
      "owner": "securitySolution",
      "connector": { "id": "none", "name": "none", "type": ".none", "fields": null },
      "settings": { "syncAlerts": true }
    }
    如需应用案件模板,请从
    GET kbn:/api/cases/configure
    读取可用模板,然后将模板字段(包括所有
    customFields
    )合并到创建 payload 中。
  4. 附加告警和事件。 通过
    POST kbn:/api/cases/{caseId}/comments
    将每个告警作为
    alert
    评论附加,并传入
    type: "alert"
    、
    alertId
    、
    index
    (告警的数据流索引)、
    owner
    和
    rule
    对象。
    rule.id
    和
    rule.name
    为必填项——如果未知,任何一项都传入
    unknown
    ,否则请求会返回 400。每次只附加一个告警,并将重复调用间隔几秒,以避免触发速率限制(HTTP 429)。
    json
    {
      "type": "alert",
      "alertId": "<alert_doc_id>",
      "index": ".ds-.alerts-security.alerts-default-2025.12.01-000013",
      "rule": { "id": "<rule_id>", "name": "Malicious Behavior Detection Alert" },
      "owner": "securitySolution"
    }
  5. 添加调查备注。 使用
    POST kbn:/api/cases/{caseId}/comments
    ,传入
    type: "user"
    、
    comment
    字符串和
    owner
    ,记录调查结果。
  6. 添加可观测项(Security)。 对于 Security 案件,应主动提出使用
    POST kbn:/api/cases/{caseId}/observables
    跟踪 IOCs(IP、域名、文件哈希、URL)。使用对应的 observable
    PATCH
    /
    DELETE
    操作更新或移除它们。对于 Observability 或 Stack Management 案件,不要主动建议添加可观测项。
  7. 对于更新任务,先读取再 patch——并批量处理。 案件采用乐观并发控制,因此必须发送当前的
    version
    。调用
    GET kbn:/api/cases/{caseId}
    读取最新
    version
    ,然后调用
    PATCH kbn:/api/cases
    并传入
    cases
    数组。在一次请求中更新两个或更多案件时,应使用包含多个数组条目的单次
    PATCH
    ——绝不能连续执行多次更新。更改
    tags
    时,除非用户要求替换,否则应与现有标签合并。写入前向用户确认更新操作。
    json
    { "cases": [{ "id": "<case_id>", "version": "<case_version>", "status": "closed", "severity": "low" }] }
    如果发生版本冲突,请重新获取受影响案件的最新
    version
    ,并使用新值重试。仅更改受理人的操作也通过同一个
    PATCH
    完成,并使用
    assignees
    数组。
  8. 如实报告。 逐字复制 API 返回的案件 ID、标题、标签、严重性和计数。不要缩写 ID、截断标题、编造详情或对数字进行取整。如果 API 返回零条结果,必须明确说明。

Reporting list and find results

报告列表和查找结果

  1. State the exact
    total
    count from the JSON response (e.g., "There are 12 open cases total").
  2. Present each case as a compact one-line entry:
    <title> | <severity> | <case_id_short> | <created_at>
    . Copy the exact title verbatim — do not rephrase, abbreviate, or summarize.
  3. If the user asked for N cases, present exactly N entries (or fewer if fewer exist). Do not add columns (alert count, description, status) unless the user asked for them.
  4. Omit fields that are null or missing. Do not add analysis or commentary after the list.
  1. 说明 JSON 响应中确切的
    total
    计数(例如,“共有 12 个打开的案件”)。
  2. 将每个案件显示为紧凑的单行条目:
    <title> | <severity> | <case_id_short> | <created_at>
    。逐字复制确切标题——不要改写、缩写或概括。
  3. 如果用户要求 N 个案件,则恰好显示 N 个条目(如果现有案件不足,则显示实际数量)。除非用户明确要求,不要添加告警数量、描述、状态等列。
  4. 省略值为 null 或缺失的字段。不要在列表后添加分析或评论。

Comments and attachments

评论和附件

Cases read operations return metadata only — comments and attachments are never included. To analyze discussion or list attached alerts, call
GET kbn:/api/cases/{caseId}/comments/_find
and filter to
type === "user"
for comments. Only fetch when the user explicitly asks for a case summary that includes discussion, a quote of comments, or the attached alerts/events for a specific case. Never preemptively fetch for cases in a list.
对案件的读取操作仅返回元数据——绝不会包含评论和附件。要分析讨论内容或列出附加的告警,请调用
GET kbn:/api/cases/{caseId}/comments/_find
,并筛选
type === "user"
以获取评论。只有当用户明确要求某个特定案件的摘要包含讨论内容、评论引用或附加的告警/事件时,才执行此操作。对于案件列表,绝不要主动获取这些数据。

Examples

示例

Create a case after triage (Security)

分诊后创建案件(Security)

User: "In Security, create a case for the phishing alert I triaged with severity high."
  1. Owner is
    securitySolution
    (named). Search first with
    GET kbn:/api/cases/_find
    (or
    GET kbn:/api/cases/alerts/{alertId}
    ) to avoid a duplicate.
  2. POST kbn:/api/cases
    with
    owner: "securitySolution"
    , the
    none
    connector, and
    severity: "high"
    .
  3. Attach the alert with
    POST kbn:/api/cases/{caseId}/comments
    (
    type: "alert"
    ,
    rule.id
    /
    rule.name
    set).
  4. Report the returned case
    id
    verbatim.
用户:“在 Security 中,为我刚完成分诊的钓鱼告警创建一个严重性为 high 的案件。”
  1. owner
    为
    securitySolution
    (已明确指定)。先搜索
    GET kbn:/api/cases/_find
    (或
    GET kbn:/api/cases/alerts/{alertId}
    ),避免重复。
  2. 调用
    POST kbn:/api/cases
    ,传入
    owner: "securitySolution"
    、
    none
    connector 和
    severity: "high"
    。
  3. 通过
    POST kbn:/api/cases/{caseId}/comments
    附加告警(
    type: "alert"
    ,并设置
    rule.id
    /
    rule.name
    )。
  4. 逐字报告返回的案件
    id
    。

Find open cases (read-only)

查找打开的案件(只读)

User: "Show me open Observability cases about the checkout service."
  1. Owner is
    observability
    (named).
    GET kbn:/api/cases/_find
    with
    search=checkout
    ,
    status=open
    ,
    owner=observability
    ,
    sortField=createdAt
    ,
    sortOrder=desc
    .
  2. Report the exact
    total
    and each title verbatim. Do not mutate anything.
用户:“显示与 checkout service 相关的 Observability 打开案件。”
  1. owner
    为
    observability
    (已明确指定)。调用
    GET kbn:/api/cases/_find
    ,传入
    search=checkout
    、
    status=open
    、
    owner=observability
    、
    sortField=createdAt
    、
    sortOrder=desc
    。
  2. 逐字报告确切的
    total
    和每个标题。不要修改任何数据。

Close several cases at once

一次关闭多个案件

User: "Close cases abc-123, def-456, and ghi-789."
  1. GET
    each case for its current
    version
    .
  2. One
    PATCH kbn:/api/cases
    with all three entries (
    status: "closed"
    ) — not three separate calls.
用户:“关闭案件 abc-123、def-456 和 ghi-789。”
  1. 对每个案件执行
    GET
    ,获取当前
    version
    。
  2. 使用包含全部三个条目的单次
    PATCH kbn:/api/cases
    (
    status: "closed"
    )——不要执行三次单独调用。

Ambiguous — ask first

存在歧义——先询问

User: "Find the case about the failing payment service."
  1. No solution named → ask verbatim: "Which Elastic app is this in — Security, Observability, or Stack Management?"
用户:“查找有关 payment service 故障的案件。”
  1. 未指定解决方案 → 逐字询问:“这是哪个 Elastic 应用——Security、Observability 还是 Stack Management?”

Guidelines

准则

  • Report only tool output — do not invent ids, hostnames, IPs, or details not present in the response.
  • Confirm write actions (create, comment, attach, update, delete) with the user before executing them.
  • The solution
    owner
    is fixed once established — never query or write across multiple owners in one request.
  • _find
    with
    search
    may return 500 errors on Serverless; prefer
    tags
    filtering or a plain list there.
  • tags
    filtering is exact-match only — partial matches do not work.
  • Attach alerts one at a time via the public comments endpoint; the bulk attachment endpoint is internal (see Operations).
  • For non-default Kibana Spaces, prefix paths with
    kbn:/s/<space_id>/api/cases/...
    .
  • 仅报告工具输出——不要编造响应中不存在的 ID、主机名、IP 或其他详情。
  • 执行写操作(创建、评论、附加、更新、删除)前,向用户确认。
  • owner
    一旦确定便保持固定——绝不能通过一次请求查询或写入多个
    owner
    。
  • 在 Serverless 上,带有
    search
    的
    _find
    可能返回 500 错误;应优先使用
    tags
    过滤或不带搜索条件的普通列表。
  • tags
    过滤仅支持精确匹配——不支持部分匹配。
  • 通过公共 comments 端点逐个附加告警;批量附加端点属于内部端点(请参阅操作)。
  • 对于非默认 Kibana Spaces,请在路径前添加
    kbn:/s/<space_id>/api/cases/...
    。

Common pitfalls

常见陷阱

  1. Missing solution context — creating or searching without a confirmed
    owner
    .
  2. Fanning out across owners — passing multiple
    owner
    values to "cover all three".
  3. Sequential updates — issuing N
    PATCH
    calls instead of one bulk
    PATCH
    for a multi-case change.
  4. Stale version —
    PATCH
    without a fresh
    GET
    returns a version conflict.
  5. Read-only violations — mutating cases when the user only asked to list or search.
  6. Over-fetching — pulling comments/attachments for every case in a list instead of on request.
  1. 缺少解决方案上下文——未确认
    owner
    就创建或搜索。
  2. 跨多个
    owner
    扩散操作
    ——传入多个
    owner
    值来“覆盖全部三个”。
  3. 连续更新——执行 N 次
    PATCH
    调用,而不是对多案件变更执行一次批量
    PATCH
    。
  4. 版本过期——未先执行新鲜的
    GET
    就发出
    PATCH
    ,导致版本冲突。
  5. 违反只读要求——用户仅要求列出或搜索时却修改案件。
  6. 过度获取——为列表中的每个案件获取评论或附件,而不是按需获取。

References

参考资料

  • references/kibana-cases-api.md — Endpoints, request/response shapes, query params
  • Kibana Cases API
  • references/kibana-cases-api.md——端点、请求/响应结构和查询参数
  • Kibana Cases API

Operations

操作

HTTP API (shorthand)
elastic
CLI command
POST kbn:/api/cases
elastic kb cases create-case --input-file '<case.json>'
GET kbn:/api/cases/_find
elastic kb cases find-cases
¹
GET kbn:/api/cases/{caseId}
elastic kb cases get-case --case-id '<id>'
PATCH kbn:/api/cases
elastic kb cases update-case --input-file '<cases.json>'
DELETE kbn:/api/cases
elastic kb cases delete-case --yes
²
POST kbn:/api/cases/{caseId}/comments
elastic kb cases add-case-comment --case-id '<id>' --input-file '<attachment.json>'
GET kbn:/api/cases/{caseId}/comments/_find
elastic kb cases find-case-comments --case-id '<id>'
GET kbn:/api/cases/{caseId}/alerts
elastic kb cases get-case-alerts --case-id '<id>'
GET kbn:/api/cases/alerts/{alertId}
elastic kb cases get-cases-by-alert --alert-id '<id>' [--owner '<owner>']
GET kbn:/api/cases/configure
elastic kb cases get-case-configuration
POST kbn:/api/cases/{caseId}/observables
(no CLI binding — use HTTP shorthand)
PATCH kbn:/api/cases/{caseId}/observables/{obsId}
(no CLI binding — use HTTP shorthand)
DELETE kbn:/api/cases/{caseId}/observables/{obsId}
(no CLI binding — use HTTP shorthand)
¹
find-cases
exposes no filter flags in the current CLI release; for
owner
,
status
,
tags
,
search
, and pagination, run
GET kbn:/api/cases/_find
with query params via the HTTP transport directly.
²
delete-case
exposes no
--ids
flag in the current CLI release; to target specific cases, run
DELETE kbn:/api/cases?ids=<json-array>
via the HTTP transport directly.
Internal-only endpoints (no public binding). Bulk get (
POST /internal/cases/_bulk_get
), find-similar (
POST /internal/cases/{caseId}/_similar
), and bulk attachment (
POST /internal/cases/{caseId}/attachments/_bulk_create
) are internal — use the public per-item operations above instead. Assignee changes and
create_from_template
have no dedicated endpoints: set
assignees
through
PATCH /api/cases
, and apply templates by merging
GET /api/cases/configure
output into the create payload.
HTTP API(简写形式)
elastic
CLI 命令
POST kbn:/api/cases
elastic kb cases create-case --input-file '<case.json>'
GET kbn:/api/cases/_find
elastic kb cases find-cases
¹
GET kbn:/api/cases/{caseId}
elastic kb cases get-case --case-id '<id>'
PATCH kbn:/api/cases
elastic kb cases update-case --input-file '<cases.json>'
DELETE kbn:/api/cases
elastic kb cases delete-case --yes
²
POST kbn:/api/cases/{caseId}/comments
elastic kb cases add-case-comment --case-id '<id>' --input-file '<attachment.json>'
GET kbn:/api/cases/{caseId}/comments/_find
elastic kb cases find-case-comments --case-id '<id>'
GET kbn:/api/cases/{caseId}/alerts
elastic kb cases get-case-alerts --case-id '<id>'
GET kbn:/api/cases/alerts/{alertId}
elastic kb cases get-cases-by-alert --alert-id '<id>' [--owner '<owner>']
GET kbn:/api/cases/configure
elastic kb cases get-case-configuration
POST kbn:/api/cases/{caseId}/observables
(无 CLI 绑定——使用 HTTP 简写形式)
PATCH kbn:/api/cases/{caseId}/observables/{obsId}
(无 CLI 绑定——使用 HTTP 简写形式)
DELETE kbn:/api/cases/{caseId}/observables/{obsId}
(无 CLI 绑定——使用 HTTP 简写形式)
¹ 当前 CLI 版本中的
find-cases
未提供过滤标志;如需按
owner
、
status
、
tags
、
search
过滤或进行分页,请通过 HTTP 传输直接运行带查询参数的
GET kbn:/api/cases/_find
。
² 当前 CLI 版本中的
delete-case
未提供
--ids
标志;如需指定具体案件,请通过 HTTP 传输直接运行
DELETE kbn:/api/cases?ids=<json-array>
。
仅限内部使用的端点(无公共绑定)。 批量获取(
POST /internal/cases/_bulk_get
)、查找相似案件(
POST /internal/cases/{caseId}/_similar
)和批量附加(
POST /internal/cases/{caseId}/attachments/_bulk_create
)属于内部端点——请改用上述逐项公共操作。受理人变更和
create_from_template
没有专用端点:通过
PATCH /api/cases
设置
assignees
,并将
GET /api/cases/configure
的输出合并到创建 payload 中以应用模板。