Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Common ELK Helm Charts

Description

None
100% Done
Type
Key
Summary
Priority
Story Points
Assignee
Status

Confluence content

mentioned on

Activity

Show:

Former user December 9, 2021 at 4:23 PM

This issue belongs to an unmaintained project and has not been updated in 18 months or more, so closing.

Former user May 15, 2019 at 11:43 AM

One more request here.
Would it be possible to include as well an open-source alering plugin, Elastalert, with this refactoring?
https://github.com/Yelp/elastalert

Former user January 21, 2019 at 8:01 PM

moving to log

michaelobrien [2:30 PM]
I would like to finish it but it would be lower priority as there is no visible direct benefit - the common chart is the right way to go - but I still need to align logs and add infrastructure first to so and dcae to start before refactoring - we should target el alto

Former user January 18, 2019 at 8:20 PM

Moved original description to a comment, as we make this Epic more general to apply to any work that involves creating common Helm Charts for reuse.

 

MOB:

The original scope was the entire elk stack (logstash, elasticsearch and kibana) - 5 days ago the scope was reduced to only es - I recommend we add 3 stories for each of the 3 charts instead

Align CLAMP and LOG ELK stacks using common charts. 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

Former user October 18, 2018 at 8:09 PM

see https://lf-onap.atlassian.net/browse/LOG-653
Note: that upgrading will also require an upgrade of all filebeat containers across the charts - so a lot of retesting each pod to verify logs get through - like for pairwise in https://lf-onap.atlassian.net/browse/LOG-770

some done here in https://gerrit.onap.org/r/#/c/64811/

Won't Do

Details

Assignee

Reporter

Labels

Fix versions

Priority

Epic Name

Created May 21, 2018 at 11:54 PM
Updated August 12, 2023 at 4:14 AM
Resolved December 9, 2021 at 4:23 PM

Flag notifications