This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

To Migrate Solarwinds APM to dedicated machine or NOT ?

We currently have Orion distributed as follows:

Main Engine (hosting NPM SLX, APM300, NCM, IPSla) + 3 Add'l NPM Pollers + 1 Add'l Web Console, with separate SQL Database server.

I understand that SolarWindsAPM can now run as a standalone product.

How can we determine if APM is consuming enough resources and warrants being migrated ?

Would it mean that users who currently access Orion NPM/APM etc via our Add'l Web console, would then need to access a separate web interface to view APM ?

The APM Admin guide, mentions that you clone your DB in order to separate NPM and APM. Does this mean if you currently monitor, poll NODES in NPM which also have components in APM being monitored, that these nodes must now be polled by both NPM and APM engines, and stored in each of their respective, and separate databases ?

If given choice to migrate APM or NCM to dedicated server/engine, which would make most sense ?

thanks in advance, any and all insight/ideas are welcomed.

ep

  • How can we determine if APM is consuming enough resources and warrants being migrated ?

    Probably the simplest way to determine to load effect on your server from APM would be to take an average baseline of your servers resources (CPU/Memory) for 10-15min, then unmanage all APM applications for the same duration collecting the same statistics and comparing the difference. This won't affect uptime statistics and shouldn't be down much longer than a reboot.

    Would it mean that users who currently access Orion NPM/APM etc via our Add'l Web console, would then need to access a separate web interface to view APM ?

    Correct. The additional Web Server can only point with a single standalone Orion instance. If you need a single pane of glass view of multiple Orion instances I recommend looking at the Enterprise Operations Console. It's similar to the Additional Web Server, but consolidates multiple Orion instances within a single web console.

    The APM Admin guide, mentions that you clone your DB in order to separate NPM and APM. Does this mean if you currently monitor, poll NODES in NPM which also have components in APM being monitored, that these nodes must now be polled by both NPM and APM engines, and stored in each of their respective, and separate databases ?

    Nodes are duplicated in this process as well, so you'll need to clean up both installations after performing the migration if you don't want APM nodes monitored by NPM, or NPM/NCM nodes monitored by APM. 

    If given choice to migrate APM or NCM to dedicated server/engine, which would make most sense ?

    Given you're license of APM is relatively small I don't imagine the resources saved on the poller would be sufficient to warrant the investment of time and resources. However, if you find that not to be the case, I'd recommend adding an additional poller and dedicating it to APM. This has the added benefits of a single Alerting Engine, Report Writer as well as the ability to maintain your additional web servers as is.