Viktor Shevchenko
Web developer from Kyiv
OpsRamp Story
From Netenrich to HPE
Act 1 — Netenrich (Early 2000s)
- Founded by Varma Kunaparaju and Raju Chekuri
- IT services company (Managed Service Provider)
What they did:
- Monitored customer infrastructure
- Responded to alerts
- Fixed incidents manually
Reality:
- Multiple tools (Nagios, SolarWinds, custom setups)
- Alerts everywhere
- Humans doing correlation
Act 2 — Pain at Scale (~2005–2013)
Founders ran operations daily and saw:
- 80–90% of alerts were noise
- Same incidents repeated across customers
- Root cause analysis = manual investigation
- Knowledge locked in engineers’ heads
Internal attempts:
- Scripts
- Partial automation
- Process standardization
Act 3 — Key Insight
Two conclusions:
- Services scale linearly
- Software scales non-linearly
Critical shift:
The value is not in reacting to alerts
The value is in how alerts are handled
That logic can be encoded.
Act 4 — OpsRamp is Born (2014)
- Spinout from Netenrich
- HQ: San Jose
Goal: Build a control plane over all IT systems
Key idea: Don’t replace tools → sit above them
Core capabilities:
- Auto-discovery of infrastructure
- Alert ingestion from multiple tools
- Event correlation (noise reduction)
- Topology mapping (dependencies)
- Automation (runbooks)
Act 5 — Early Growth (2015–2017)
- Focus on enterprises and MSPs
- Raised funding (Sapphire Ventures, others)
Why customers bought:
- Too many tools
- No unified view
- Manual operations didn’t scale
Act 6 — AIOps Shift (2017–2022)
Industry problem evolved:
Not “monitoring”
→ but “understanding signals”
OpsRamp evolution:
- Alert correlation → reduce noise
- Topology → understand dependencies
- Automation → reduce manual work
- ML → prioritize incidents
Act 7 — Market Context (~2020)
- Multi-cloud became default
- SaaS exploded
- Tool sprawl increased
Result: Complexity > human capacity
Customer demand:
- Fewer tools
- Central control
- Faster root cause
OpsRamp matched this exactly.
Act 8 — Acquisition by HPE (2023)
- Acquired by Hewlett Packard Enterprise
Strategic reason: HPE had:
- infrastructure
- hybrid cloud (GreenLake)
But lacked:
- modern operations layer
OpsRamp became:
- control plane for HPE hybrid cloud
Act 9 — Today
OpsRamp inside HPE:
- Part of GreenLake platform
- Observability + automation layer
- Foundation for AI-driven operations
Current focus:
- Hybrid / multi-cloud visibility
- Automation at scale
- AI copilots and context-aware operations
Key Takeaway
Same problem, different levels:
- Manual (Netenrich)
- Assisted (early OpsRamp)
- Automated (AIOps)
- Integrated (HPE platform)
Direction: Less human effort. More system intelligence
OpsRamp Story
By Viktor Shevchenko
OpsRamp Story
- 19
