Skip to main content

Kubernetes 360 Prerequisite

Kubernetes 360 application provides an overview of your Kubernetes data, providing a quick overview of your current deployments, pods, and more useful information regarding your environment.

Main dashboard

Manually shipping Kubernetes data

If you already have Kubernetes 360 data in your Logz.io account or prefer connecting Kubernetes manually, you'll need an active Infrastructure Monitoring account, and ensure that your Kubernetes data is connected to Logz.io.

In addition, you'll need to ship your cluster metrics from the following sources:

  • Node exporter (should be installed on every node).
  • CAdvisor.
  • Kube-state-metrics version 2.1 or higher.

And send the following metrics:

Metric nameLabels
*p8s_logzio_name // Equivalent to a Cluster's name
kube_pod_status_phasepod, uid, node, host_ip, phase, namespace
kube_pod_infopod,namespace,p8s_logzio_name,region
container_cpu_usage_seconds_totalpod, region, topology_kubernetes_io_region, container
container_memory_working_set_bytespod, container, resource
kube_pod_container_resource_limitspod
kube_pod_container_infopod
container_network_transmit_bytes_totalpod
container_network_receive_bytes_totalpod
kube_pod_createdpod
kube_pod_ownerpod, owner_kind, owner_name
kube_pod_container_status_restarts_totalpod
kube_pod_status_reasonpod, reason
kube_pod_container_status_waiting_reasonpod, reason
node_cpu_seconds_totalinstance, mode
node_memory_MemAvailable_bytesinstance
node_memory_MemTotal_bytesinstance
kube_node_rolenode,role
kube_node_status_conditionnode, status, condition
kube_node_creatednode
node_filesystem_avail_bytesinstance
node_filesystem_size_bytesinstance
kube_node_status_allocatableresource, resource
kube_node_labelslogzio_p8s_name
kube_replicaset_ownerowner_kind, owner_name,replicaset
kube_deployment_createddeployment
kube_deployment_status_conditiondeployment,status
kube_daemonset_labelsall labels
kube_daemonset_status_number_readyall labels
kube_daemonset_status_number_availableall labels
kube_daemonset_status_number_unavailableall labels
kube_daemonset_status_current_number_scheduledall labels
kube_daemonset_status_number_misscheduledall labels
kube_daemonset_status_desired_number_scheduledall labels
kube_job_labelsall labels
kube_job_completeall labels
kube_job_status_failedall labels
kube_job_status_succeededall labels
kube_job_completeall labels
kube_job_status_failedall labels
kube_job_status_completion_timeall labels
kube_replicaset_labelsall labels
kube_replicaset_spec_replicasall labels
kube_replicaset_status_replicasall labels
kube_replicaset_status_ready_replicasall labels
kube_statefulset_replicasall labels
kube_statefulset_status_replicasall labels
kube_statefulset_status_replicas_updatedall labels
kube_statefulset_status_replicas_availableall labels
kube_job_ownerall labels

Manually configuring Security Risks

To add Security risks view to your existing Kubernetes data, you need to:

After setting up the Trivy operator, ensure your account receives type:trivy logs.

If you encounter an issue while setting up your metrics or logs, contact Logz.io's support team for additional help.