PRTG reads your past.Trends Explorer tells your future.

Turn existing PRTG history into operational Views, governed objectives, forecasts and controlled deployment — across one or many monitoring configurations.

No crystal ball. Just your data — refined into foresight.

Current release and PDF guides

Trends Explorer Desktop 2.20.12.0 · 12 October 2026 · Bundled Engine 2.20.12.0

Starter: one team / Engine Instance, up to 20 Trends sensors. Enterprise: unlimited teams, up to 50 Trends sensors per team. Both include Qbilon integration and support up to 50 output channels per Trends sensor. PRTG and Qbilon licences are separate.

Download — sign in requiredStarter and Enterprise pricing

PDF documentation for 2.20.12.0: the End User Guide covers everyday workflows, native PRTG warnings and Qbilon investigation. The Installation and Administration Guide covers upgrades, Engine packages, connection settings and verification. Both are available in the Trends Explorer downloads after sign-in.

Already signed in? Open Trends Explorer downloads.

One workspace for operational foresight

Trends Explorer brings the full lifecycle together: discover useful signals, build service-level Views, define channel objectives, review AI proposals, validate readiness, deploy the approved result and keep the forecast visible in PRTG.

See direction

Understand whether a value or service is improving, stable or moving toward risk.

See uncertainty

Forecast ranges, data coverage and confidence show how much trust the result deserves.

See the service

Combine related sensors and channels into one reusable operational View.

From sensor lists to operational Views

Build Views around a component, capacity question, application or complete service. A View can use one source or combine multiple sensors and channels on a common timeline while retaining traceability to the original PRTG objects.

  • Single-source and combined multi-sensor Views
  • Per-channel participation and analysis model
  • Service, capacity, performance and diagnostic perspectives
  • Movable chart windows and a fast dashboard overview
PRTGPlugins Trends Explorer dashboard with configured Views
Organize component, service and executive perspectives from one dashboard.

Your SLA and operational objectives — translated into governed, measurable monitoring and trends

Turn agreed SLA commitments and operating policies into governed objectives for the PRTG channels that define and evidence the service — availability, latency, capacity, backlog, error rate, backup age or any other relevant signal already present in your monitoring. Each approved objective records what good looks like: the expected direction, threshold, bounds, forecast model and the evidence behind the decision. Trends Explorer then turns that objective into foresight: when is the limit likely to be crossed, how much time remains and what is the probability of a breach within the selected forecast horizon?

Flow from monitoring evidence through proposed and approved channel objectives to forecasts
Evidence becomes a proposal; operator approval determines which objectives affect deployment and forecasting.
ProposedVisible and editable for review, with confidence and rationale.
ApprovedEligible for deterministic threshold forecasting and deployment.
Disabled or lockedIntentionally inactive or protected from proposal changes.
Which signals define the service?Combine evidence across infrastructure, applications, databases and delivery paths — without pretending that every available channel belongs in the service View.
When does risk become action?Approved objectives produce time-to-threshold and breach-probability outputs instead of waiting for a limit to fail.
Why this objective?Direction, limit, evidence, rationale and confidence remain visible so an operator can approve, edit, lock or disable the proposal.

From policy to action: qualifying sources gain Days to threshold and Breach probability outputs. The same governed result is available as statistics and as a clear Service Outlook message in PRTG Maps. Maintenance-policy interpretation is available for review.

View definition and forecast preview
Choose sources, history, forecast horizon and model, then preview before deployment.

Forecast beyond the current moment

Every View is configurable. Select the relevant history, forecast horizon, analysis offset and model, then inspect the chart before accepting the result.

Trend slopeRate and direction
Forecast valueEstimated future value
Anomaly scoreRecent unusual behavior
CoverageSource completeness
ConfidenceFit, variability and evidence
Threshold riskTime and breach probability

AI assistance with human control

Package a selected, structured PRTG inventory for AI analysis. Ask for clearer service Views, useful channel roles, per-channel objectives, analysis models, monitoring gaps and duplicated signals. Work manually with an AI service you already use, or configure a supported provider for an automatic exchange.

Anonymized AI inventory scope and analysis perspectives
Choose the inventory scope, primary perspective, preset and operational questions.
AI assists the design — never the active monitoring runtime.Use AI when you want help turning inventory and SLA context into proposed Views, channel roles, objectives and models. Every proposal remains separate until you review and approve it. Once the approved configuration is deployed, AI leaves the operational path completely: the Engine reads PRTG data and performs the statistical calculations autonomously. No AI provider, API key, live AI connection or running Desktop is required for active monitoring.

Teams and multiple configurations without identity confusion

Manage saved Trends configurations from the Configurations workspace using local, shared or network locations. Starter supports alternative configurations for the same team and Engine Instance: deploying another version updates that same sensor set. Enterprise also supports independent teams and separately identified Engine Instances, each with its own Views and deployment scope.

