Get logs and version

For the Kubernetes integration, the infrastructure agent adds a log entry only in the event of an error. Most common errors are displayed in the standard (non-verbose) logs. If you are doing a more in-depth investigation on your own or with New Relic Support, you can enable verbose mode.

To get verbose logging details for an integration using a manifest file:

1. Enable verbose logging: In the deployment file, set the value of NRIA_VERBOSE to 1.

2. Apply the modified configuration by running:

   kubectl apply -f your_newrelic_k8s.yaml

   コピー

3. Leave on verbose mode for a few minutes, or until you feel enough activity has occurred.

4. Disable verbose mode: Set the NRIA_VERBOSE value back to 0.

5. Apply the restored configuration by running:

   kubectl apply -f your_newrelic_k8s.yaml

   コピー

6. Get a list of nodes in the environment:

   kubectl get nodes --all-namespaces

   コピー

7. Get a list of infrastructure and kube-state-metrics pods:

   kubectl get pods --all-namespaces -o wide | egrep 'newrelic|kube-state-metrics'

   コピー

8. Get logs from the pods connecting to kube-state-metrics.

9. Retrieve kube-state-metrics service configuration.

For the Kubernetes integration, the infrastructure agent adds a log entry only in the event of an error. Most common errors are displayed in the standard (non-verbose) logs. If you're doing a more in-depth investigation on your own or with New Relic Support, you can enable verbose mode.

To get verbose logging details for an integration using Helm:

1. Enable verbose logging:

   helm upgrade -n <namespace> --reuse-values newrelic-bundle --set newrelic-infrastructure.verboseLog=true newrelic/nri-bundle

   コピー
2. Leave on verbose mode for a few minutes, or until enough activity has occurred.
3. When you have the information you need, disable verbose logging:

   helm upgrade --reuse-values newrelic-bundle --set newrelic-infrastructure.verboseLog=false newrelic/nri-bundle

   コピー
4. Follow the steps to restore your configuration from step 5 in the section, Get verbose logs for installations using a manifest file.

For the Kubernetes integration, the infrastructure agent is distributed as a Docker image that contains the infrastructure agent and the Kubernetes integration. The Docker image is tagged with a version, and the infrastructure agent also has its own version.

When the agent is successfully sending information to New Relic, you can retrieve the versions of the infrastructure agent for Kubernetes (the Docker image) you are running in your clusters by using the following NRQL query:

FROM K8sContainerSample SELECT uniqueCount(entityId) WHERE containerName = 'newrelic-infra' facet clusterName, containerImage

If the agent is not reporting any data:

1. Get the version(s) of the New Relic integration for Kubernetes that you are running in a cluster using kubectl:

   kubectl get pods --all-namespaces -l name=newrelic-infra -o jsonpath="{.items..spec..containers..image}"

   コピー

2. Look for output similar to this:

   newrelic/infrastructure-k8s:1.0.0

   コピー

To retrieve the version of kube-state-metrics running on your clusters, run the following NRQL query:

FROM K8sContainerSample SELECT uniqueCount(entityId) WHERE containerName LIKE '%kube-state-metrics%' facet clusterName, containerImage

To get the logs from pods connecting to kube-state-metrics:

1. Get the nodes that kube-state-metrics is running on:

   kubectl get pods --all-namespaces -o wide | grep kube-state-metrics

   コピー

   Look for output similar to this:

   kube-system   kube-state-metrics-5c6f5cb9b5-pclhh     2/2       
   Running   4          4d        172.17.0.3   minikube

   コピー

2. Get the New Relic pods that are running on the same node as kube-state-metrics:

   kubectl describe node minikube | grep newrelic-infra

   コピー

   Look for output similar to this:

   default                    newrelic-infra-5wcv6                     100m (5%)
   0 (0%)      100Mi (5%)       100Mi (5%)

   コピー

3. Retrieve the logs for the nodes by running:

   kubectl logs newrelic-infra-5wcv6

   コピー

To retrieve the configuration:

1. Run:

   kubectl get pods --all-namespaces | grep "kube-state-metrics"

   コピー

2. Look for a response similar to this:

   kube-system   kube-state-metrics-5c6f5cb9b5-5wf9m     2/2       
   Running       8          6d

   コピー

3. Review the namespace in the first column.

   kubectl describe service kube-state-metrics -n <namespace>

   コピー

To get the logs from a pod running on a master node:

1. Get the nodes that are labelled as master:

   kubectl get nodes -l node-role.kubernetes.io/master=""

   コピー

   Or,

   kubectl get nodes -l kubernetes.io/role="master"

   コピー

   Look for output similar to this:

   NAME                         STATUS  ROLES   AGE   VERSION
   ip-10-42-24-4.ec2.internal   Ready   master  42d   v1.14.8

   コピー

2. Get the New Relic pods that are running on one of the nodes returned in the previous step:

   kubectl get pods --field-selector spec.nodeName=ip-10-42-24-4.ec2.internal -l name=newrelic-infra --all-namespaces

   コピー

   Look for output similar to this:

   newrelic-infra-whvzt

   コピー

3. Retrieve the logs for the nodes by running:

   kubectl logs newrelic-infra-whvzt

   コピー