Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Enterprise Operations Console (EOC) > What is Enterprise Operations Console and how does it work?

What is Enterprise Operations Console and how does it work?

Created by Anthony.Rinaldi_ret, last modified by Anthony.Rinaldi_ret on Sep 26, 2016

Views: 148 Votes: 0 Revisions: 2

Updated September 26, 2016


You can scale the Orion Platform in one of two ways:

  • Add Additional Polling Engines (APE) to scale horizontally
  • Deploy multiple Orion Platform installations and roll them up into the Enterprise Operations Console

This article describes the Enterprise Operations Console (EOC) and how it works. The main functionality of EOC is to aggregate data from multiple Orion Platform installations, and to display it like the Orion Web Console.


  • EOC 1.6.3


In the image below, there is a worldwide network with teams responsible for managing their respective geographic regions. An Orion Platform installation resides in North America, EMEA, and APAC. The global Network Operations Center (NOC) and Management Team requires a roll-up of all the servers into a single installation for status, alerting, reporting, and more.

SolarWinds EOC aggregates the current status of your Orion Platform installations and presents the data in the EOC Web Console. Administrators can restrict what data each EOC user can see. These restrictions can be set individually by customizing user settings, and on a group level by defining roles.


The EOC Web Console is pictured below. A common misconception about EOC is that it pulls all the data from each Orion server into the EOC database. EOC actually pulls high-level information, such as current status, alerts, events, syslog and traps. Any data beyond that, when you click an item in the EOC Web Console, you are redirected to the Orion server where that item resides.

Let's walk through an example.

  1. In the EOC dashboard, I see that the Switch sales is down in the Global Nodes with Problems resource.
  2. I click on Switch sales, and am redirected to the Orion server in North America. The node details page for that device displays.
  3. I can perform my investigation, and return to my global EOC dashboard when finished.


How does EOC work?

The image below is a more detailed version of the first image in this article. EOC is comprised of four main components:

  • Orion Poller
  • Information Service
  • Website
  • Database


EOC pulls the following data types through the SolarWinds Information Service:

  • Alerts, Events, Syslog, Traps (last 24 hours worth of data)
  • Node, Volume, and Interface data (no historical data)
  • APM data (no historical data)
  • NetFlow (no historical data)
  • IPSLA Manager (no historical data)
  • Wireless (no historical data)
  • NCM (no historical data)
  • UDT (no historical data)
  • IPAM (no historical data)
  • Support for displaying Orion Groups

The SolarWinds Information Service (SWIS) module exists in EOC and Orion products. The service provides a single point of communication, and a simple and efficient mechanism to query the servers. All communication with the SWIS module is encrypted using SSL and is on port 17777.

The communication module uses Windows Communication Foundation (WCF) as its basis. This enables other applications, websites, scripts, and application modules to communicate with it. WCF also provides security, reliablity, and several transport and encoding options. You can build several types of messaging protocols, such as REST and SOAP, with it.

The SWIS module provides a simple query interface that allows the client to execute a read-only query written in the SolarWinds Query Language (SWQL). SWQL is similar to the SQL language, with a few deviations.

How does EOC scale, and how many Orion servers can EOC handle? Typically you can roll up 20 to 25 SLXs into one EOC instance. You can exceed this recommendation, as long as the total number of elements feeding into EOC is fewer than approximately 600,000.

How much traffic should I anticipate between the Orion servers and EOC? The answer varies, but the table below can give you an idea of what to expect:


Nodes Interfaces Volumes Events VoIP APM NetFlow Wireless Bytes
10 10 13 782 0 0 0 0 625 kB
20 20 13 782 0 0 0 0 700 kB
50 50 13 782 0 0 0 0 822 kB
100 100 13 0 0 0 0 0 479 kB
100 100 13 782 0 0 0 0 1.183 MB
137 460 13 782 2 3 apps
37 components
1 source 2 1.277 MB
Last modified
13:40, 26 Sep 2016