JON Monitoring

JON - Jboss Operation Network
Overview

• JON stands for Jboss Operations Network
• JON is centralized system which has inventory of resources across multiple platforms
• JON - is a Server - Agent Model with a backend Database to store Metrics

Components:

• JON Server : myTestJonServer1
• JON Database: myTestDBServer1
• JON Agents: Servers where apps has to be monitored

JON Server : myTestJonServer1
    Unix id: jonsrvr
    Start/Stop Server:
                    /opt/jon/jon-server-2.4.0.GA/bin/rhq-server.sh start
                   /opt/jon/jon-server-2.4.0.GA/bin/rhq-server.sh stop
     Logs:
                    /opt/jon/jon-server-2.4.0.GA/logs
    JON Admin Console

     http://myTestJonServer1:7080

  JON Agents
      We need one agent per Server
      Unix id: jonagent
    Start/Stop Agent
                    /opt/jonagent/rhq-agent/bin/rhq-agent-wrapper.sh start
                      /opt/jonagent/rhq-agent/bin/rhq-agent-wrapper.sh stop
     Logs:
                    /opt/jonagent/rhq-agent/logs/agent.log

 JON Instance Configuration

1. Once the agent is discovered, next step is complete JBOSS instance configuration. One time setup.

1. Open the JON server console.

• http://myTestJonServer1:7080

• 

• Navigate to  Dashboard  --> Server Total -->JBossAS Server    

    

• For any JBoss instance,  click on INVENTORY tab and “Connection”

• 

• Now edit the

Naming Provider URL

Principal

Password

     (For JNP Url look at   eg: “ /appshr/jb5-logs/pafClusterC/data> less jnp-service.url )

• Prinicpal and password should be same values used to authenticate JMX-console

(Before using principal and password, test it using JMX-CONSOLE for same user

 http://ip:port/jmx-console

• Once its configured correctly, it should display values in “Monitoring tab”

   ( Some times, you have wait 10mins before “warning” symbol goes away on JBOSS server)