PH38048: PROMETHEUS ENDPOINT ENHANCEMENTS FOR PERFORMANCE MONITORING INFRASTRUCTURE METRICS ON WEBSPHERE APPLICATION SERVER TRADITIONAL

APAR status

• Closed as new function.

Error description

• This is a collection of enhancements to the metrics.ear
  application released in the previous fixpack.
  
  1. In addition to the pre-existing node and server labels for
  each metric, a cell label should be added as well.
  2. The ability to omit cell/node/server labels should be provide
  via a system property.
  3. Add a timeout for the server metrics scraping, so if one of
  the servers is particularly slow in responding, and the /metrics
  response time can be large and Prometheus times out, a response
  still be send back to Prometheus, even if that means some server
  data could be omitted from the response.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Prometheus endpoint enhancements for    *
  *                      the                                     *
  *                      Performance                             *
  *                      Monitoring Infrastructure (PMI)         *
  *                      metrics.ear application                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A collection of enhancements was added to the metrics.ear
  application:
  - In addition to the pre-existing node and server labels for
  each metric, a cell label was added to the Prometheus output.
  - The ability to omit cell/node/server labels via a system
  property
  (com.ibm.ws.pmi.prometheus.includeCellNodeServerLabels=false)
  - Added a timeout for server metrics scraping, so if one of
  the servers is particularly slow in responding, the /metrics
  response time will be large and Prometheus will eventually time
  out, with no response. With this timeout, a response will
  still be send back to Prometheus, even if that means some server
  data could be omitted from the response. The server scrape
  timeout
  value can be configured via a system property
  (com.ibm.ws.pmi.prometheus.serverScrapeTimeout), where the
  default
  is 8 seconds. If the value is set to 0 or a negative value, no
  timeout value is set for the server scrapes.
  

Problem conclusion

• The code was updated to include the enhancements.
  
  The fix for this APAR is targeted for inclusion in fix pack
  8.5.5.20 and 9.0.5.9. For more information, see 'Recommended
  Updates for WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP

• R900 PSY

     UP