You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We would like to report and alert the resource consumption for each ZOWE Components.
Quickly we will have new customers who wants to use ZOWE component.
ZOWE users are incoming and CPU consumption will grow quickly and unexpectly.
So we need to track which API is most used and to identify eventually a loop in a component to stop it individually.
The only way to classify and report ZOWE resources comsuption is with WLM.
Unfortunatelly, the unique method to have a detailed reporting for WLM OMVS susbsystem is to use the account variable.
The value that can be catch by WLM is an export of variable _BPX_ACCT_DATA.
Do you have a method to export _BPX_ACCT_DATA variable for each ZOWE component or alternatively do you another suggestion to achieve the scope of survey and alert resource consumption ?
Regards
Gilles
The text was updated successfully, but these errors were encountered:
I am not aware if there any methods to export _BPX_ACCT_DATA as we do not set it anywhere, but I suppose this parameter can be added to Zowe components as part of startup if needed. However it should be reviewed by community leads first.
Meanwhile could you please elaborate a little bit more, i guess you are speaking about Zowe Components but you also mention APIs, is the main issue the potentially corrupted onboarded APIs? Or are there any other reasons why loops are expected?
We would like to identify which Zowe component use CPU but we also developped our own components to run some APIs which do some simple administration operations ( command zwe install component )
We would like to monitor our APIs to know which one are used and eventually have a loop. The objectif is to measure CPU consumption and to avoid a CPU loop in the system.
Hello
We would like to report and alert the resource consumption for each ZOWE Components.
Quickly we will have new customers who wants to use ZOWE component.
ZOWE users are incoming and CPU consumption will grow quickly and unexpectly.
So we need to track which API is most used and to identify eventually a loop in a component to stop it individually.
The only way to classify and report ZOWE resources comsuption is with WLM.
Unfortunatelly, the unique method to have a detailed reporting for WLM OMVS susbsystem is to use the account variable.
The value that can be catch by WLM is an export of variable _BPX_ACCT_DATA.
Do you have a method to export _BPX_ACCT_DATA variable for each ZOWE component or alternatively do you another suggestion to achieve the scope of survey and alert resource consumption ?
Regards
Gilles
The text was updated successfully, but these errors were encountered: