Skip to content
vScope Support Page

Studio

Studio extends vScope discovery to cover systems without native probes. It brings custom data into the asset repository while keeping collection, credentials, and storage inside your environment.

What Studio adds

Section titled “What Studio adds”
  • Custom integrations: Bring assets from in-house tools or third-party systems that lack a native probe.
  • Unified asset handling: Imported assets are stitched, versioned, and available in tables, dashboards, reports, and Tracker.
  • On‑prem execution: Runs on the vScope server or discovery proxy; credentials and data stay local.
  • Flexible connectors: Supports scripted or API-based collectors for structured sources.

When to use it

Section titled “When to use it”
  • Coverage is needed for a source without a built-in probe (custom, legacy, niche).
  • You want to prototype asset ingestion before requesting a native probe.
  • Structured data exists outside the discovery scope (APIs, scripts, exports) and should live in the repository.
  • Assets must be represented even when not directly discoverable (e.g., planned or offline equipment).

How it works

Section titled “How it works”
  1. A Studio integration runs as part of discovery, from the vScope server or proxy.
  2. It authenticates to your data sources (credentials always stay local).
  3. It fetches and stores assets as Studio assets in vScope.
  4. If matching data exists, relationships are created between Studio assets and existing assets in the repository.
  5. Data from the data source can be fetched as tags to support filtering, grouping, and analysis.
  6. All data is automatically updated during discovery, just like any other asset.

Scope and boundaries

Section titled “Scope and boundaries”
  • Designed for custom asset and tag ingestion; scheduling and history stay part of core discovery.
  • Best for structured, repeatable sources; ad-hoc/manual data fits better in one-time tag import or by creating tags.
  • Complements standard discovery; it does not replace native probes where they exist.

Developer guides and connector samples are available on request via customersuccess@vscope.net.

See also

Section titled “See also”
  • vScope Studio for feature highlights.
  • Discovery for the standard discovery that Studio extends.
  • Assets to learn more about how assets are structured and used.