New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
metrics: add bpf_map_capacity metric which provides max size of maps #28146
Conversation
Commit 128fdebf2bbd5a8cfcb5332996006a54312df986 does not match "(?m)^Signed-off-by:". Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin |
128fdeb
to
62a76d0
Compare
Commit 62a76d063446190c694abdf38f2f04dad3704e4b does not match "(?m)^Signed-off-by:". Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin |
1 similar comment
Commit 62a76d063446190c694abdf38f2f04dad3704e4b does not match "(?m)^Signed-off-by:". Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin |
89399d4
to
b015f0f
Compare
Commit 12e551f7090601c0af1b6e3b3d049b856e43e1ae does not match "(?m)^Signed-off-by:". Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin |
b015f0f
to
dcd37fb
Compare
Commit 12e551f7090601c0af1b6e3b3d049b856e43e1ae does not match "(?m)^Signed-off-by:". Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin |
dcd37fb
to
201752f
Compare
2d41d6b
to
d3a8e44
Compare
d3a8e44
to
36ef3d7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM for docs
36ef3d7
to
472c952
Compare
/test |
472c952
to
3e92d1c
Compare
It is useful to have bpf map capacity metric, which is the defined bpf max size, for writing general Promtheus queries that can detect various issues with map usage (for example, providing an upper bound on FQDN IPs). This is especially helpful in the face of configurable map sizes, where you cannot assume the default value is always used. bpf_map_capacity metrics are emitted per "group" of maps, this is any group of maps that share common purpose and attributes. This avoids having excessive redundant cardinality due to similar map types each having their capacity emitted in a separate metric (ex. endpoint policy maps are all always the same size). Signed-off-by: Tom Hadlaw <tom.hadlaw@isovalent.com>
Signed-off-by: Tom Hadlaw <tom.hadlaw@isovalent.com>
/test |
3e92d1c
to
f958495
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work! LGTM.
/test |
It is useful to have bpf map capacity metric, which is the defined bpf max size, for writing general Promtheus queries that can detect various issues with map usage (for example, providing an upper bound on FQDN IPs).
This is especially helpful in the face of configurable map sizes, where you cannot assume the default value is always used.
bpf_map_capacity metrics are emitted per "group" of maps, this is any group of maps that share common purpose and attributes.
This avoids having excessive redundant cardinality due to similar map types each having their capacity emitted in a separate metric (ex. endpoint policy maps are all always the same size).
As well, maps that are the default map capacity size (i.e. 2^16) are not included in this metric.
A follow up to this change will be adding a bpf map size metric, which can be used in conjunction with this metric to specify exactly how much capacity there is left in a map.
bpf_map_capacity metrics are emitted