Updated September 26, 2016
You can scale the Orion Platform in one of two ways:
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.
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.
The image below is a more detailed version of the first image in this article. EOC is comprised of four main components:
EOC pulls the following data types through the SolarWinds Information Service:
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:
|137||460||13||782||2||3 apps |
|1 source||2||1.277 MB|