...
JIRAs | Git (pending) | Gerrit (pending) | Nexus | Jenkins (pending) | Sonar |
High Level Description
There are the 3 elk containers in the log pod in kubernetes off the OOM deployment. Currently all 3 ports are exposed, logstash, elasticsearch and kibana. We use Kubernetes 1.8 with Helm 2.8 charts via the OOM project deployment. The ports are all mapped as node ports in the external 302xx namespace. We use filebeat as a side car container for all the onap components to push logs to the logstash node port.
Logstash port mapping
https://git.onap.org/oom/tree/kubernetes/log/charts/log-logstash/templates/service.yaml
https://git.onap.org/oom/tree/kubernetes/log/charts/log-logstash/templates/deployment.yaml
port numbers are here - 5044
https://git.onap.org/oom/tree/kubernetes/log/charts/log-logstash/values.yaml
for example SDC filebeat config to log-ls on port 5044
https://git.onap.org/oom/tree/kubernetes/sdc/values.yaml
the filebeat sidecar docker image for sdc-be
https://git.onap.org/oom/tree/kubernetes/sdc/charts/sdc-be/values.yaml
Logging configmap
https://git.onap.org/oom/tree/kubernetes/sdc/charts/sdc-be/templates/configmap.yaml
Logging filebeat deployment spec
https://git.onap.org/oom/tree/kubernetes/sdc/charts/sdc-be/templates/deployment.yaml
and the logback config
https://git.onap.org/oom/tree/kubernetes/sdc/charts/sdc-be/resources/config/logging/logback.xml
ELK stack in ONAP
Use Cases
...
Gliffy Diagram | ||
---|---|---|
|
Deployment with primary ELK stack only in pods:
| ||
Gliffy Diagram | ||
---|---|---|
|
Southbound APIs
Northbound APIs
https://github.com/opentracing
...