Skip to content

AI Native IT Operations

AI Native IT Operations

An IT operations solution that handles monitoring and incident analysis with evidence, with agents also covering assets, security and cost management. Managed targets are defined in the CMDB, and actions run after approval.

IT operations solution

Root cause analysis based on the CMDB and observability data

Operated assets are defined in a CMDB (164 CI classes, 48 relation types), and cause hypotheses with confidence are computed from observability data and dependencies to propose actions. Actions run after approval.

  • Alarms merged into incidents
  • Cause hypotheses, confidence and evidence
  • Actions proposed, approved, then run with records

Suited to these organizations

  • Operations teams whose alarms are spread across several consoles, which slows root cause analysis
  • Teams that reconcile the CMDB and asset inventory by hand
  • IT departments that must report on security logs and cloud costs together

Common situations before adoption

  • Scattered alarmsOne incident fires server, network and storage alarms across consoles, slowing decisions.
  • Slow root cause analysisPeople match dependencies and changes by hand, so recovery takes long.
  • Manual asset and cost workAssets, licenses and costs are gathered and organized separately.

AI Native IT Operations

Key features

  • Incident merge and noise reduction

    Groups alarms from the same failure into one incident using CMDB dependencies.

  • Root cause analysis

    Computes cause hypotheses and confidence from CMDB relations and observability data, with evidence.

  • ITSM

    Covers incidents, problems, changes, service catalog, SLA, approvals and knowledge.

  • ITAM inventory

    Collects hardware and software assets by agent, agentless and zero-footprint methods.

  • Agentic SIEM

    Finds threats with 41 built-in detection rules (25 core, 16 web) and 3,698 rules converted from SigmaHQ, while security agents triage and respond.

  • FinOps

    Agents report cost analysis, budgets, forecasts, renewals and EOL.

From alarm to action

Alarms turn into incidents and causes, then approved actions.

  1. Collect signals

    Alarms, logs, metrics & changes

  2. Merge incidents

    Grouped by CMDB dependencies

  3. Analyze causes

    Hypotheses, confidence & evidence

  4. Approve action

    Runbook proposed, then approved

  5. Run and record

    Execution kernel and audit

FormatSignal collection, incident grouping, root cause analysis and actions.

ApprovalSignalsAlarmsLogs and tracesMetricsChange eventsMerge and correlateCMDB dependenciesNoise reductionIncident groupingRoot cause analysisHypotheses and confidenceBlast radiusChange correlationActionABFOS execution kernelRunbooks and auto-remediationApprovalExecution recordApprovalSignalsAlarmsLogs and tracesMetricsChange eventsMerge and correlateCMDB dependenciesNoise reductionIncident groupingRoot cause analysisHypotheses and confidenceBlast radiusChange correlationActionABFOS execution kernelRunbooks and auto-remediationApprovalExecution record

Roles

Agents narrow down the likely causes, and the operator decides what action to take.

Roles
StageAI agentPeople
MonitoringMerges alarms and reduces noiseConfirm incidents
AnalysisCause hypotheses and blast radiusReview hypotheses
ActionWrites runbooks and actionsApprove or reject
SecurityDetects, triages & investigatesDecide response
Assets and costInventory and cost reportsDecide purchases and retirement

Scope of operations and detection

The scale of models and rules implemented in the product.

164

CI classes

Basis Defined with 48 relation types

41

Built-in detection rules

Basis 25 core, 16 web, plus 3,698 Sigma-converted

43

Built-in specialist agents

Basis 31 skills across monitoring, ITSM, assets, security & RCA

66

Use cases

Basis IT, security, enterprise, public, manufacturing, quant

Use cases by areaHow the 66 use cases on the same platform are distributed.

Use cases by areaBar chart of use cases by areaAI Native IT ops12AI security ops12Enterprise ops11Civil services11Manufacturing10Quant (finance)10AI Innovation Center use case catalog
Use cases by areaBar chart of use cases by areaAI Native ITops12AI security ops12Enterprise ops11Civil services11Manufacturing10Quant (finance)10AI Innovation Center use case catalog

Delivery options

Ways to use this product. Each option lists what is included, who operates what and the steps to start.

  • Installed SaaS

    Installed in your environment and run by you
    What is included
    Installed in your cloud or on your own servers, with observability data loaded into Lumi Cloud or Lumi in your environment.
    Operation
    You operate it, and AIONIS handles installation, updates and technical support. Real assets are connected step by step after your security review.
    Getting started
    Scenarios are validated with synthetic data and a virtual CMDB, then the real asset inventory is collected to build the CMDB. After monitoring and RCA pilots, scope expands to action automation with approval gates.
    Learn more
  • Consulting

    Civil services and AX
    What is included
    An AIOps transformation workshop and AX assessment define the target use cases and success criteria.
    Operation
    Run by AIONIS consultants and engineers.
    Getting started
    Start with a workshop where business and IT staff collect operational problems.
    Learn more
  • Education

    AI Innovation Center
    What is included
    A practical course that moves through CMDB, ITAM, ITSM and ITOM to AIOps and SecOps.
    Operation
    Run by the AIONIS AI Innovation Center.
    Getting started
    Start with stage 3 of the AI Native transformation course (AI Native ITOps in practice).
    Learn more

RolloutFrom synthetic data to real assets, step by step.

  1. Virtual environment

    Replay with synthetic data and a virtual CMDB

    Output Scenario validation

  2. Build CMDB

    Collect real inventory, link CIs

    Output CMDB and service map

  3. Monitoring and RCA

    Pilot incident merge and cause analysis

    Output Analysis report

  4. Automate actions

    Runbooks with approval gates

    Output Operating model

Use cases

Typical use cases carried out with features built into the product. These are not specific customer cases.

  • Alarm incident merge

    Situation
    One failure fires dozens of alarms across consoles.
    What the AI agents do
    Alarms from the same failure are grouped into one incident by CMDB dependencies and assigned.
    Result
    The owner decides from one incident.
  • Saturation forecasting

    Situation
    Resource saturation is noticed late.
    What the AI agents do
    Trends in observability data forecast saturation and recommend scaling, executed after approval.
    Result
    Action happens early, with evidence.
  • First-pass security triage

    Situation
    Too many security logs lead to missed events.
    What the AI agents do
    Logs are normalized and detected, and security agents triage and investigate first.
    Result
    People respond starting from triaged events.

Adoption consulting for your industry and operating environment

Tell us your industry, size and current systems. We will propose the right products and delivery option.