Gathering postmortem logs

The logs to gather for upload to a support case.

The mustgather script

Gathering the pod logs

If the mustgather script fails, the pod logs can be gathered manually:
  • VMware: SSH into your analytics VM and run apic logs:
    1. Use an SSH client to login as the apicadm user:
      ssh apicadm@<analytics VM FQDN>
    2. sudo to root:
      sudo -i
    3. Run the apic logs command:
      apic logs
    4. Two compressed files are created: appliance-logs, and node-logs. Copy both files off the VM and upload to the support case.
  • Kubernetes and Openshift: Get the logs from all analytics pods in your environment. Use the command:
    kubectl -n <namespace> logs <analytics pod name> > <analytics pod name>.log
    where:
    • <namespace> is the namespace of your analytics subsystem.
    • <analytics pod name> is the name of the analytics pod. See the list of analytics pods.

    The logs for each pod are written to the file <analytics pod name>.log. Upload all the generated logs to the support case.

Getting the OpenSearch cluster status

If the mustgather script fails you can use the toolkit CLI to get the status of your OpenSearch cluster, and a list of the indices.
  1. Follow the steps to install and configure the toolkit CLI.
  2. Login to the CLI as the cloud admin user:
    apic login --server <platform api endpoint> --username admin --realm provider/default-idp-1
  3. Get the OpenSearch cluster status with:
    apic --mode analytics clustermgmt:catIndices --server <platform api endpoint> --analytics-service <analytics service name> --format json
  4. Get the details of the OpenSearch indices with:
    apic --mode analytics clustermgmt:catIndices --server <platform api endpoint> --analytics-service <analytics service name> --format json
Upload the cluster status and indices output to the support case.