Current template collects a number of AIX-specific CPU and memory metrics, but it does not provide alerts for several conditions that may be important when monitoring AIX LPAR environment.

1. 
   No triggers for LPAR CPU capacity

The following metrics are collected:
 

system.stat[cpu,ec] 
system.stat[cpu,pc] 
system.stat[cpu,app] 
system.stat[ent]

However, there are no alerts based on these metrics.
Suggested improvements: *
Trigger when entitlement consumption remains above 100%, indicating an uncapped LPAR borrowing CPU capacity from the shared pool.

• 
  Trigger when the available shared-pool capacity approaches zero.

1. 
   Memory monitoring does not fully reflect the AIX memory model

Current trigger is based on:
vm.memory.size[available] < 20M
 
AIX uses available memory for file caching, so a fixed available-memory threshold may not provide a sufficient indication of actual memory pressure.
Suggested improvement: *
Add computational memory utilization based on active virtual memory compared with total real memory.

Template already collects:

system.stat[memory,avm]

but does not calculate or alert on computational memory utilization. #
Paging space utilization is not monitored

Template collects page-in and page-out activity but does not monitor the actual paging space utilization.
Suggested improvements: *
Add paging space utilization monitoring.

• 
  Add a high paging space utilization trigger.

Paging space exhaustion may cause AIX to terminate processes.