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
Problem description
When using the plugin for SAP Cloud ALM, resolutions below 5minutes return an error like this:
"code:"BAD_REQUEST"
message:"Unknown resolution : 15S"
This happens when using a configuration query with the "Automatic Resolution" switch turned on and selecting short timeperiod like "Last 6 hours".
Root Cause
This is happening because SAP Cloud ALM data providers do not support resolutions higher than 5 minutes (1Min, 10s and so on).
When using the Automatic Resolution switch, the granularity is automatically calculated based on the selected time period (e.g. using L48H the granularity is 5min while for L6H the resolution is 15s), hence the error for short timeframes.
Proposed Solution
Disable granularities higher than 5minutes for SAP Cloud ALM.
Unsupported resolutions should be also managed by the backend data providers which should automatically select a default value in case of errors.
The text was updated successfully, but these errors were encountered:
Problem description
When using the plugin for SAP Cloud ALM, resolutions below 5minutes return an error like this:
"code:"BAD_REQUEST"
message:"Unknown resolution : 15S"
This happens when using a configuration query with the "Automatic Resolution" switch turned on and selecting short timeperiod like "Last 6 hours".
Root Cause
This is happening because SAP Cloud ALM data providers do not support resolutions higher than 5 minutes (1Min, 10s and so on).
When using the Automatic Resolution switch, the granularity is automatically calculated based on the selected time period (e.g. using L48H the granularity is 5min while for L6H the resolution is 15s), hence the error for short timeframes.
Proposed Solution
Disable granularities higher than 5minutes for SAP Cloud ALM.
Unsupported resolutions should be also managed by the backend data providers which should automatically select a default value in case of errors.
The text was updated successfully, but these errors were encountered: