Before making any changes to the Solarwinds environment, such as patching, application or OS, a shutdown of the Solarwinds services is required.
Orion Service Manager can be located on the Solarwinds application server and is a better alternative to having to stop and start services manually.
To shutdown Solarwinds correctly click stop everything.
To startup Solarwinds correctly click start everything.
- Check for recurring alerts and events, determine what is causing the recurring alert/event, raise and resolve the issue with relevant service owner and alter thresholds accordingly.
- Check environmental appstack and application health overview for new critical or warning items. Raise and resolve.
- Check through nightly imported nodes, configure Appinsight and apply templates if required, speak to service owner to find out about new nodes and requirements.
- Remove nodes or unmanage nodes, no longer required, confirmed by service owner.
- Check NOC displays for updates due to new nodes being added or nodes being removed.
- Raise any particular alerting issues at the morning meeting.
- Review and apply as needed Application Patches, Hotfixes to Solarwinds Application Server.
- Review and apply as needed Updates to OS, Hardware Drivers, etc.
- Review CPU/Memory/Disk on Monitoring application server and Monitoring SQL server and any other Solarwinds application servers.
- Check Active Diagnostics Bi-Weekly.
- Run Diagnostics for support purposes – Store elsewhere than application or database server (Other network location or offline storage).
- Take Snapshots (If virtualized).
- Review Enable/Disable Automatic Baselining settings as needed.
- Review Enable/Disable Automatic Dependencies as needed.
- Alerts should be running every 1 minute – unless the environment requires more regular alerting.
- Check in-house created Alerts’ raw SQL Queries against Estimated Execution Plan Time in SQL Server Management Studio to ensure queries don’t need refactoring.
- Review “Down” or “Unknown” Nodes or Applications for polling errors or that need to be unmanaged or removed from monitoring.
- Review Custom Property Utilization Across the Board for all Nodes, Applications, Interfaces, etc. – Fill in gaps where needed.
- Verify Database Maintenance is Completing MS SQL Server running Orion Solarwinds database.
- Review C:\ProgramData\Solarwinds\Logs\Orion\swdebugMaintenance.log
- Ensure “Database Maintenance Complete” Message appears in a reasonable amount of time from when it begins at 2:15 AM every morning (by default).
- Ensure you have Database backups and you can restore from those backups.
- Index Rebuilds / Reindexing – Ensure this is happening, quarterly at a minimum.
- Review Total Database Size and/or large tables for uncharacteristic growth.
- Verifying Trap & Syslog Messages are being cleaned out (space reservations in SQL DB)
- Review Polling Engine Polling Status/Rates.
- Check Polling Completion (Polling Engine Status Report).
- Check Polling Settings (Consider Alert Time Frames vs. Polling Intervals). Reminder – Retention Syslog, Trap, Discovery, Downtime – Will increase DB Size.
- Review Logging Levels – Run Logadjuster.exe to see all logging settings.
- Ensure that Logging Levels are at the Defaults or specified standard settings.
- Review Logs with Quick Rotations/Timestamp Successions.
- Review Diagnostic Logs for Errors – Check against Success Center for common issues; escalate to Support if KB is unable to solve.
- Ensure Permissions are set appropriately (Run Orion Permission Checker).
For some great Solarwinds training videos click below.