Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Events for the users to understand what's going on with their WPA #52

Open
alok87 opened this issue Mar 2, 2020 · 0 comments
Open

Events for the users to understand what's going on with their WPA #52

alok87 opened this issue Mar 2, 2020 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@alok87
Copy link
Contributor

alok87 commented Mar 2, 2020

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:

  1. Easy to debug.
  2. 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
@alok87 alok87 added the enhancement New feature or request label Mar 2, 2020
@alok87 alok87 added the good first issue Good for newcomers label Mar 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant