Yes, VNF fogging is through the parallel CLAMP ELK stack
https://wiki.onap.org/display/DW/CLAMP+Project

5 containers
http://jenkins.onap.info/job/oom-cd-master2-aws/112/console

16:57:10 onap onap-clamp-clamp-766f56bd4d-jrvn9 2/2 Running 0 51m 10.42.183.131 a-ld0.fkpj53f4vfsulhfnozmmhljcya.cx.internal.cloudapp.net <none>
16:57:10 onap onap-clamp-clamp-dash-es-6d8b4c65cc-8nc4t 1/1 Running 0 51m 10.42.83.92 a-ld0.fkpj53f4vfsulhfnozmmhljcya.cx.internal.cloudapp.net <none>
16:57:10 onap onap-clamp-clamp-dash-kibana-67978bc768-rzrdc 1/1 Running 0 51m 10.42.30.187 a-ld0.fkpj53f4vfsulhfnozmmhljcya.cx.internal.cloudapp.net <none>
16:57:10 onap onap-clamp-clamp-dash-logstash-756485d766-rwwn7 1/1 Running 0 51m 10.42.240.171 a-ld0.fkpj53f4vfsulhfnozmmhljcya.cx.internal.cloudapp.net <none>
16:57:10 onap onap-clamp-clampdb-56cbd6f996-vw46h 1/1 Running 0 51m 10.42.135.37 a-ld0.fkpj53f4vfsulhfnozmmhljcya.cx.internal.cloudapp.net <none>

We have a pending merge of the two ELK stacks into a common chart

For VES – DCAE should be able to handle this when their filebeat is added
16:57:10 onap dep-dcae-hv-ves-collector-7959976fcf-sx8zc 2/2 Running 0 3h 10.42.34.171 a-ld0.fkpj53f4vfsulhfnozmmhljcya.cx.internal.cloudapp.net <none>
16:57:10 onap dep-dcae-tca-analytics-5754b64d6b-n7ts2 2/2 Running 0 3h 10.42.54.178 a-ld0.fkpj53f4vfsulhfnozmmhljcya.cx.internal.cloudapp.net <none>
16:57:10 onap dep-dcae-ves-collector-7894fd57b6-8s6h6 2/2 Running 0 3h 10.42.153.244 a-ld0.fkpj53f4vfsulhfnozmmhljcya.cx.internal.cloudapp.net <none>

/michael

From: AGRAHARAM, SANJAY <sa2785@att.com>
Sent: Friday, February 1, 2019 2:35 PM
To: Michael O'Brien <Frank.Obrien@amdocs.com>
Subject: Strategy for VNF logging

Hi Michael,

Do we address VNF logging in the ONAP logging framework?
How can we extend the current specification to cover VNFs also? Not sure how we can leverage/integrate the Event Standardization framework- VES (Virtual Functions Event Streaming)
Let me know if you need details on VES.

Sanjay