The same PRTG source sensors can support several teams wherever their data is relevant to each team’s own service. A team does not have to adopt every channel from a shared sensor: it can select only the channels that explain its service, combine them with other sources and govern them with its own channel objectives, forecast models and approved thresholds inside its own configuration.

Shared configuration workspace with multiple separately identified monitoring configurations
A shared repository can support teams while each monitoring configuration retains its own identity and deployment package.
Configuration registryDiscover and activate available configuration files from one window.
Shared PRTG evidenceReuse relevant source sensors while each View selects only the channels its service needs.
Team-owned objectivesApply configuration-specific models, thresholds and approval states to the selected channels.
Stable instancesFile names and locations do not silently redefine Engine identity.
Practical example: one Hyper-V sensor, different service questions

A platform team can use host CPU, memory pressure and cluster capacity channels from a Hyper-V sensor with infrastructure-level warning limits. An application team can reuse the same sensor but select only the VM availability, storage latency or resource-pressure channels relevant to its application service. Both teams start from the same PRTG evidence, yet build different Views and approve thresholds that reflect their own responsibilities — without duplicating the source monitoring.

Deploy approved insight through a workflow that guides you

Desktop leads you through six resumable stages: choose what will be published, review and approve objectives, check readiness, build the Engine Installer, verify the Engine and synchronize the selected Trends sensors and Maps. Each stage explains what is needed, checks the current state and lets you continue from the last completed point.

The hand-off is one self-contained EXE.Desktop builds a configuration-specific Engine Installer with the precompiled runtime and approved definitions included. Copy it to the owning PRTG Probe server, run it, and the installer prepares the Engine under Custom Sensors\EXEXML. AI credentials and provider connections are never included in this operational package. Return to Desktop: the workflow verifies the installed Engine and continues with sensor and Map deployment.

Do Desktop or AI need to stay running? No. Once deployed, the Engine runs autonomously at the Probe, reads the configured source PRTG data and produces the approved Trends results inside PRTG using its packaged statistical logic. Reopen Desktop — and optionally use AI again — only when you want to review, refine or redeploy the configuration.

  • Read-only readiness checks before target changes
  • Clear approval and publication-scope gates
  • Version and package-state verification
  • Resumable progress across the Desktop and Probe hand-off
  • Identity-aware updates with explicit impact when replacement is unavoidable
Guided deployment and sensor synchronization
Keep every deployment stage visible, resumable and reviewable.

Keep foresight visible inside PRTG

The Engine keeps every approved View alive inside PRTG. The Trends sensor is the numerical monitoring and alarm object: it carries the calculated channels, including Days to threshold and Breach probability wherever an approved objective applies, while PRTG applies the reported warning state, any configured channel limits and notification rules. The matching Map component presents the same Engine result as a multi-channel forecast, a traceable threshold table and a plain-language Service Outlook.

T01 SQL Service Health Overview combining several PRTG channels and forecasts
T01 — SQL Service Health Overview: several reachability, SQL, CPU and memory channels become one service-level history and forecast without losing their individual identities.
PRTG Trends Map statistics showing approved objective thresholds, forecasts and source coverage
Statistics & sources: see the current value, forecast, trend, approved threshold, probability within the horizon, coverage and the source sensors behind every channel.
PRTG Trends Map Service Outlook explaining an approved objective that needs attention
Service Outlook: translate the same approved objective into a clear situation report — which channel needs attention, whether the limit is already breached or forecast to be reached, and within what horizon.
1. Approve the objectiveThe operator confirms the direction, threshold, model and evidence that define attention for that channel.
2. Let the Engine forecastThe deployed Engine evaluates the approved objective continuously from the available PRTG history.
3. Alert and explainEngine 2.20.12.0 reports a native PRTG Warning when a threshold crossing is projected within 90 days, even with Maps disabled. PRTG applies your notification rules; the optional Map explains the same threshold outlook.
Service-level forecast chart with prediction intervals
A service View with normalized history, trend lines and forecast intervals.

Built for practical, repeatable foresight

The result is a repeatable operating model: inventory, understand, design, govern, deploy, measure, predict and learn. New measurements improve the next iteration while the evidence remains visible.

  • Statistics-first operation with optional AI assistance
  • Traceable sources, provenance and explicit confidence
  • Reusable Views for different services and audiences
  • Controlled proposals, approvals and deployment scope
  • Multi-configuration operation for growing environments

Learn. Refine. Evolve.

PRTGPlugins Trends Explorer turns monitoring history into a clearer view of where your services are heading — and what deserves attention next.

PRTG reads your past. Trends Explorer tells your future.
No crystal ball. Just your data — refined into foresight.