28. @solarwinds
The SolarWinds, SolarWinds & Design, Orion, and THWACK trademarks are
the exclusive property of SolarWinds Worldwide, LLC or its affiliates, are
registered with the U.S. Patent and Trademark Office, and may be
registered or pending registration in other countries. All other SolarWinds
trademarks, service marks, and logos may be common law marks or are
registered or pending registration. All other trademarks mentioned herein
are used for identification purposes only and are trademarks of (and may be
registered trademarks) of their respective companies.
Editor's Notes
Proposed timeline-
SolarWinds overview (5)
FITARA overview (5)
Improving your FITARA scorecard (18)
IT tools consolidation
Modernize and consolidate
Improve compliance
Additional resources (2)
Demonstration (25)
Q&A (5)
We are simplifying the Orion Server instances on the bottom of slide; Orion Servers require a SQL Server, and potentially a NetFlow Storage Database.
New release details from release history-
06.06.19 – Enterprise Operations Console 2.2
Increased Scale
Support for up to 100 SolarWinds Orion Platform instances
Improved Performance
Increased web performance by 35%, significantly reducing page load times
08.14.18 – Enterprise Operations Console 2.1
Improved and Updated UI
Improved Enterprise Environment Summary to allow for additional flexibility when customizing views, and unique controls for on-demand filtering; examples include Orion® Site Status, Site Filter, and Enterprise Nodes widgets
Enterprise Summary Tile Enhancements
These tiles are now individual widgets and include an Advanced Entity Filter; this allows users to take advantage of unique and granular filtering controls, without the need to understand SWQL
Enterprise Top 10 and Groups
Enterprise Top 10 page provides quick insight into critical status, problem areas, and hotspots
Enterprise Groups view lets users pinpoint group status, alerts, and events from all configured groups across their deployments
New PerfStack™ Widgets in EOC
PerfStack dashboard gives EOC users the ability to troubleshoot and correlate metrics across the entire distributed environment; saved projects to be displayed alongside other resources on any dashboard
Mention heartbeat between orion servers, and APEs; polling engine data goes directly to SQL database
Your main Orion server and your Orion database server should be hosted at the same location, either both servers are on-premise or both are in the cloud. Hosting the main Orion server and database servers separately is not recommended due to connectivity concerns. Regardless of deployment location, it is important the main Orion server and Orion database are hosted on different servers.
Cloud (main Orion server and database in the cloud)
SolarWinds recommends this deployment when your monitored environment resides mostly in the cloud, and you have a good understanding of how much computer capacity you require to monitor your environment.
Hybrid (Additional Polling Engines in the cloud; main Orion server and database on-premise)
Use this deployment type when the majority of your monitored networks are on-premise or if your hybrid environment is geographically diverse and use different availability zones.
You can also deploy agents to your nodes in the cloud to reduce the amount of data transferred within the Virtual Machine instance - and from the Virtual Machine instance - to your main Orion server.
You will need to create a virtual private network (VPN) tunnel between the Additional Polling Engine (APE) in the Azure VM instance and your main Orion and Orion database servers.
Hybrid (Main server and database in the cloud; APE on-premise)
This deployment is recommended when your monitored environment includes a significant number of on-premise devices, or if you are migrating your infrastructure to the cloud.
Requirements (see guide)
Azure instances required for additional databases
Some Orion Platform products, such as NTA or Log Analyzer, use additional databases. For more details, see Databases used by SolarWinds modules.
Launch the Orion Web Console using either of the following methods:
Start Orion Web Console in your SolarWinds Orion program folder.
Launch a browser and enter http://ip_address or http://hostname, where ip_address is the IP address of your Orion server, or where hostnameis the domain name of your Orion server.
Enter the user name and password, and click Login.See Configure automatic login for details about login options.
12.4.18 – Orion Platform 2018.4
Centralized upgrades
Automatically upgrade additional polling engines, additional web servers, and High Availability servers directly from the Orion Web Console; upgrades run in parallel, which can dramatically reduce the time required to upgrade large deployments