IMPORTANT ANNOUNCEMENT: On May 6, 2024, Carbon Black User eXchange (UeX) and Case Management will move to a new platform!
The Community will be in read-only mode starting April 19th, 7:00 AM PDT. Check out the blog post!
You will still be able to use the case portal to create and interact with your support cases until the transition, view more information here!

Container Essentials: How to Collect Diagnostic Logs

Container Essentials: How to Collect Diagnostic Logs

Environment

  • VMWare Carbon Black Container Essentials: All Versions

Objective

How to collect diagnostics for CB Container Essential resources.

Resolution

  1. SSH into Kubernetes cluster [NOTE: SSH is not strictly required as long as you have access via kubectl]
  2. Run the following command:
    kubectl logs -n cbcontainers-dataplane -l control-plane=operator --tail=-1 > operator-logs_$(date +%b_%d_%Y_%H_%M_%S.txt)
  3. Run the following which generates logs for each component in the dataplane.
    kubectl logs -l 'app.kubernetes.io/name in (cbcontainers-hardening-enforcer, cbcontainers-hardening-state-reporter, cbcontainers-image-scanning-reporter, cbcontainers-monitor, cbcontainers-node-agent, cbcontainers-runtime-resolver)' --all-containers --prefix -n cbcontainers-dataplane
  4. Transfer the operator-logs*.txt file and attach to the support case. If the file is large, use CBVault.

Additional Notes

  • If the namespace has been renamed, the -n switch can be modified to specify the new namespace
  • If the label has been renamed, the -l switch can be modified to specify the new label

Related Content


Labels (2)
Was this article helpful? Yes No
No ratings
Article Information
Author:
Creation Date:
‎01-06-2021
Views:
741
Contributors