summaryrefslogtreecommitdiffstats
path: root/roles/openshift_master_cluster
diff options
context:
space:
mode:
authorOpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com>2017-09-27 05:36:09 -0700
committerGitHub <noreply@github.com>2017-09-27 05:36:09 -0700
commit5afef2e7b29813760aa7b4f42013aebe16d08ec8 (patch)
treef43c5e71604493724d7a049000faec40c230b4e7 /roles/openshift_master_cluster
parent1ab97938845c00119c3e88d58b33ae6cbd8f97fd (diff)
parent4e30a4243a6c9692c24a574ecfd83c2bcd1e2785 (diff)
downloadopenshift-5afef2e7b29813760aa7b4f42013aebe16d08ec8.tar.gz
openshift-5afef2e7b29813760aa7b4f42013aebe16d08ec8.tar.bz2
openshift-5afef2e7b29813760aa7b4f42013aebe16d08ec8.tar.xz
openshift-5afef2e7b29813760aa7b4f42013aebe16d08ec8.zip
Merge pull request #4973 from wozniakjan/logging_eventrouter
Automatic merge from submit-queue logging: introducing event router Initial concept integrating kubernetes events to EFK stack using [eventrouter](https://github.com/heptio/eventrouter) - **eventrouter** is deployed to logging project, has a service account and its own role to read events - **eventrouter** watches kubernetes events, marshalls them to JSON and outputs to its STDOUT - **fluentd** picks them up and inserts to elastic search logging project index Kubernetes events could be easily stored into different index. Among other ways, it could be achieved either by a fluentd filter plugin or custom eventrouter sink. Pending actions: - [x] - get our downstream and upstream images for eventrouter, don't use heptio's cc: @josefkarasek , @jcantrill , @richm
Diffstat (limited to 'roles/openshift_master_cluster')
0 files changed, 0 insertions, 0 deletions