Kubernetes 360 Prerequisites

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.

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.

To ensure your Kubernetes 360 dashboard is up and running, you'll need to send the following metrics:

Metric name	Labels
*	p8s_logzio_name // Equivalent to a Cluster's name
kube_pod_status_phase	p8s_logzio_name, namespace, pod, phase, uid
kube_pod_info	p8s_logzio_name, namespace, host_ip, node, pod
container_cpu_usage_seconds_total	p8s_logzio_name, namespace, pod, region, topology_kubernetes_io_region, container
kube_pod_container_resource_limits	p8s_logzio_name, namespace, pod, resource
container_memory_working_set_bytes	p8s_logzio_name, namespace, pod, container
kube_pod_container_info	p8s_logzio_name, namespace, pod
container_network_transmit_bytes_total	p8s_logzio_name, namespace, pod
container_network_receive_bytes_total	p8s_logzio_name, namespace, pod
kube_pod_created	p8s_logzio_name, namespace, pod
kube_pod_owner	p8s_logzio_name, namespace, pod, owner_kind, owner_name
kube_pod_container_status_restarts_total	p8s_logzio_name, namespace, pod
kube_pod_status_reason	p8s_logzio_name, namespace, pod, reason
kube_pod_container_status_waiting_reason	p8s_logzio_name, namespace, pod, reason
node_cpu_seconds_total	p8s_logzio_name, instance, kubernetes_node
kube_node_status_allocatable	p8s_logzio_name, node, resource
node_memory_MemAvailable_bytes	p8s_logzio_name, instance, kubernetes_node
node_memory_MemTotal_bytes	p8s_logzio_name, instance, kubernetes_node
kube_node_role	p8s_logzio_name, status, role, node
kube_node_status_condition	p8s_logzio_name, status, role, node
kube_node_created	p8s_logzio_name, node
node_filesystem_avail_bytes	p8s_logzio_name, instance, kubernetes_node
node_filesystem_size_bytes	p8s_logzio_name, instance, kubernetes_node
kube_replicaset_owner	p8s_logzio_name, namespace, owner_kind, owner_name, replicaset
kube_deployment_created	p8s_logzio_name, namespace, deployment
kube_deployment_status_condition	p8s_logzio_name, namespace, deployment, status

Additional Kubernetes metrics

To enrich your services and infrastructure data even further, we recommend sending the following metrics as well:

