Private Cloud Overview
AppNeta provides two deployment options for AppNeta Performance Manager (APM): public cloud and private cloud. The public cloud offering runs as a service (SaaS) within the public cloud. The private cloud offering, APM-Private Cloud, runs as a virtual machine instance on a server within a customer network. APM-Private Cloud is typically used by customers whose network or security policy precludes use of the public cloud offering.
With APM-Private Cloud:
- All data remains within the customer network.
- There are no external network connections except where explicitly enabled. These include:
- Maintenance tunnel
- ISP resolution service
- Geo map service
Public cloud vs. Private cloud
Generally there is feature parity between the public and private cloud offerings with the following exceptions:
| Feature | Public cloud | Private cloud |
|---|---|---|
| Monitoring Points supported | Unlimited | 1000 |
| Usage monitoring at 10 Gbps | Yes | No |
| Global Monitoring Point access | Yes | No |
| System-level branding options | No | Yes |
| Organization-level branding options | Yes | Yes |
There are also some differences in Data retention and roll-up.
APM-Private Cloud deployment options
The APM-Private Cloud can be deployed on AppNeta-supplied hardware (the AppNeta Private Cloud Server (PCS)) or on customer-supplied hardware using either KVM or VMware hypervisors:
- If you are deploying on a PCS, see Private Cloud Server Setup.
- If you are deploying on your own hardware using KVM, see APM-Private Cloud - KVM Setup.
- If you are deploying on your own hardware using VMware, see APM-Private Cloud - VMware Setup.