Understanding of Java Heap Dump Alert

[SAPSupport]

Hello team,

We got an alert Java heap dump with the value 7 but from instance level we can see only 4 .hprof files,need to understand how the alert will be caluclated for heap dumps

------------------------------------------------------------------------------------------------------------------------------------------------
Learn more about the SAP Support user and program here.

[SAPSupport · Accepted solution]

Number of Heap Dumps metric is reading under

Folder: \Q/usr/sap/${LMDB}SAP_J2EEEngineClusterInstance->SAP_J2EEEngineCluster.SAPSystemName$/${COMPLEX}INSTANCE.NAME$/j2ee/cluster\E

Filepattern: search by file pattern .*hprof

[luis_salazarzahonero · Accepted solution]

Parameters like ${LMDB}SAP_J2EEEngineClusterInstance->SAP_J2EEEngineCluster.SAPSystemName$ are being replaced in runtime, you can check the value through Transaction MAI_TOOLS / Alerting Directory Browser service. In Navigation by, you can filter by Managed Object type and enter the Managed Object Name, then select for example a technical System named FT7SYS(ABAP), then: Under Metrics tab you can select the metric and review parameters in data collection tab You can check directly Collector Parameter Variables section. More information about Data Provider File Information used in Number of heap dumps metric: This data provider checks file attributes of one or more files in a specific folder location. Metric Parameters: FOLDER (mandatory): Absolute full path to the folder containing the files to be monitored. Wild cards are not possible. FILEPATTERN (mandatory): Regular expression to filter for file names. KEY_FIG (mandatory): File attribute to be returned. Possible values are: Count: Number of files matching the given file pattern MaxSize: Size of the biggest file matching the file pattern in bytes MaxSize_KB: Size of the biggest file matching the file pattern in kilobytes MaxSize_MB: Size of the biggest file matching the file pattern in megabytes MaxSize_GB: Size of the biggest file matching the file pattern in gigabytes MinSize: Size of the smallest file matching the file pattern in bytes MinSize_KB: Size of the smallest file matching the file pattern in kilobytes MinSize_MB: Size of the smallest file matching the file pattern in megabytes MinSize_GB: Size of the smallest file matching the file pattern in gigabytes TotalSize: Sum of file sizes matching the file pattern in bytes TotalSize_KB: Sum of file sizes matching the file pattern in kilobytes TotalSize_MB: Sum of file sizes matching the file pattern in megabytes TotalSize_GB: Sum of file sizes matching the file pattern in gigabytes LastModified: File matching the file pattern that is modified latest as long (milliseconds since 01.01.1970) AgeLastModified: File matching the file pattern that is modified latest as difference of current time and the modification date in seconds. FirstModified: File matching the file pattern that is modified earliest as long (milliseconds since 01.01.1970) FolderAgeLastModified: Returning the difference of current time and the modification date in seconds for specified FOLDER. RECURSIVE (optional - default value is FALSE): Specifies if the sub folders should also be taken into account. DATEPATTERN (optional - default value is "yyyy-MM-dd"): Pattern to be applied as date format for supported variables $TODAY$ and $YESTERDAY$ in mandatory parameter FILEPATTERN. An example for the DATAPATTERN would be e.g.: yyyy-MM-dd Meaning of the different chars: y: year - allowed is either yyyy or yy => stands for e.g. 2016 or 16 M: month - allowed is only MM => stands for e.g. 10 d: day - allowed is either dd or d => stands for e.g. 07 or 7 Allowed characters for separating year, month and day are: _ (underline) - (dash) . (point) no separator All permutations are possible e.g.: yy-d-MM dd_MM_yyyy MM.dd.yyy Example for a FILEPATTERN making use of e.g. variable $TODAY$ could be: example_$TODAY$\.log.* This gets replaced during runtime e.g. by example_2016-10-07\.log.* Keep in mind that metric has an standard collection interval of 15 minutes, so if situation changes in corresponding folder (number of files changes during next data collection) it will take 15 minutes to update it.