Uploaded image for project: 'Application Server 3 4 5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-5246 Open console support
  3. JBAS-5529

Add support for JBAS, JBossWeb and JBossWeb connector components

    XMLWordPrintable

Details

    • Sub-task
    • Resolution: Done
    • Major
    • JBossAS-5.1.0.Beta1
    • None
    • None
    • None

    Description

      We've got support for monitoring and configuring datasource and jms destinations, we should extend this support so that we can discover and monitor (initially) other resource types e.g. JBoss AS server instance itself, JBossWeb container (monitoring things like Total Number of Requests Served) and JBossWeb connectors (collecting stats like Bytes Received/Bytes Sent).

      In the future this could be extended to other services within the appserver (e.g. EJB container) and also add support for configuring these, however at the moment the above would be a good start.

      Here is an initial list:

      JBAS Metrics (in addition to availablity)
      <metric property="partitionName" dataType="trait" displayType="summary"
      description="the name of the cluster partition this app server instance belongs to"/>

      <metric displayName="Version Name" property="jboss.system:type=Server:VersionName"
      dataType="trait" displayType="summary"
      description="the code name for the this app server instance's major version (AS 3.2 = WonderLand, AS 4.0 = Zion, AS 4.2 = Trinity, EAP 4.x = EAP, SOA 4.x = SOA)"/>

      <metric displayName="Build Date" property="jboss.system:type=Server:BuildDate"
      dataType="trait" displayType="summary"
      description="the date this app server was built"/>

      <metric displayName="Start Date" property="jboss.system:type=Server:StartDate"
      dataType="trait" displayType="summary"
      description="the date and time this app server instance was started"/>

      <metric property="jboss.system:type=ServerInfo:ActiveThreadCount" displayName="Active Thread Count"
      defaultInterval="300000" displayType="summary" category="throughput"/>

      <metric property="jboss.system:type=ServerInfo:ActiveThreadGroupCount" displayName="Active Thread Group Count"
      defaultInterval="300000" defaultOn="true" category="throughput"/>

      <metric property="jboss.system:type=ServerInfo:FreeMemory" displayName="JVM Free Memory" displayType="summary"
      defaultInterval="300000" defaultOn="true" category="utilization" units="bytes"/>

      <metric property="jboss.system:type=ServerInfo:MaxMemory" displayName="JVM Max Memory"
      defaultInterval="1800000" defaultOn="true" category="utilization" units="bytes"/>

      <metric property="jboss.system:type=ServerInfo:TotalMemory" displayName="JVM Total Memory" displayType="summary"
      defaultInterval="300000" defaultOn="true" category="utilization" units="bytes"/>

      <metric property="jboss:service=TransactionManager:TransactionCount" displayName="Transactions Active"
      defaultInterval="300000" defaultOn="true" category="utilization"/>

      <metric property="jboss:service=TransactionManager:CommitCount" displayName="Transactions Committed" displayType="summary" measurementType="trendsup"
      defaultInterval="600000" defaultOn="true" category="utilization"/>

      <metric property="jboss:service=TransactionManager:RollbackCount" displayName="Transactions Rolledback" measurementType="trendsup"
      defaultInterval="600000" defaultOn="true" category="utilization"/>

      JBossWeb Server
      Just need availability

      JBossWeb connectors metrics (in addition to availability)
      <!-- jboss.web:name=http-0.0.0.0-8080,type=GlobalRequestProcessor:maxTime -->
      <metric property="jboss.web:name=%schema%%dash%%address%-%port%,type=GlobalRequestProcessor:maxTime"
      displayName="Maximum Request Time"
      description="Maximum time it took to process a request"
      units="milliseconds"
      defaultOn="true" category="performance"/>

      <!-- jboss.web:name=http-0.0.0.0-8080,type=GlobalRequestProcessor:requestCount -->
      <metric property="jboss.web:name=%schema%%dash%%address%-%port%,type=GlobalRequestProcessor:requestCount"
      displayName="Request count" description="Total number of requests processed since last restart."
      defaultOn="false" category="utilization" measurementType="trendsup"/>

      <!-- jboss.web:name=http-0.0.0.0-8080,type=GlobalRequestProcessor:errorCount -->
      <metric property="jboss.web:name=%schema%%dash%%address%-%port%,type=GlobalRequestProcessor:errorCount"
      displayName="Error count" description="Number of errors while processing since last restart."
      defaultOn="true" category="utilization" measurementType="trendsup"/>

      <!-- jboss.web:name=http-0.0.0.0-8080,type=ThreadPool:currentThreadsBusy -->
      <metric property="jboss.web:name=%schema%%dash%%address%-%port%,type=ThreadPool:currentThreadsBusy"
      displayName="Threads Active"
      defaultOn="true" category="utilization" displayType="summary"/>

      <!-- jboss.web:name=http-0.0.0.0-8080,type=ThreadPool:currentThreadCount -->
      <metric property="jboss.web:name=%schema%%dash%%address%-%port%,type=ThreadPool:currentThreadCount"
      displayName="Threads Allocated"
      defaultOn="true" category="utilization" displayType="summary"/>

      JBossWeb vhost metrics (in addition to availability)
      <metric property="jboss.web:type=Host,host=%name%:aliases"
      displayName="Aliases"
      defaultOn="true" dataType="trait" />

      Attachments

        Issue Links

          blocks

          Sub-task - The sub-task of the issue JBAS-6595 org.jboss.test.profileservice.test.ServerManagedObjectsTestCase

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. JBAS-6470 Open console support blockers

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is blocked by

          Sub-task - The sub-task of the issue JBAS-6167 Restore the ServerInfo bean/mbean

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBAS-5689 Not seeing bootstrap ManagedDeployment/ManagedComponents

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              starksm64 Scott Stark (Inactive)
              ccrouch_jira Charles Crouch (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: