Skip to content

Commit 0909a61

Browse files
authored
Docs: Add CPU usage note for --metrics-per-undefined-host. (#12309)
1 parent 02a3933 commit 0909a61

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/user-guide/monitoring.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -168,7 +168,7 @@ According to the above example, this URL will be http://10.192.0.3:31086
168168

169169
- By default request metrics are labeled with the hostname. When you have a wildcard domain ingress, then there will be no metrics for that ingress (to prevent the metrics from exploding in cardinality). To get metrics in this case you have two options:
170170
- Run the ingress controller with `--metrics-per-host=false`. You will lose labeling by hostname, but still have labeling by ingress.
171-
- Run the ingress controller with `--metrics-per-undefined-host=true --metrics-per-host=true`. You will get labeling by hostname even if the hostname is not explicitly defined on an ingress. Be warned that cardinality could explode due to many hostnames.
171+
- Run the ingress controller with `--metrics-per-undefined-host=true --metrics-per-host=true`. You will get labeling by hostname even if the hostname is not explicitly defined on an ingress. Be warned that cardinality could explode due to many hostnames and CPU usage could also increase.
172172

173173
### Grafana dashboard using ingress resource
174174
- If you want to expose the dashboard for grafana using an ingress resource, then you can :

0 commit comments

Comments
 (0)