see: LOG-66 - Getting issue details... STATUS LOG-49 - Getting issue details... STATUS
Logging Framework Deployment
The ELK stack containers are under the onap-log namespace in the OOM deployment of ONAP. They should be started by default - if not you can start them manually.
# look for log containers root@ip-172-31-82-46:~# kubectl get pods --all-namespaces -a | grep onap-log onap-log elasticsearch-2934588800-st9j3 1/1 Running 0 3h onap-log kibana-3372627750-ff8rv 1/1 Running 0 3h onap-log logstash-1708188010-703pk 1/1 Running 0 3h # start the ELK stack if required root@ip-172-31-82-46:~/oom/kubernetes/oneclick# ./createAll.bash -n onap -a log # check access ports (30254 and 30253) root@ip-172-31-82-46:~/oom/kubernetes/oneclick# kubectl get services --all-namespaces -a | grep onap-log onap-log elasticsearch 10.43.86.120 <nodes> 9200:30254/TCP onap-log kibana 10.43.165.215 <nodes> 5601:30253/TCP onap-log logstash 10.43.72.107 <none> 5044/TCP
Logging Access
Robot logs
after a
/dockerdata-nfs/onap/robot# ./demo-k8s.sh init_customer
http://host:30209/logs/demo/InitCustomer/report.html
user:robot pass:robot
Host VM logs
/dockerdata-nfs/onap/aai/aai-traversal/logs/
/dockerdata-nfs/onap/sdc/logs/ASDC/ASDC-BE/
ELK Logs
Configuring Logging Analytics
Login to the kibana dashboard on the ONAP host machine (http://dev.onap.org:30253)
$elasticsearch_username: "elastic"
$elasticsearch_password: "changeme"
