kubernetes/website

Visually Document Container Memory Metrics and their Relationships

Open

#25.388 aberto em 3 de dez. de 2020

Ver no GitHub
 (22 comments) (7 reactions) (0 assignees)HTML (13.918 forks)batch import
help wantedkind/featurelanguage/enlifecycle/frozenpriority/backlogsig/instrumentationtriage/accepted

Métricas do repositório

Stars
 (4.127 stars)
Métricas de merge de PR
 (Mesclagem média 16d 13h) (160 fundiu PRs em 30d)

Description

This is a Feature Request

What would you like to be added A document that explains what all the different container memory metrics mean and how they are interrelated.

Why is this needed Today, the following metrics exist for container memory:

  • container_memory_cache
  • container_memory_mapped_file
  • container_memory_max_usage_bytes
  • container_memory_rss
  • container_memory_swap
  • container_memory_usage_bytes
  • container_memory_working_set_bytes

I would like to see a document that explains what they are, how they are different or similar to each other, how they nest, what container="" and container="POD" mean, which metric(s) are used by the kubelet to evict, why usage_bytes and max_usage_bytes might differ, the effects of quantized sampling, etc.

Comments A visual description would be amazing here, as there are hierarchical relationships that would benefit from such a view.

Guia do colaborador