In this lesson, you will learn how to monitor the SAP HANA Cloud database services using the SAP BTP version of the SAP HANA cockpit.
You will also learn about the different features available in the Performance Monitor app.
In addition, you can identify which tables have a high memory usage and have a high read/write load.
As an database administrator, you want to monitor the availability and resource consumption of the SAP HANA Cloud database services.
SAP HANA Cockpit - Services Card
See the following video to find the SAP HANA cockpit - services card.
The Manage Services app gives you an (1) overall status summary of your database.
The Reset Memory Statistics button (2) lets you clear the statistics history.
Peak used memory is the highest recorded value for used memory since the last time the memory statistics were reset. This value is useful for understanding the behavior of used memory over time and under peak loads. Resetting peak used memory allows you, for example, to establish the impact of a certain workload on memory usage. If you reset peak used memory and run the workload, then you can then examine the new peak used memory value.
The Go to Alerts button (3) lets you directly open the Alerts application to investigate the alerts associated to this resource.
The Kill Service button (4) stops the selected service immediately and if the related option is selected, creates a crash dump file. Normally the SAP HANA daemon will restart the killed service.
The Settings icon (5) lets you add and remove columns from the display. Not all columns are visible by default.
The Service column (1) show the service name, for example, indexserver, nameserver, xsengine, and so on
The Status column (2) show the The status of the service. The following statuses are possible:
- Running - the service is operating within normal parameters.
- Running with Issues - at least one service is not running, or there is at least one high alert.
- Starting - the service or system is starting.
- Stopping - the service or system is stopping.
- Stopped - the service is stopped.
- Not Running - to investigate why the service is not running, you can navigate to the crash dump file created when the service stopped.
The Role column (2) shows the role of the service in a failover situation. Currently not applicable in SAP HANA Cloud.
The Port column (3) show the port number that the system uses for internal communication between services
The Process ID column (4) show the operating system process id assigned to this service.
The CPU column (5) displays a mini chart visualizing the CPU usage of the service. Choosing the mini chart opens the Performance Monitor app for a more detailed breakdown of CPU usage.
The Memory column (6) provides a mini chart visualizing the memory usage of the service. The different colors represent the following:
Dark green shows the service's used memory.
Light green shows the service's peak memory.
The grey stroke represents the effective allocation limit.
The light grey background represents the physical memory.
Choosing the mini chart opens the Memory Analysis app for a more detailed breakdown of memory usage.
The SQL Port column (7) show the SQL port number assigned to this service. Not all services require an SQL port.
Selecting the mini chart in the CPU Column (1), the Performance Monitor app is opened and displays a detailed breakdown of CPU usage over time.
Clicking the Memory column (2) mini chart opens the Memory Analysis app for a more detailed breakdown of memory usage.
The applications Performance Monitor and Memory Analysis will be explained in detail in their respective SAP Learning Card.