580
39%

Ran 23 Apr 2020 10:29AM UTC

Jobs 1

Files 66

Run time 6s

Badge

Embed ▾

Committed 23 Apr 2020 10:19AM UTC coverage: 41.127%. Remained the same

Build # 580

Build Type

push

travis-ci

Committed by

slaskawi

Commit Message

Lower severity of rate based alerts

Discussed offline (& in https://issues.redhat.com/browse/INTLY-6614) 
I think it might be best to go down to just 1 critical alert where SRE need to investigate as a matter of urgency at this time i.e. the 'up' alert (KeycloakInstanceNotAvailable).

The response times alerts may become more important in time, but I don't think we know what immediate steps an SRE could take when paged, so i think lowering them to warning is reasonable.
There could be an immediate action to increase the number of instances (in the keycloak CR) while investigation continues, but i'd like to have that discussion with our SRE team first as there's resourcing concerns there. Also, they Keycloak CR gets reset back to 2 in RHMI whenever changed at the moment (David Ffrench is following up on that to allow changes)

TLDR: Just have the 'up' alert for at least 1 keycloak pod as critical.
All others as warning, but will add gained knowledge from discussions here to the SOP to help with debugging any warnings related to memory & GC.

Run Details

2693 of 6548 relevant lines covered (41.13%)

4.6 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	580.1 (CHANGE_MINIKUBE_NONE_USER=true MINIKUBE_WANTUPDATENOTIFICATION=false MINIKUBE_WANTREPORTERRORPROMPT=false MINIKUBE_HOME=$HOME KUBECONFIG=$HOME/.kube/config)	23 Apr 2020 10:29AM UTC	0	41.13	Travis Job 580.1

Source Files on build 580

Detailed source file information is not available for this build.

keycloak / keycloak-operator / 580
39%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 580

keycloak / keycloak-operator / 580 39%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 580

keycloak / keycloak-operator / 580
39%

README BADGES
x