During this interactive webinar, our presenter discussed how automation can improve support levels and maximize your resources. He also reviewed how SolarWinds® IT operations management (ITOM) solutions can help with alerts, configuration management, capacity planning, and cyberthreat response and prevention.
Attendees learned about:
Alerts—leverage intelligent alerting to notify the appropriate staff members and use thresholds to trigger alerts
Configuration management—for networks, back up and standardize configs and automate repetitive tasks during upgrades; for systems, establish baselines and get notified of changes
Capacity planning—monitor system capacity and get notified when trends indicate shortages will occur; get virtualization recommendations based on data from your environment
Threat response—establish conditions for active responses to automatically make changes to deter active cyberthreats
26. 26
@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
[I thought about doubling the graphic to show how supporting local and remote issues/tech is twice as hard]
Use the out-of-the-box alerts as templates
SolarWinds recommends using the alerts that are included when you install the product as templates for your new alerts.
Find an alert similar to the one you want to create and then click Duplicate & Edit in the menu bar. Fields are pre-populated so you can skip to specific parts of the Alert Wizard where there’s data you want to change.
Enable out-of-the-box alerts
If there are out-of-the-box alerts that match your monitoring needs, enable them in your environment. You can customize the alert actions for those alerts. If you want to modify the conditions, use the alert as a template.
Restrict who receives alerts
During your initial evaluation and testing, send alerts to a few people instead of to a large distribution list. This can prevent overloading your email server while you fine tune your alerts.
Plan which devices to monitor
To reduce the number of alerts sent out, consider which devices are most important. For example, you may want to receive alerts only for mission-critical interfaces instead of every interface on a device.
Establish dependencies
Establish dependencies to prevent you from receiving duplicate alerts that stem from a single network event. For example, you may want to be emailed if servers in your server farm go down, but if the router goes down and the servers can no longer be polled, you do not want to receive notifications for your servers.
See this success center page for webpages on each of these topics- https://support.solarwinds.com/SuccessCenter/s/article/Alerting-resources-for-Orion-Platform-products
Navigate to the Alert Manager – How to find the Alert Manager.
Creating alerts – How to create an alert.
Alert preconfiguration tasks – Some alert actions require additional setup.
Set Alert properties – Basic properties of alerts.
Define the conditions that must exist to trigger an alert – Introduction to alert trigger conditions.
Define the conditions that must exist to reset an alert – Introduction to alert reset conditions.
Define what happens when an alert is triggered – Introduction to alert actions.
Define what happens when the alert is reset – Introduction to alert reset actions
If you go to this page, there are subpages for each bullet – https://documentation.solarwinds.com/en/success_center/orionplatform/Content/Onboarding/Core-OB_Parent_Reduce_Alert_Noise.htm
Complex trigger conditions
Alerts with multi-element triggers
Use duration in the alert trigger
The “Do Not Alert” alert
Send alerts to specific contacts
Alerts with device-specific thresholds
Single alert when multiple devices go down
Event correlation alerts (Y after X)
[for talking points and demo track, see links for SW use cases or success center documentation]
[for talking points and demo track, see links for SW use cases]
[skipping other resources because links to use cases and products and in previous slides]