-
Sub-task
-
Resolution: Won't Do
-
Medium
-
None
-
LOG Sprint 8, LOG Sprint 10, Dublin-Logging
Code up a dual pod containing the microservice developed for the RI and a filebeat container to push logs to the ONAP OOM ELK stack
These yamls should ideally be pushed to the OOM repository - however the structure including the create/delete scripts could be in logging-analytics alongside the RI code and the docker image spec.
Need to discuss more which repo to put it in - as if we put it with OOM then it will need to be disabled by default. See the sniro container in the robot namespace - we are essentially the same.
See existing code for the following
root@ip-172-31-27-86:~/oom/kubernetes/robot# kubectl get pods --all-namespaces | grep 2/2 onap-aai aai-resources-1039856271-htsbt 2/2 Running 0 1h onap-aai aai-traversal-143081090-8d2xx 2/2 Running 0 1h onap-aai model-loader-service-4144225433-8k8c5 2/2 Running 0 1h onap-aai search-data-service-3842430948-l2333 2/2 Running 0 1h onap-aai sparky-be-4222608366-4hh3n 2/2 Running 0 1h onap-appc appc-1828810488-8m0w0 2/2 Running 0 1h onap-mso mso-736294529-hww5r 2/2 Running 0 1h onap-portal portalapps-1783099045-5svmk 2/2 Running 0 1h onap-sdc sdc-be-2336519847-b2jm0 2/2 Running 0 1h onap-sdc sdc-fe-2862673798-4h70n 2/2 Running 0 1h onap-sdnc sdnc-0 2/2 Running 0 1h onap-sdnc sdnc-dbhost-0 2/2 Running 0 1h onap-vid vid-server-3026751708-xv0g5 2/2 Running 0 1h
see K8S documentation for logging side container
https://kubernetes.io/docs/concepts/cluster-administration/logging/#sidecar-container-with-a-logging-agent
https://stackoverflow.com/questions/47028651/how-to-get-method-argument-value-in-joinpoint-getargs
- blocks
-
LOG-487
LOG Pipeline Integrity: Docker to Filebeat to Logstash to ElasticSearch to Kibana
-
- Closed
-
-
LOG-178
Log Specification Alignment - each onap component
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
LOG-156
Support R2 Beijing Logging initiatives in ONAP projects not currently on the ELK system (Multicloud,..)
-
- Closed
-
-
MULTICLOUD-151
Logging Enablement
-
- Closed
-
- is blocked by
-
OOM-631
Centralized config to reserve unused 0-99 range in nodePortPrefix-ed nodePorts
-
- Closed
-
-
OOM-656
Framework for reserving nodeports 302nn - need a policy
-
- Closed
-
- links to
