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 have often see developer telling us the problems going on with WPA and then the first way to debug the issue is by going through WPA kubernetes logs for the queue to find what is going on. We should logs events for all the important thing that goes on with the WPA object.
Reasons:
Easy to debug.
Developer who does have access to wpa logs but has access to their WPA object can troubleshoot problems on their own.
Examples
Say if the queue specified does not exist, logs error, but does not log events.
Cases where scale up is happening slow, developer should be able to see their WPA queue activity history to measure the scaling times. lastScaleupTime, idleSince
The text was updated successfully, but these errors were encountered:
We have often see developer telling us the problems going on with WPA and then the first way to debug the issue is by going through WPA kubernetes logs for the queue to find what is going on. We should logs events for all the important thing that goes on with the WPA object.
Reasons:
Examples
lastScaleupTime
,idleSince
The text was updated successfully, but these errors were encountered: