Submit a ticketCall us

Cloud Workloads: Meet Your New Hybrid IT Reality
Have you found yourself in that evolving, hybrid IT grey area and wondering if cloud workloads are now part of your purview? And if so, will monitoring cloud workloads require a new set of dedicated cloud monitoring tools? Your answers: yes, they should be, and no, they don’t.

Find out how SolarWinds® Server & Application Monitor (SAM) can help you monitor your cloud workloads side by side with your on-premises workloads. Register Now.

Home > Success Center > Storage Manager (STM) > SRM Profiler Administrator Guide > SRM Profiler health status overview page > Services


Table of contents
No headers

Updated: June 16, 2017


The Services resource shows Java Heap memory consumption and Java Heap memory allocation of the services excluding the database service.

Java Heap memory does not apply to the database, it only applies to the Maintenance, Web Server, Event Receiver, Collector, and Poller services. The database uses key buffer size as allocated memory while processed memory is considered used memory. User can learn more about allocating physical memory to the SRM Profiler services by clicking the Learn how to allocate physical memory for services link. Users can also learn more about allocating memory to the database by clicking the Learn how to allocate memory to the database link.

When a threshold reaches 70%, the indicator bar changes to yellow, meaning warning. When a threshold reaches 90%, the indicator bar changes to red, meaning critical. If a service is stopped or in a stopped state, it is labeled as offline.

Last modified