We are missing robot healthcheck on the 3 ports (9200,5601,5044) of the 3 elk containers
http://jenkins.onap.info/job/oom-cd-master/

currently http://jenkins.onap.info/job/oom-cd-master/2710/console
27/34 passing 20180418 - use this server to verify your change 3 hours after merge
as of today we are good with deployment - just wait for it
07:14:54 onap dev-log-elasticsearch-66cdc4f855-65ghj 1/1 Running 0 1h
07:14:54 onap dev-log-kibana-567557fb9d-mjh4k 1/1 Running 0 1h
07:14:54 onap dev-log-logstash-fcc7d68bd-qxdqj 1/1 Running 0 1h

20180412
ubuntu@ip-10-0-0-196:~$ kubectl get pods --all-namespaces | grep log
onap dev-log-elasticsearch-66cdc4f855-956s2 1/1 Running 0 8h
onap dev-log-kibana-5b6f86bcb4-v4vxb 1/1 Running 0 8h
onap dev-log-logstash-6d9fdccdb6-qjfdk 1/1 Running 0 8h

ubuntu@ip-10-0-0-196:~$ kubectl get services --all-namespaces | grep log
onap log-es NodePort 10.43.105.168 <none> 9200:30254/TCP 8h
onap log-kibana NodePort 10.43.249.244 <none> 5601:30253/TCP 8h
onap log-ls NodePort 10.43.112.170 <none> 5044:30255/TCP 8h

follow example on
https://gerrit.onap.org/r/#/c/41715/1/robot/testsuites/health-check.robot

see consul checks already existing
https://jira.onap.org/browse/OOM-428

Team,
Anyone that would like to add some robot code to query the 3 ports of the 3 log containers is welcome to pick up the following JIRA
I thought I had a - been spending so much time on the health of other components – forgot our own log component.
https://jira.onap.org/browse/OOM-914

Jasmine already added consul log healthchecks – we can key off those readiness endpoints.
https://jira.onap.org/browse/OOM-428