Maximo

 View Only

✅ Maximo Application Suite (MAS) Performance Check List

By Ramakrishnudu Kayala posted 6 days ago

  

🖥️ Node & Pod Health:
-------------------------
🔄 Check OpenShift/Kubernetes node status (e.g., any NOT Ready worker nodes)
📊 Identify any Maximo pod or node CPU/memory usage approaching limits
🔁 Detect any Maximo pods restarting frequently (maximo-app, maximo-ui, crontask, etc.)
📝 Check if any JVM Heapdump has been generated in Maximo pods
🛑 Look for JVM Hung Threads in logs (SystemOut.log, SystemErr.log)
🔍 Review Garbage Collection (GC) logs for excessive GC pauses or out-of-memory (OOM) errors

⚙️ System Resource & Performance:
---------------------------------------
📈 Monitor any node or pod with high system load or I/O wait > 20%
🏋️‍♂️ Check if any node has memory, disk, or PID pressure
⏳ Monitor Maximo UI/API response time (e.g., over 2 sec on critical transactions)
🔍 Identify any long-running (over 2 sec) or high CPU cost SQL queries (autonomicmanager, longrunningquery table)
🌐 Look for network bottlenecks (e.g., OpenShift Route, Ingress, Load Balancer delays)

🚀 Maximo Application Server Performance (WebSphere Liberty):
-----------------------------------------------------------------------
🖥️ Is Maximo Application Server Busy?
⚖️ Check CPU & memory request/limit values in maximo-app pods
🛠️ Review WebSphere Liberty logs for thread pool exhaustion (SystemOut.log, messages.log)
🔄 Check active HTTP/HTTPS connections
🏗️ Investigate stuck transactions or thread dumps if application is slow
➕ Consider scaling up Maximo replicas if high load is observed

🗄️ Maximo Database Server Performance:
---------------------------------------------
📊 Check CPU, memory, and disk usage vs. limits in the DB server
🔧 Identify any background utilities running (e.g., backup, reindexing, stored procedures)
🔒 Look for database locks that may impact transactions (sysibm.syslockwait, Maximo lockwait table)
🔥 Investigate high-cost SQL queries (longrunningquery, performance tables, DB logs)
💾 Check disk performance, tablespace usage, and index fragmentation

⏲️ Cron Task & Scheduled Jobs Performance:
-------------------------------------------------
⏳ Check for stuck or long-running cron tasks (CRONTASKINSTANCE, CRONTASKHISTORY)
🔄 Identify cron tasks that failed to complete or restarted frequently
⚙️ Review MBO count and query performance for cron tasks that process large datasets

📄 Maximo Logs & Error Monitoring:
---------------------------------------
🛑 Check SystemOut.log, SystemErr.log for errors, warnings, or performance issues
📌 Review database connection pool usage in messages.log
🔍 Look for WebSphere Liberty garbage collection (GC) issues (gc.log)
🚨 Investigate any Maximo integration (MIF) or REST API failures

0 comments
2 views

Permalink