Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Enterprise Operations Console (EOC) > EOC Documentation > EOC Administrator 2.1 Guide > Introduction to SolarWinds EOC

Introduction to SolarWinds EOC

Updated: September 12, 2017

In some situations, organizations might choose to deploy SolarWinds products on multiple Orion servers (referred to as a distributed deployment). For example, a distributed deployment could be beneficial due to mergers and acquisitions, or because of how an MSP provides services to clients. In a distributed deployment, each Orion server operates independently and cannot access data from the other servers.

The Enterprise Operations Console (EOC) offers a comprehensive view of the instances in distributed deployment (called SolarWinds Sites). EOC provides insight into alerts, global reporting capabilities, and a compilation of current status information from all entities at each site. EOC users can view, triage, and troubleshoot issues that might span multiple sites.

File:Success_Center/Reusable_content_-_InfoDev/EOC/EOC_2.0_Administrator_Guide/0010-Introduction_to_SolarWinds_EOC/EOC_Intro.png

Get started

To begin using SolarWinds EOC, administrators must:

  • Install SolarWinds EOC.
  • Add SolarWinds Sites. SolarWinds EOC can connect to any SolarWinds Site that runs on a supported version of the Orion platform.

  • Create user accounts and define what SolarWinds Site data each user can access.

    Administrators can specify which SolarWinds Sites the user account can access. They must also associate each EOC user account with a SolarWinds Site account which is used to access SolarWinds Site data. The privileges granted to the associated SolarWinds Site account determine what data the EOC user can view and what actions the user can perform (for example, whether the user can acknowledge alerts in EOC).

Access data from SolarWinds Sites

After you add SolarWinds Sites, you can view data from all connected sites:

Last modified

Tags

Classifications

Public