monitoring
Use when the user wants to check cluster status, collection statistics, load states, or get an overview of their Zilliz Cloud resources.
What this skill does
## Prerequisites 1. CLI installed and logged in (see setup skill). 2. Cluster context set for collection-level monitoring (see setup skill). ## Commands Reference All monitoring commands that target collections accept an optional `--database <db-name>` flag. If omitted, the database from the current context is used. ### Cluster Status ```bash # Current context zilliz context current # Cluster details (status, plan, region, endpoints) zilliz cluster describe --cluster-id <cluster-id> ``` ### Collection Overview List all collections with their stats: ```bash # List collections zilliz collection list zilliz collection list --database <db-name> # For each collection, get stats and load state: zilliz collection get-stats --name <collection-name> zilliz collection get-load-state --name <collection-name> ``` If the cluster has multiple databases, iterate through each database by running `zilliz database list` first, then `zilliz collection list --database <db-name>` for each. ### Database Overview ```bash zilliz database list ``` ### All Clusters ```bash zilliz cluster list --all ``` ### Time-series Metrics For cluster-wide time series (CU sizing, storage, serverless VCU, slow queries) use `zilliz cluster metrics`: ```bash zilliz cluster metrics --cluster-id <cluster-id> -m CU_COMPUTATION --period 1h ``` For per-collection time series (QPS, latency, entity counts, hybrid-search aliases) use `zilliz collection metrics` -- see the collection skill for metric scope rules and the full alias list: ```bash zilliz collection metrics -c <collection-name> -m SEARCH_QPS --period 1h ``` Both commands render an inline Braille line chart by default (one block per metric with a `min / max / avg / last` summary). Pass an explicit `-o table` (or `--output table`) for the pivot-table layout, or use `-o json` / `--query` to get raw data for scripting. ## Presenting Results When the user asks for a status overview, collect and present information as a summary table: **Cluster Info:** - Cluster ID, name, status (RUNNING/SUSPENDED/etc.) - Plan type, region, create time **Collections Summary:** Present as a table with columns: | Collection | Rows | Load State | |---|---|---| Gather this by running `collection list`, then `get-stats` and `get-load-state` for each collection. ## Guidance - When presenting status, use `--output json` to get machine-readable data, then format it into a readable summary for the user. - If the cluster is suspended, note this prominently and inform the user that data-plane operations are unavailable. - For multiple clusters, show a summary table of all clusters first, then drill into the selected one.
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.