Lately I have had a couple conversations with some of you, and it became clear that there is some confusion lately on standalone vs. module in Orion means. Do I get less functionality if I deploy one way or the other?
First, let me set some context for those of you not familiar with what I am talking about. Until recently, if you wanted to purchase our SolarWinds Application Performance Monitor (APM) or SolarWinds IP Address Manager (IPAM) product, then you had to own Orion Network Performance Monitor (NPM). Now, with the most recent releases of both of these products, this is no longer true. We also just recently released a new product, SolarWinds User Device Tracker (UDT), which can be installed either way as well.
So why do this? It seems confusing. There are two main reasons:
- Some folks came to look at SolarWinds whose need was just for Application Monitoring or IP Address Management, but they already owned an NMS and didn’t need or want to purchase our NPM product.
- In other cases, we had existing customers of NPM and other teams/groups within their organization saw it, learned that we had APM for apps and servers, and they wanted it; however, the two groups did not want to share the same database because they had different approaches to the product (or they just hated each other, or whatever).
Question: Do I get different functionality by installing standalone vs. a module? Meaning do I get functionality by installing one way that I do not get installing the other way?
Answer: No, they are identical in functionality. The only difference is that if you own NPM currently, then purchase APM and choose to deploy standalone and not as a module. In that case, you would now have two web consoles, two database, etc. so you will lose the single pane of glass. I have put together an image, below, to help illustrate this.
Question: If I want to deploy as a module, does NPM have to be the base or can any standalone product be the base/initial product.
Answer: Any standalone product (with the exception of NCM) can be the base product and the other standalone products can be installed on top as modules. The only products which have any relationship/dependency is IPSLA Manager and NTA, which both require NPM to be present, see the below image as an example.
The ultimate goal of this decision on our part was to give customers more flexibility in deploying our technology.
So which Orion-family products can now be deployed as either stand-alone or a module and which can only be deployed as a module for Orion?
Stand-alone or Module:
Module Only (requires NPM):
- IPSLA Manager
Virtualization Manager (formerly Hyper9) and Storage Manager (formerly Storage Profiler) live on a different platform, and while we do have or will have integrations with these products, the standalone vs. module discussion doesn’t apply.