PH12560: SUPPORT CUSTOMIZATION OF USAGE METERING METRICS

9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as new function.

Error description

• When the usage metering feature of WebSphere Application
  Server is enabled to send metrics to the IBM Cloud Private
  metering service, there are 9 metrics collected and sent, with
  no way to disable the collection of any of the metrics. A
  mechanism should be provided to disable the collection of some
  of the usage metering metrics.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server usage metering                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: Provide customizable metrics for        *
  *                      usage metering                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When the usage metering feature of WebSphere Application
  Server is enabled to send metrics to the IBM Cloud Private
  metering service, there are 9 metrics collected and sent, with
  no way to disable the collection of any of the metrics. A
  mechanism should be provided to disable the collection of some
  of the usage metering metrics.
  

Problem conclusion

• In prior releases of usage metering, all of the defined
  metrics are always sent to the metering service. Now you can
  limit which of the optional metrics to report. The virtual
  processor cores metric is not optional and is always reported.
  
  For WebSphere Application Server Liberty, the optionalMetrics
  attribute of the <usageMetering> feature can be specified in
  the server.xml file to limit which metrics are reported to the
  metering service. For example:
  
   <usageMetering url="https://x.x.x.x:8443/meteringapi"
    apiKey="xxxxxxxxxxxxxxxxxxxx"
    sslRef="usageMeteringSSL"
    optionalMetrics="CPU_TIME,TOTAL_PHYSICAL_MEMORY &#243;&#212;&#233;&#188; &#244;/>
  
  For WebSphere Application Server traditional, the
  optionalMetrics property can be specified in the
  was-usage-metering.properties file to limit which metrics are
  reported to the metering service. For Example:
  
   url=https://x.x.x.x:8443/meteringapi
   apiKey=xxxxxxxxxxxxxxxxxxxx
   trustStore=metering.jks
   optionalMetrics=CPU_TIME,TOTAL_PHYSICAL_MEMORY
  
  The possible values for the new attribute or property are:
  
  ALL (default)
  NONE
  CPU_TIME
  JAVA_INIT_MEMORY
  JAVA_USED_MEMORY
  JAVA_COMMITTED_MEMORY
  JAVA_MAX_MEMORY
  JAVA_MEMORY_AFTER_GC
  SERVLET_REQUESTS
  TOTAL_PHYSICAL_MEMORY
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 9.0.5.0 and 8.5.5.16 for WebSphere Application Server
  and 19.0.0.4 for WebSphere Application Server Liberty..  Please
  refer to the Recommended Updates page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R850 PSY

     UP

• R900 PSY

     UP