kubernetes-sigs/prometheus-adapter
1
0
Fork 1
mirror of https://github.com/kubernetes-sigs/prometheus-adapter.git synced 2026-04-06 01:38:10 +00:00
Code Issues Projects Releases Packages Activity Actions

Add a note on resource quanities to walkthrough

Browse source 
Quantities continue to confuse people, so adding concrete examples
should help.
This commit is contained in:
Solly Ross 2018-08-07 15:19:06 -04:00
parent 9f08038f07
commit 77614d151a
1 changed files with 12 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

12
docs/walkthrough.md
View file

@ -273,6 +273,18 @@ Try fetching the metrics again. You should see an increase in the rate
after the collection interval specified in your Prometheus configuration after the collection interval specified in your Prometheus configuration
has elapsed. If you leave it for a bit, the rate will go back down again. has elapsed. If you leave it for a bit, the rate will go back down again.
Notice that the API uses Kubernetes-style quantities to describe metric
values. These quantities use SI suffixes instead of decimal points. The
most common to see in the metrics API is the `m` suffix, which means
milli-units, or 1000ths of a unit. If your metric is exactly a whole
number of units on the nose, you might not see a suffix. Otherwise, you'll
probably see an `m` suffix to represent fractions of a unit.
For example, here, `500m` would be half a request per second, `10` would
be 10 requests per second, and `10500m` would be `10.5` requests per
second.
### Troubleshooting Missing Metrics ### Troubleshooting Missing Metrics
If the metric does not appear, or is not registered with the right If the metric does not appear, or is not registered with the right