-
Epic
-
Resolution: Done
-
Medium
-
None
-
Align CLAMP and LOG ELK stacks using common charts
-
Done
Both components implement a full ELK stack
http://cd4.onap.info:30290/
http://cd0.onap.info:30253/
We can align at least at the infrastructure level by using a common chart (as we do for dgbuilder, mysql, postgres) while still differentiating on our use cases.
onap onap-clamp-dash-es-7bbf5f6db4-rfbcm 1/1 Running 0 10m onap onap-clamp-dash-kibana-5bb7fbd596-fhx4r 1/1 Running 0 10m onap onap-clamp-dash-logstash-775c4b7bcc-2dz5l 1/1 Running 0 10m onap onap-clampdb-9cfb679f6-blh5d 1/1 Running 1 10m onap onap-log-elasticsearch-7554b888f6-f8dmm 1/1 Running 0 10m onap onap-log-kibana-7f77d468c4-vz5xz 1/1 Running 0 10m onap onap-log-logstash-jd968 1/1 Running 0 10m onap onap-log-logstash-k7tx2 1/1 Running 0 10m onap onap-log-logstash-lrsk4 1/1 Running 0 10m onap onap-log-logstash-v4tf7 1/1 Running 0 10m onap onap-log-logstash-v5qpk 1/1 Running 0 10m
- blocks
-
CLAMP-175 Align CLAMP and LOG ELK stacks using common charts
- Closed
-
CLAMP-199 filebeat data volumeMount typo datag should be data - filebeat will add a second data dir
- Closed
- is blocked by
-
OOM-1120 values.yaml resource limits for cpu/ram have no effect - workaround is use JVM threadpool setting
- Closed
- relates to
-
LOG-415 Align CLAMP and LOG and POMBA ELK stacks using common charts
- Closed
-
LOG-902 CLAMP logs missing/mis-configured or not generated
- Closed
-
LOG-936 Common ELK Helm Charts
- Closed