Cloud Shell, New Integrations, and More

VirtualMetric DataStream now includes a PowerShell console in the browser, more than a dozen new integrations, and a new way to collect data from servers and virtualization hosts, where teams choose exactly what they collect. This update also brings guided learning for new users, built-in monitoring rules, and new controls for organizations managing branding and sign-in.

Here’s what’s new.

Cloud Shell opens a PowerShell console directly in the DataStream interface. A new button in the header docks the console on screen, and it runs the VirtualMetric cmdlets as the signed-in user, in whichever tenant they choose.

The same commands also run from a workstation. A matching PowerShell module with CLI sign-in gives teams the choice of working in the browser or from their own terminal. Both are backed by a public API covering pipelines, clusters, Quick Routes, the Library, and the Content Hub, so teams can script and automate the same operations they perform in the interface.

This update extends DataStream’s reach across network equipment, virtualization platforms, backup systems, and additional operating systems:

Eight new agent dataset types are also available, including scripts from the Library.

Host monitoring now uses one dataset per data model. Teams select the specific data they need for each host type and filter it at the source, so only relevant data enters the pipeline.

This applies across Windows, Linux, Microsoft SQL Server, failover clusters, Hyper-V, IIS, Storage Spaces Direct, SCVMM, and Solaris, AIX, and macOS hosts.

Microsoft Sentinel Smart Engine now includes a learning mode for Sentinel targets. Sentinel targets also gain coverage analysis and a Reduction tab with reduction statistics.

Twelve built-in monitoring rules now come ready to use on Standard and Enterprise plans, including a new rule for target delivery lag. Each rule can be enabled, disabled, or cloned as a starting point for custom rules.

Schema drift now appears as a Monitoring alert that shows the field-level differences, so teams can see exactly what changed in an incoming data structure. Director, device, and target lists also include a Monitoring column that shows each resource’s current monitoring state at a glance.

A new Guided tours hub walks users through the real product screens. It includes a Getting started tour for onboarding, the Pipeline Academy with 22 lessons covering the full pipeline lifecycle, and Scenarios: complete data flows built on Content Hub packs and tailored to Microsoft Sentinel, Splunk Enterprise Security, and Elastic Security.

All plans include five built-in themes, and every user can choose their own, including an appearance that follows their system’s light or dark mode. On the Enterprise plan, appearance settings also let organizations define their own themes and branding across the platform.

Tenants can now require single sign-on for their users, with self-service opt-in and an owner break-glass account for recovery.

The Library now ships platform-provided content, with each tenant owning its own copy. This includes simulation samples, Grok pattern packs, and schemas for Microsoft Sentinel, ASIM, and OCSF tables.

Deleted devices and Directors can now be restored directly from their audit log entry.

The pipeline editor now autocompletes field, schema, Grok pattern, and lookup table names, and the debugger shows what a run rerouted.

Pipelines managed through GitOps are read-only in the console, and pushes land on staging, keeping the repository as the single source of truth for those pipelines.

Directors running on Azure Container Apps can reuse an existing managed environment, and their published listener ports can be viewed and changed from Connection settings. Orchestrated Directors can now run additional device types and agentless deployments.

Health pages and Quick Routes follow a new, consistent layout. Cost & Usage adds a tenant-wide rate card, tenant-scoped statistics, and per-target delivery rows.

Sign-in, sessions, MFA, SSO, and API tokens have been further hardened. Audit entries now record who did what and what changed across a wide range of resource types, from users, roles, and tenants to vault secrets, detection rules, devices, Directors, and GitOps sources.

These are the highlights – this update also includes a broad set of fixes across devices, Directors, pipelines, the interface, and sign-in.

These changes give teams more ways to work with DataStream, whether from the interface, a PowerShell console, or their own scripts, and bring more of their infrastructure into the pipeline. We’ll continue building on both in upcoming updates.

As always, feedback from real-world deployments helps guide future development. If you would like a walkthrough of any of these features or want to share suggestions, we would be glad to hear from you.