Add traces/metrics relate to routes

[skabashnyuk]

Description

We would like to observe how routes creation is happening.
Related issue openshiftio/openshift.io#4730

[garagatyi]

Can you clarify what do you mean by metrics for routes?
BTW we already have traces for routes creation here https://github.com/eclipse/che/blob/master/infrastructures/openshift/src/main/java/org/eclipse/che/workspace/infrastructure/openshift/OpenShiftInternalRuntime.java#L176
Did you mean traces for routes availability?

[sleshchenko]

@garagatyi Do you happen to know how routes availability can be checked? I mean maybe status is not set for an unavailable route?

[skabashnyuk]

I need some time to clarify this task. Basically, I want to see some routes related metric that will mean something for the user. Not only API call. May be we need something that will ensure that route really created.

[garagatyi]

@sleshchenko we could add traces programatically when we ping servers. We could also try to use https://docs.openshift.com/container-platform/3.5/rest_api/openshift_v1.html#list-or-watch-objects-of-kind-route, but I'm not sure it shows flaky routes

[fche]

@skabashnyuk It sounds a little like what you need is some metric from the openshift infrastructure, in the form of latencies for a complete operation (route CRD creation through to actual operation).

[skabashnyuk]

closing in prefer of #12740

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

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

Moderators: Add lifecycle/frozen label to avoid stale mode.