Use Orion Remote Collectors with SAM

In SAM deployments that use node-based licensing, you can add Orion Remote Collectors (ORCs) to distribute monitoring loads. These lightweight polling engines:

• Use Orion agent technology to communicate with the Orion Platform.
• Do not require a direct connection to the Orion database.
• Are easy to deploy in remote locations, thanks to their simplified architecture.
• Can poll and store data up to 24 hours with no connection to the polling engine, making them useful for unreliable networks, DMZs, and devices that don’t support Orion agents.

Polling jobs run independently of the Main Polling Engine and any Additional Polling Engines (APEs). Results are stored locally, and then forwarded to the Orion server via agents.

For requirements, see Scalability Engine Guidelines for SolarWinds products.

Note the following details about using Orion Remote Collectors with SAM:

• ORC polling is not supported for nodes monitored by Orion agents; for example, if AppInsight for IIS is assigned to a node.
• In a SolarWinds Network Automation Manager (NAM) deployment that combines SolarWinds Network Performance Manager (NPM) with SAM, ORCs can be used for both NAM- and SAM-supported features.
  
• The following SAM features do not currently support ORC polling: 
  • API Poller monitoring
  • AppOptics integrations on AppInsight for IIS nodes
  • Container monitoring
  • Hardware Health monitoring for UCS or Nutanix devices
  • JMX monitoring
• The following component monitors do not currently support ORC polling: 
  • JMX Monitor
  • MAPI User Experience Monitor
  • Nagios Script Monitor
  • NNTP Monitor
  • Oracle User Experience Monitor
  • RADIUS User Experience Monitor
  • TACACS+ User Experience Monitor

To display ORCs currently deployed in your environment:

1. Click Settings > All Settings > Manage Agents.
2. On the Manage Agents page, click the Remote Collectors tab.
   
   

To learn more about Orion Remote Collectors, see the Scalability Engine Guidelines.