Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Orion Service Processes

I am trying to find what is using all of the CPU on my Orion server and I want to make sure its ok for me to have both the old and new version of these processes running.

Solarwinds Job Engine

SolarWinds Information Service

Solarwinds Alerting Engine.

Find more posts tagged with

Accepted answers

mharvey

I believe there are still modules, pieces that are still using the "old" versions of the some of the services, so they should still be running.

All comments

mharvey

I believe there are still modules, pieces that are still using the "old" versions of the some of the services, so they should still be running.

solaradmin

Thanks mharvey that makes sense. Figured since NPM and SAM were on the same platform they would consolidate, then I remembered the other 5 modules I have that are probably a bit behind and are using the old ones

mharvey

yeah I don't think they've moved everything to the new services quite yet.

aLTeReGo

If all your alerts have been properly migrated from the legacy Win32 Advanced Alert Manager then this service can be stopped and disabled. It should no longer be needed. It remains solely for situations where alerts failed to migrate properly (so people would continue to get alerts) as well as a fallback should someone encounter any major issue with Web Based Alerting. If you don't fall into either category, feel free to disable the service.

As for the Information Service and Job Engine, these are still relied upon for some modules and as such should continue running. If they are not needed then they should consume essentially zero CPU cycles and a very nominal memory footprint. Once all Orion modules have been fully migrated to the new versions of these services they will be automatically removed upon upgrade.