Your infrastructure. Under control. Before the alert.
neoo.× Monitoring
Your infrastructure.
Machines, sessions, certificates: hundreds of signals at the same time.
The watch
One tower sweeps the whole fleet.
Health, performance and capacity, watched continuously.
P1 → P4
A signal weakens. The tower sees it first.
Real impact is separated from noise, prioritised P1 to P4.
From signal to action
The fix leaves before the incident.
Analysis, maintenance plan, human approval: the incident never happens.
Neoo Monitoring
Under control. Before the alert.
Health, performance and capacity: Neoo anticipates risks before they become incidents.
- P1 → P4 alerts
- Capacity from real usage
- Segmented Neoo SSO
The film is loading
0%
NEOO MONITORING
Health, performance and capacity: Neoo anticipates risks before they become incidents.
- P1 → P4 alerts
- Capacity from real usage
- Segmented Neoo SSO
Your entire fleet, in one cockpit
Monitoring that connects every signal.
Parallels RAS, Ovastack, Echo and Active Directory converge in one operational view, without switching tools for every diagnosis.
Cockpit & search
Run the multi-company fleet from one overview and find any resource instantly.
- Health KPIs and prioritised queue
- Ctrl+K search: VM, user, node
- Shareable navigation and wallboard mode
Fleet & agents
Move from the whole fleet to the detail of a VM, node or Echo agent.
- Real CPU, RAM and volumes
- Allocation, OS and Echo coverage
- Certificates, version and uptime
Sessions & experience
Trace a poor user experience back to the session and the VM carrying it.
- WTS state and duration
- Logon, latency and protocol
- Device, idle time and export
Actionable alerts
Focus the team on incidents that genuinely require a decision.
- P1 to P4 priorities
- Impact score and noise reduction
- Acknowledge, escalate, resolve
Capacity & forecasts
Size resources from real usage instead of one isolated peak or a misleading average.
- Median, P95, P99 and confidence
- Usage windows by customer
- Disk saturation forecast
Security & coverage
Monitor access safeguards and document precisely what should be excluded.
- TLS, SNI, chain and expiry
- Echo coverage and AD lockouts
- Targeted expiring rules
Maintenance & tickets
Turn an alert into traceable work, with human approval at the right moment.
- Reboot, CPU, RAM and disk plans
- Windows with no connected users
- Context-rich Neoo tickets
Reports & governance
Measure service and share a segmented view, from operational reporting to product updates.
- Statistics, MTTR, backlog and recurrence
- Neoo API health and release log
- Read-only partner views
From signal to decision
Less noise. More context.
Neoo Monitoring qualifies impact, keeps the useful history and prepares action. Sensitive operations remain under your team’s control.
Hold the button to follow one weak signal all the way to a scheduled fix.
Alert centre
Critical volumeVM-PROD-07 · less than 10 GB free
Action required
Certificate renewalportal.example · expiry approaching
Plan next
Capacity reviewStable usage above P95
Recommendation
- ObserveSources are consolidated into a local, revisioned snapshot.
- PrioritiseImpact, severity, freshness and noise shape a useful queue.
- DecideTechnical and customer context follow the alert into the ticket.
- LearnTimeline, MTTR, backlog and recurrence make progress visible.
One weak signal awaits a decision
One weak signal awaits a decision Analysing and planning… Correction scheduled · incident avoided88signals to qualify
Demo example. Real alerts and statuses come from your cockpit.
Anticipate instead of reacting
Capacity grounded in real usage.
Capacity Advisor compares 24, 48 and 72-hour windows, exposes data coverage and makes no recommendation until the signal is sufficiently reliable.
- Hours without users can be excluded from CPU and RAM decisions.
- Volumes are tracked independently, with hysteresis to avoid false positives.
- A recommendation can become a traceable Neoo request, never a silent Ovastack action.
- Maintenance can wait for a window with no connected user.
Architecture that protects Neoo
One collector. Every view. No request storm.
Monitoring centralises collection, persists the exact state and serves every screen from a local snapshot. The upstream API stays protected, even when many people open the cockpit.
Short signed token, mandatory Bearer auth and server-side permission checks.
A partner can receive a read-only view limited to its signed scope.
No synthetic history: actual coverage accompanies every trend.
Frequently asked questions
Neoo Monitoring, with no grey area.
Which sources does Neoo Monitoring consolidate?
The cockpit brings together available data from Parallels RAS, Ovastack, Echo agents and Active Directory, then links it to alerts, tickets and maintenance plans.
Does monitoring act directly on Ovastack?
No. Sensitive actions prepare a Hermes job or a Neoo request that requires approval. The product does not promise silent infrastructure changes.
Are metrics instantaneous?
The feed is near real time: the urgent cycle is paced and viewers read a persistent snapshot. This prevents duplicated calls when multiple users open the app.
What happens when there is not enough history?
Coverage and freshness stay visible. Charts and recommendations wait for enough coherent points instead of inventing a trend.
See the cockpit in action
Turn your infrastructure into an operational flow.
Discover how Neoo Monitoring connects your fleet, users, alerts and decisions in one centre.