Skip to content
RezolveITDocumentation

AIOps

AIOps is the operations launchpad for keeping infrastructure and business services healthy. Raw monitoring signals arrive as events, get correlated into actionable alerts, and are judged against the business services they impact — the chain this guide covers in Alerts & Events. Around that spine sit the surfaces that tell you where problems are trending and what the environment even looks like: anomaly detection, service health, discovery, and service mapping, covered in Service Health.

The AIOps launchpad home

What it covers

Section titled “What it covers”
Area What you do there
Alerts & Events Triage correlated alerts, acknowledge and close them, and trace an alert back to its raw events — see Alerts & Events.
Service Health Watch anomaly alerts, business-service health, discovery, and service mapping — see Service Health.

The navigation rail

Section titled “The navigation rail”
  • Home — the launchpad dashboard.
  • Alerts and Events — list entry points for the correlated alert queue and the raw event stream behind it.
  • Anomaly alerts — metric deviations flagged by anomaly detection, ranked by anomaly score.
  • Impact / Service health — the rollup of business-service health, worst open-alert severity, and availability.
  • Services — the business/application service list (the service-map endpoints alerts impact).
  • Discovery — scheduled discovery runs, their targets, MID server, and last-run results.
  • Service Mapping — top-down mapped business services, their discovered configuration items, and map completeness.
  • MID Servers — the status, validation, and queue health of each MID server.
  • Synthetic monitoring — scheduled synthetic checks and their uptime.
  • Log Viewer — a live, filterable log/event stream.
  • AIOps Dashboards and AIOps configuration center — reporting and configuration surfaces for the launchpad.
  • Reports — cross-cutting reporting, shared with every other launchpad.

Every list and record you open in this launchpad follows the same toolbar and layout conventions used everywhere else in the app — that shared behavior is documented once in the launchpads/shared guides rather than repeated per module.