search

fabric8-services / fabric8-jenkins-proxy

Apache License 2.0
1 stars 16 forks source link

Have a way to inspect and delete individual replay request from the request table #201

Open hferentschik opened 6 years ago

hferentschik commented 6 years ago

This relates to this issue in the Idler: https://github.com/fabric8-services/fabric8-jenkins-idler/issues/163

And it also relates to this issue in the Proxy: https://github.com/fabric8-services/fabric8-jenkins-proxy/issues/107

We need more control of what's in the request table and probably we want to add some REST API endpoints to control this.

hferentschik commented 6 years ago

While on it, we should check whether the max retry of requests works.

hferentschik commented 6 years ago

Kibana query (prod):

kubernetes.pod_name:jenkins-idler AND msg:"Get /oapi/v1/namespaces/ldimaggi-osiotest2-jenkins/deploymentconfigs/jenkins"

and

kubernetes.pod_name:jenkins-proxy* AND msg:"Retrying request"

hferentschik commented 6 years ago

We already have a way to get a count on the cached requests, but running the Kibana query "kubernetes.pod_name:jenkins-proxy* AND msg:"statistic"", but we need more detailed (on request level) ways of doing this.