Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

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

Services

Table of contents
No headers

Updated: June 16, 2017

File:Success_Center/Reusable_content_-_InfoDev/SRM_Profiler/Services/0300002F_443x79.png

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

Tags

Classifications

Public