aboutsummaryrefslogtreecommitdiffstats
path: root/common/chapters/control_if.adoc
diff options
context:
space:
mode:
Diffstat (limited to 'common/chapters/control_if.adoc')
-rw-r--r--common/chapters/control_if.adoc4
1 files changed, 2 insertions, 2 deletions
diff --git a/common/chapters/control_if.adoc b/common/chapters/control_if.adoc
index cd639c7..e64f661 100644
--- a/common/chapters/control_if.adoc
+++ b/common/chapters/control_if.adoc
@@ -169,7 +169,7 @@ The rate counter group name have to be prefixed with interval
specification which can be any of "*per_sec*", "*per_min*", "*per_hour*", "*per_day*"
or "*abs*" for absolute value.
-The old-style counters available via "+counter.*+" variables are superceeded by "+rate_ctr.abs+"
+The old-style counters available via "+counter.*+" variables are superseded by "+rate_ctr.abs+"
so its use is discouraged.
There might still be some applications not yet converted to rate_ctr.
@@ -188,7 +188,7 @@ Another implementation is in `scripts/osmo_rate_ctr2csv.py` which will retrieve
for a given Osmocom program and output it in csv format. This can be used to periodically (using systemd timer
for example) retrieve data to build KPI and evaluate how it changes over time.
-Internally it uses "+rate_ctr.*+" variable described in <<ctrl_common_var>> to get the list of counter groups
+Internally it uses "+rate_ctr.*+" variable described in <<ctrl_common_vars>> to get the list of counter groups
and than request all the counters in each group. Applications interested in individual metrics can request it
directly using `rate_ctr2csv.py` as an example.