Metric name	Labels
*	p8s_logzio_name // Equivalent to a Cluster's name
kube_pod_container_resource_requests	p8s_logzio_name, namespace, pod, container, resource
container_memory_usage_bytes	p8s_logzio_name, namespace, pod, container, instance, node
kube_pod_container_status_waiting	p8s_logzio_name, pod, container
kube_pod_container_status_terminated	p8s_logzio_name, pod, container
kube_pod_container_status_running	p8s_logzio_name, pod
kube_node_status_capacity	p8s_logzio_name, node, resource
node_disk_reads_completed_total	p8s_logzio_name, kubernetes_node
node_disk_read_bytes_total	p8s_logzio_name, kubernetes_node
node_disk_read_time_seconds_total	p8s_logzio_name, kubernetes_node
node_disk_writes_completed_total	p8s_logzio_name, kubernetes_node
node_disk_written_bytes_total	p8s_logzio_name, kubernetes_node
node_disk_write_time_seconds_total	p8s_logzio_name, kubernetes_node
node_network_transmit_bytes_total	p8s_logzio_name, kubernetes_node
node_receive_transmit_bytes_total	p8s_logzio_name, kubernetes_node
node_memory_MemFree_bytes	p8s_logzio_name, kubernetes_node
kube_node_info	p8s_logzio_name, node
kube_deployment_status_replicas	p8s_logzio_name, namespace, deployment
kube_deployment_status_replicas_updated	p8s_logzio_name, namespace, deployment
kube_deployment_spec_replicas	p8s_logzio_name, namespace, deployment
kube_daemonset_status_number_available	p8s_logzio_name, daemonset
kube_daemonset_status_number_unavailable	p8s_logzio_name, daemonset
kube_daemonset_status_current_number_scheduled	p8s_logzio_name, daemonset
kube_daemonset_status_number_misscheduled	p8s_logzio_name, daemonset
kube_daemonset_status_desired_number_scheduled	p8s_logzio_name, daemonset
kube_statefulset_status_replicas	p8s_logzio_name, namespace, app_kubernetes_io_instance, statefulset
kube_statefulset_replicas	p8s_logzio_name, namespace, app_kubernetes_io_instance, statefulset
container_network_transmit_packets_total	p8s_logzio_name, namespace, pod
container_network_receive_packets_total	p8s_logzio_name, namespace, pod
container_network_transmit_packets_dropped_total	p8s_logzio_name, namespace, pod
container_network_receive_packets_dropped_total	p8s_logzio_name, namespace, pod, container
node_memory_Cached_bytes	p8s_logzio_name, kubernetes_node
node_memory_Buffers_bytes	p8s_logzio_name, kubernetes_node
kube_statefulset_status_replicas_updated	p8s_logzio_name, namespace, statefulset, app_kubernetes_io_instance
kube_deployment_labels	p8s_logzio_name, namespace, deployment
kube_replicaset_status_replicas	p8s_logzio_name, status, namespace, deployment, owner_kind, owner_name, replicaset
kube_replicaset_status_ready_replicas	p8s_logzio_name, status, namespace, deployment, owner_kind, owner_name, replicaset
kube_pod_container_status_terminated_reason	p8s_logzio_name, pod, container, reason
kube_node_spec_unschedulable	p8s_logzio_name, node, resource, status, reason
kube_node_labels	p8s_logzio_name, node, resource
kube_pod_status_ready	p8s_logzio_name, namespace, pod, phase, uid
kube_pod_container_status_ready	p8s_logzio_name, namespace, pod, container
kube_replicaset_labels	p8s_logzio_name, namespace, deployment, owner_kind, owner_name, replicaset
kube_replicaset_spec_replicas	p8s_logzio_name, namespace, deployment, owner_kind, owner_name, replicaset
kube_deployment_status_replicas_available	p8s_logzio_name, namespace, deployment
kube_deployment_status_replicas_unavailable	p8s_logzio_name, namespace, deployment
kube_statefulset_status_replicas_available	p8s_logzio_name, namespace, app_kubernetes_io_instance, statefulset
node_disk_io_time_seconds_total	p8s_logzio_name, kubernetes_node
node_network_receive_bytes_total	p8s_logzio_name, kubernetes_node
node_network_transmit_packets_total	p8s_logzio_name, kubernetes_node
node_network_receive_packets_total	p8s_logzio_name, kubernetes_node
node_network_transmit_drop_total	p8s_logzio_name, kubernetes_node
node_network_receive_drop_total	p8s_logzio_name, kubernetes_node
node_filesystem_free_bytes	p8s_logzio_name, instance
kube_daemonset_status_number_ready	p8s_logzio_name, daemonset
kube_daemonset_labels	all labels
kube_statefulset_labels	all labels
kube_job_labels	all labels
kube_pod_labels	all labels
kube_job_status_succeeded	all labels
kube_job_complete	all labels
kube_job_status_failed	all labels
kube_job_status_completion_time	all labels
machine_cpu_cores	all labels
node_boot_time_seconds	all labels
node_time_seconds	all labels
kube_namespace_status_phase	all labels
kubelet_volume_stats_inodes	all labels
kubelet_volume_stats_inodes_used	all labels
kubelet_volume_stats_used_bytes	all labels
kube_persistentvolumeclaim_info	all labels
kube_persistentvolumeclaim_resource_requests_storage_bytes	all labels
kube_job_owner	all labels

Manually configuring Security Risks

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

• Ship reports from Trivy operator.
• Configure and send security logs.

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.