monitor boskos cleanup timing

[BenTheElder]

What would you like to be added: export and graph metrics for boskos cleanup timing

Why is this needed: so we can determine if this is increasing and we need to increase the janitor or fix boskos xref #14697

Possibly this should also move to the new monitoring stack? cc @cjwagner @detiber

/area boskos
/assign @krzyzacy
cc @fejta @mm4tt

[cjwagner]

/cc @chaodaiG
Is also working on boskos metric using the new monitoring stack.

[stevekuznetsov]

We have boskos metrics using the new stack... what do you mean? We should sync this week.

[ixdy]

Boskos is now using the Prow monitoring stack (#15344). I guess next thing is to expose cleanup timing metrics?

[ixdy]

@BenTheElder if you remember, is the intent here to track how long resources are in a given state (e.g. how long something remains as dirty before transitioning to free)? Or how long the actual cleanup itself takes? (Maybe both?)

[BenTheElder]

IIRC how long the cleanup takes, which we sometimes have issues with, but both would be useful

…

On Fri, Jan 10, 2020 at 5:37 PM Jeff Grafton ***@***.***> wrote: @BenTheElder <https://github.com/BenTheElder> if you remember, is the intent here to track how long resources are in a given state (e.g. how long something remains as dirty before transitioning to free)? Or how long the actual cleanup itself takes? (Maybe both?) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#14715?email_source=notifications&email_token=AAHADK355UA7O2CMBMUBX4TQ5EPGBA5CNFSM4I7SC5S2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIVVTRQ#issuecomment-573266374>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHADK34EIKJAFCTAGUGMJDQ5EPGBANCNFSM4I7SC5SQ> .

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[ixdy]

/remove-lifecycle stale

[ixdy]

Moving this issue to kubernetes-sigs/boskos#13.
/close

[k8s-ci-robot]

@ixdy: Closing this issue.

In response to this:

Moving this issue to kubernetes-sigs/boskos#13.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.