Digital Nomad

WebLogic에서는 JMX 연결을 하려면 RMI/IIOP를 사용한다. (아래 블로그 참고)

http://blog.naver.com/javalove93/130031031944

그런데 Zabbix에서는 JMX 연결 시(Java Agent를 통해) 프로토콜을 지정할 수 없어 WebLogic JMX에 직접 접속할 수 없다.

Zabbix에 Zapcat이라는 다른 방식이 있는 것 같은데 이것은 Application 내에 JAR를 포함시켜야 하는 것으로 보여 역시 일반적으로 사용하기에는

쉽지 않아 보인다 (http://www.kjkoster.org/zapcat/How_To.html)

https://support.zabbix.com/browse/ZBXNEXT-1935

Java gateway server only support RMI protocol, but WebLogic doesn't support RMI. It's necessary to use IIOP protocol.
http://docs.oracle.com/cd/E13222_01/wls/docs90/jmx/accessWLS.html

Also, there is a difference in environment parameter of JMXConnectorFactory.connect method for WebLogic JMX

Current java gateway code:

env = new HashMap<String, String[]>();
env.put(JMXConnector.CREDENTIALS, new String[]

);

Sample code from WebLogic documentation:

Hashtable h = new Hashtable();
h.put(Context.SECURITY_PRINCIPAL, username);
h.put(Context.SECURITY_CREDENTIALS, password);
h.put(JMXConnectorFactory.PROTOCOL_PROVIDER_PACKAGES, "weblogic.management.remote");

결론적으로는 애매해 보이는데 Zabbix의 Java Gateway를 조금 수정해서 IIOP를 지원하게 하거나

WLS JMX 를 일반적인 RMI기반 JMX로 Wrapping할 수 있는 프로그램을 만들면 어떨까 하는 생각이다.

원문: https://www.zabbix.com/wiki/howto/monitor/db/orabbix_monitor_oracle_with_zabbix

아래는 오라클 DB 에서 모니터링 가능한 내용의 예이다.

• DB Version (i.e. Validity of package)
• Archiving (Archive log production with trend analysis)
• Event Waits (Files I/O, single block read, multi-block read, direct path read, SQLNet Messages, Control file I/O, Log Write)
• Hit Ratio (Hit Ratio on Triggers, Tables/Procedures, SQL Area, Body)
• Logical I/O (Server performance on Logical I/O of: Current Read, Consistent Read, Block Change)
• Physical I/O (Redo Writes, Datafile Writes, Datafile Reads)
• PGA
• SGA (In particular; Fixed Buffer, Java Pool, Large Pool, Log Buffer, Shared Poolm Buffer Cache)
• Shared Pool (Pool Dictionary Cache, Pool Free Memory, Library Chache, SQL Area, MISC.)
• Pin Hit Ratio (Oracle library cache pin are caused by contention with the library cache, the area used to store SQL executables for re-use)
• Sessions / Processes
• Sessions (Active Sessions, Inactive Sessions, System Sessions)
• DBSize/DBFileSize (DBSize size of database really used space and of Filesize)

그래프로 생성 가능한 항목들이다.

• Archivelog
• DBSize and DBFileSize
• Events Wait
• HIT Ratio
• Logical I/O
• PGA
• Pin HIT Ratio
• Session
• SGA
• Shared Pool
• Sessions Processes