Monitor Apache Ignite

When TIBCO MDM starts, Apache Ignite is intialized. You can monitor it on application server console. It also shows the current snapshot of cache topology. 

[14:21:46]    __________  ________________
[14:21:46]   /  _/ ___/ |/ /  _/_  __/ __/
[14:21:46]  _/ // (7 7    // /  / / / _/
[14:21:46] /___/\___/_/|_/___/ /_/ /___/
[14:21:46]
[14:21:46] ver. 1.9.0#20170302-sha1:a8169d0a
[14:21:46] 2017 Copyright(C) Apache Software Foundation
[14:21:46]
[14:21:46] Ignite documentation: http://ignite.apache.org
[14:21:46]
[14:21:46] Quiet mode.
[14:21:46]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or "-v" to ignite.{sh|bat}
[14:21:46]
[14:21:46] OS: Windows Server 2008 R2 6.1 amd64
[14:21:46] VM information: Java(TM) SE Runtime Environment 1.8.0_112-b15 Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.112-b15
[14:21:46] Configured plugins:
[14:21:46]   ^-- None
[14:21:46]
[14:21:46] Message queue limit is set to 0 which may lead to potential OOMEs when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to message queues growth on sender and receiver sides.
[14:21:46] Security status [authentication=off, tls/ssl=off]
[14:22:09] Performance suggestions for grid 'MDMNODE' (fix if possible)
[14:22:09] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
[14:22:09]   ^-- Enable G1 Garbage Collector (add '-XX:+UseG1GC' to JVM options)
[14:22:09]   ^-- Set max direct memory size if getting 'OOME: Direct buffer memory' (add '-XX:MaxDirectMemorySize=<size>[g|G|m|M|k|K]' to JVM options)
[14:22:09]   ^-- Disable processing of calls to System.gc() (add '-XX:+DisableExplicitGC' to JVM options)
[14:22:09] Refer to this page for more performance suggestions: https://apacheignite.readme.io/docs/jvm-and-system-tuning
[14:22:09]
[14:22:09] To start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
[14:22:09]
[14:22:09] Ignite node started OK (id=5da32f64, grid=MDMNODE)
[14:22:09] Topology snapshot [ver=1, servers=1, clients=0, CPUs=2, heap=2.0GB]
You can monitor Apache Ignite by using the following ways:
  • JMX: JMX cache MBean of TIBCO MDM can be used to monitor various cache metrics and operations. Additionally, Apache Ignite has its own JMX, the default port is 49112. By default, Apache Ignite based statistics for each cache are disabled for performance reasons.
  • Visor Commandline Interface: Apache Ignite provides a command line interface called Visor for monitoring.
  • Logging: TIBCO MDM generates a separate file for the Apache Ignite log.
  • REST API: Apache Ignite supports REST API and the same has been integrated with TIBCO MDM. It can be used to perform different operations, such as, read or write cache (from or to), execute tasks, get various metrics, and so on.