vss-setup-behavior-analytics
Use to deploy the vss-behavior-analytics service standalone (entrypoint, config-source, optional calibration). Not for the full warehouse deploy.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-10
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- vss-setup-behavior-analytics
- license
- Apache-2.0
- metadata
- { "tags": "nvidia blueprint operational deployment behavior-analytics", "author": "NVIDIA Video Search and Summarization team", "version": "3.2.0", "github-url": "https://github.com/NVIDIA-AI-Blueprints/video-search-and-summarization" }
- description
- Use to deploy the vss-behavior-analytics service standalone (entrypoint, config-source, optional calibration). Not for the full warehouse deploy.
02 资源文件 8
- 参考文档BENCHMARK.md2.3 KB
- 参考文档evals/standalone_deploy.json1.8 KB
- 参考文档references/configuration.md3.5 KB
- 参考文档references/deploy-behavior-analytics-service.md13.8 KB
- 参考文档references/dynamic-calibration.md13.0 KB
- 参考文档references/dynamic-config.md19.3 KB
- 参考文档skill-card.md2.7 KB
- 其他skill.oms.sig5.5 KB
03 SKILL.md 正文
Purpose
Deploy the behavior-analytics service standalone with the user's chosen entrypoint, config, and calibration.
Instructions
Follow the routing tables and step-by-step workflows below. Each section that ends in workflow, quick start, or flow is intended to be executed top-to-bottom. Detailed reference material lives in references/ and helper scripts live in scripts/ — call them via run_script when the skill points to a script by name.
Examples
Worked end-to-end examples are kept under evals/ (each *.json manifest
contains a runnable scenario). Run a Tier-3 evaluation to replay them:
nv-base validate skills/vss-setup-behavior-analytics --agent-eval
A minimal standalone bring-up looks like:
cd $REPO/deploy/docker
export VSS_APPS_DIR=$(pwd)
docker compose -f services/analytics/behavior-analytics/compose.yml up -d vss-behavior-analytics-base
Follow references/deploy-behavior-analytics-service.md for the full
workflow (entrypoint pick, config source, dynamic updates).
Limitations
- Requires the matching VSS profile / microservice to be deployed and reachable from the caller.
- NGC-hosted models and NIMs may be subject to rate-limits, GPU memory requirements, and license restrictions.
- Concurrency, GPU memory, and storage limits depend on the host hardware and the profile's compose file.
Troubleshooting
- Error: REST call returns connection refused. Cause: target microservice not running. Solution: probe
/docsor/health; redeploy viavss-deploy-profileor the matchingvss-deploy-*skill. - Error: HTTP 401/403 from NGC pulls. Cause: missing/expired
NGC_CLI_API_KEY. Solution:docker login nvcr.ioand re-export the key before retrying. - Error: container OOM or model fails to load. Cause: insufficient GPU memory for the selected profile. Solution: switch to a smaller variant or free GPUs via
docker compose down.
VSS Setup Behavior Analytics — Standalone
Deploy just the vss-behavior-analytics container (the spatial-AI analytics pipeline from the upstream behavior-analytics repo), not as part of the full warehouse blueprint stack.
The full operational walkthrough — entrypoint table, config-source options, calibration types, dynamic-update wire contract, troubleshooting — is references/deploy-behavior-analytics-service.md. This SKILL.md only handles routing and prerequisites.
When to use
- "Deploy behavior analytics" / "run behavior-analytics standalone"
- "I just want to run analytics, not the full stack"
- "Change the entrypoint to fusion_search / dev_example / analytics 3D / mv3dt"
- "Use my own behavior-analytics config / calibration JSON"
- "Point behavior-analytics at the warehouse-3d (or mv3dt) config without spinning up the rest of the warehouse profile"
- "Dynamic config / dynamic calibration into a running behavior-analytics"
Prerequisites
- Repo checkout with
$VSS_APPS_DIRpointing at<repo>/deploy/docker/. Required by the service compose's volume binds. - NGC credentials —
$NGC_CLI_API_KEYset so docker can pull the image. See../vss-deploy-profile/references/ngc.md. - Docker runtime — Docker Engine 28.3.3 with Docker Compose plugin v2.39.1+. Verify with
docker --versionanddocker compose version. - Optional broker (Kafka / Redis Streams / MQTT). The container starts fine without one — the Kafka client retries a bounded number of times, then the app exits and
restart: alwayscycles the container. Status will showRestarting (N)indocker psuntil a broker is reachable. With a broker, dynamic config / dynamic calibration overmdx-notificationbecome available. - Optional config / calibration files on disk if the user is bringing their own.
If any required prerequisite fails, surface the gap before going further.
Workflow
Hand the user references/deploy-behavior-analytics-service.md and walk them through its steps in order:
- Pick an entrypoint (analytics 2D / 3D / mv3dt, dev_example, fusion_search).
- Choose a config — profile-shipped or custom.
- Choose a calibration — optional; profile-shipped or custom; otherwise the app waits for a dynamic-calibration notification.
- Decide whether a broker is reachable; if yes, point them at the dynamic-update flows.
The compose-file edits, YAML diffs, deploy + verify commands, and troubleshooting table all live in that reference — don't duplicate them here.
Dynamic updates (runtime, no restart)
Once the container is up and a broker is reachable, two runtime-update flows are available — neither requires redeploying:
Dynamic config
Publish an upsert (per-key patch) or upsert-all (full snapshot) message to the mdx-notification topic with Kafka key behavior-analytics-config and headers:
event.type:upsert|upsert-all|request-config|ackreference-id:video-analytics-api-<uuid>(web-api originated),behavior-analytics-<uuid>(bootstrap reply), or the source-type literal (kafka/redis/mqtt) for direct-publisher upserts.
Body: {"status": ..., "config": <patch>, "error": ...}.
The listener validates each message at the envelope layer (rejects unknown keys, missing config, malformed status/error) and at the per-payload layer (rejects forbidden sections, bad item shapes). Successful upserts are persisted to disk, applied to every worker, and ACK'd back over the topic.
Full wire contract + ack semantics: references/dynamic-config.md.
Dynamic calibration
Publish to the same topic with Kafka key calibration and headers:
event.type:upsert-all(full snapshot) |upsert(per-sensor merge) |delete(per-sensor removal)timestamp: ISO-8601 UTC (YYYY-MM-DDTHH:MM:SS.fffZ).
Body: JSON sensor list (and ROIs / tripwires / homographies for upsert-all).
The listener validates against the vendored AJV schema before persisting. Schema violations log a calibration schema violation warning and are dropped — the previously-good calibration stays loaded.
Full wire contract + per-action validation policy: references/dynamic-calibration.md.
Both flows live entirely on the broker — the producer can be video-analytics-api, your own script, or any Kafka client that mirrors the wire shape. They're the recommended way to change configuration after the container is running, so the operator doesn't have to redeploy.
Routing rules
- If the user wants "the full stack" (UI / agent / perception): hand off to
vss-deploy-profilewith profilewarehouse(oralerts). Don't run this skill in parallel. - If the user wants to publish a runtime config / calibration update to an already-running container: walk the Dynamic updates section above. Both flows need a reachable broker.
- If the user describes a behavior-analytics behavior change they want to validate (new incident type, new ROI rule, new sensor): point them at
references/configuration.md,references/dynamic-config.md, orreferences/dynamic-calibration.mdbefore editing the JSON.
bump:1
04 同仓库更多 Skills
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
slack
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.