it would help debugging if we could also export the details in the analysis CRD error message, the current error message propagation does not help users understand their errors.
We should also specify how the metric providers queries the API , already using the 'metricsSelector=' a proper blog/ DT tutorial is needed for this probably.
DoD
[ ] add details in error struct and return them in the provider logs + metric status
[ ] avoid user error by trimming metricsSelector= prefix if the query starts with it
This issue has been automatically marked as stale because it has not had recent activity. It will be
closed if no further activity occurs. Thank you for your contributions.
this ticket overlaps a bit with #2790
typical API errors look like:
it would help debugging if we could also export the details in the analysis CRD error message, the current error message propagation does not help users understand their errors.
We should also specify how the metric providers queries the API , already using the 'metricsSelector=' a proper blog/ DT tutorial is needed for this probably.
DoD