MBeansReference6061 < Deployment

<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%">
---+!! JMX Application MBeans Reference Guide for 6.0.6.1<img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/uc.png" alt="uc.png" width="50" height="50" align="right"> 
%DKGRAY% Authors: Main.TimFeeney <br>
Build basis: 6.0.6.1
%ENDCOLOR%</div></sticky>

<!-- Page contents top of page on right hand side in box -->
<sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;">
%TOC{title="Page contents"}%
</div></sticky>

<sticky><div style="margin:15px;"></sticky>

Revised approach to documenting MBeans
   * A reference guide for a release should be wholly complete, that is, it should include new MBeans for the release but also all other released MBeans
   * Organize the MBeans for each release by 
      * Java/JVM - since we don't 'own' these, it could be that these standalone outside the ELM MBean reference guides for each release
      * Foundation/Common
      * DOORS Next
      * EWM
      * LQE - this is an outlier too since we are just using MBeans available in Jena
      * Future add ETM, RMM and other apps as they pub MBeans
   * Within an application domain category, organize the MBeans alphabetically.  The current organization by collector task is not meaningful to end users.  Alternatively, if a reasonable functional categorization can be defined, that could be considered, e.g. cluster, performance, server health, usage, etc.
   * Each release should have release notes that indicate any changes (high level) from previous release
      * Changes to a release should NOT break client monitoring for a prior release, e.g. avoid changing object name paths
   * What to capture for each MBean:
      * Name, Object name/path
      * Advanced Property Namespace, Advanced Property Display Name, Advanced Property ID and their default values and unit of measurement (e.g. milliseconds, seconds....)
      * Description/usage/why of value
      * Default frequency and how to alter in UI and/advanced property 
      * Name of collector task, TaskID used in UI
      * Attribute names with good descriptions
      * see [[CLM606ServiceabilityComponentMBeanMapping][Serviceability Component MBean Mapping]] especially the attached table
      * need to show examples on how to find and use an MBean in the Serviceability page, RepoDebug and some monitoring tool, e.g. Splunk

---+++++!! Related topics: [[JMXMBeans][JMX MBeans for ELM application monitoring]]

<sticky></div></sticky>

This topic: Deployment > WebHome > DeploymentMonitoring > JMXMBeans > MBeansReference > MBeansReference6061

History: r4 - 2020-01-08 - 20:56:07 - TimFeeney

Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.