| Table of Contents |
|---|
...
Questions on onap-discuss from the teams
https://lists.onap.org/pipermail/onap-discuss/2018-January/007415.html
Latest Filebeat/ELK implementation by Clamp for reference - https://gerrit.onap.org/r/#/c/48961/ on
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Purpose
The goals of the logging project are the following
...
| Gliffy | ||||
|---|---|---|---|---|
|
Quickstart
WIP (as of 20180121) - will notify when complete
...
| app | project | repo | version | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| aai | aai-common | 1.0.0 | |||||||||
| aai | aai-core | 1.0.0 | |||||||||
| aai | aai-service (deprecated) | 0.0.1 (not in use) | |||||||||
| aai | aai-traversal | 1.0.0 | |||||||||
| aai | ajsc-aai | 1.0.0 | |||||||||
| aai | eelf-logging | logging-service | 0.0.1 (not in use) | ||||||||
| appc | (pax.logging = wrapper on log4j, slf4j, commons-logging 1.2 and logback 1.1.1) needs this RI - provide a demo to the appc team | 0.0.1 (upgrade?) | |||||||||
| ccsdk | nbapi | ccsdk/platform/nbapi | 1.0.0 | ||||||||
| dmaap | buscontroller | dmaap/buscontroller | 0.0.1 | ||||||||
| ui | dcae_dmaap_webapp | dmaapbc | 1.0.0 | ||||||||
| ui | dmaap-bc-app-common | 1.0.0 | |||||||||
| ui | dmaap-bc-app-parent | 1.0.0 | |||||||||
| policy | common-modules/ | common | 1.0.0 | ||||||||
| policy | drools-pdp | 1.0.0 | |||||||||
| portal | ecompportal-be-common | portal | <eelf.version>1.0.0 | ||||||||
| policy | feature-eelf | drools-pdp | 1.0.0 | ||||||||
| policy | PolicyEngineSuite/ONAP-logging | common | 0.0.1 (not in use) | ||||||||
| policy | ONAP-SDK-APP | engine | 0.0.1 (not in use) | ||||||||
| sdc | ? | ||||||||||
| so | common | so | 0.0.1 (upgrade ?) | ||||||||
| vid | epsdk-app-onap | vid | 1.0.0 | ||||||||
| vid | vid-app-common | vid | 1.0.0 | ||||||||
| open-o | |||||||||||
| multicloud | python based |
|
...
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-656
DI 9: 20180417: Restart a failed ELK stack container
Periodically one of the higher containers in a dependency tree will not get restarted in time to pick up running child containers - usually this is the kibana container
Fix this or "any" container by deleting the container in question and kubernetes will bring another one up.
| Code Block | ||
|---|---|---|
| ||
root@a-onap-auto-20180412-ref:~# kubectl get services --all-namespaces | grep log
onap dev-vfc-catalog ClusterIP 10.43.210.8 <none> 8806/TCP 5d
onap log-es NodePort 10.43.77.87 <none> 9200:30254/TCP 5d
onap log-es-tcp ClusterIP 10.43.159.93 <none> 9300/TCP 5d
onap log-kibana NodePort 10.43.41.102 <none> 5601:30253/TCP 5d
onap log-ls NodePort 10.43.180.165 <none> 5044:30255/TCP 5d
onap log-ls-http ClusterIP 10.43.13.180 <none> 9600/TCP 5d
root@a-onap-auto-20180412-ref:~# kubectl get pods --all-namespaces | grep log
onap dev-log-elasticsearch-66cdc4f855-wmpkz 1/1 Running 0 5d
onap dev-log-kibana-5b6f86bcb4-drpzq 0/1 Running 1076 5d
onap dev-log-logstash-6d9fdccdb6-ngq2f 1/1 Running 0 5d
onap dev-vfc-catalog-7d89bc8b9d-vxk74 2/2 Running 0 5d
root@a-onap-auto-20180412-ref:~# kubectl delete pod dev-log-kibana-5b6f86bcb4-drpzq -n onap
pod "dev-log-kibana-5b6f86bcb4-drpzq" deleted
root@a-onap-auto-20180412-ref:~# kubectl get pods --all-namespaces | grep log
onap dev-log-elasticsearch-66cdc4f855-wmpkz 1/1 Running 0 5d
onap dev-log-kibana-5b6f86bcb4-drpzq 0/1 Terminating 1076 5d
onap dev-log-kibana-5b6f86bcb4-gpn2m 0/1 Pending 0 12s
onap dev-log-logstash-6d9fdccdb6-ngq2f 1/1 Running 0 5d
onap dev-vfc-catalog-7d89bc8b9d-vxk74 2/2 Running 0 5d
|
Implementation
Deploying the RI
...