summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMax <msuraev@sysmocom.de>2018-01-04 14:58:12 +0100
committerMax <msuraev@sysmocom.de>2018-01-04 14:58:12 +0100
commita8d2935f830900dc0baeca0ddc1ae7391900f623 (patch)
treef1690643fa9e70285e90c5369e00d7b3aadf83e5
parenta13675c549c5b2077b54f3b384ed0304ad3b736e (diff)
Update path to ctrl scripts
-rw-r--r--common/chapters/control_if.adoc6
1 files changed, 3 insertions, 3 deletions
diff --git a/common/chapters/control_if.adoc b/common/chapters/control_if.adoc
index dd6938a..ea55cd7 100644
--- a/common/chapters/control_if.adoc
+++ b/common/chapters/control_if.adoc
@@ -176,7 +176,7 @@ There might still be some applications not yet converted to rate_ctr.
=== Control Interface python examples
In the `osmo-python-tests` repository, there is an example python script
-called `osmopy/osmo_ctrl.py` which implements the Osmocom
+called `scripts/osmo_ctrl.py` which implements the Osmocom
control interface protocol.
You can use this tool either stand-alone to perform control interface
@@ -184,7 +184,7 @@ operations against an Osmocom program, or you can use it as a reference
for developing your own python software talking to the control
interface.
-Another implementation is in `osmopy/rate_ctr2csv.py` which will retrieve performance counters
+Another implementation is in `scripts/osmo_rate_ctr2csv.py` which will retrieve performance counters
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.
@@ -196,7 +196,7 @@ directly using `rate_ctr2csv.py` as an example.
.Example: Use `rate_ctr2csv.py` to get rate counters from OsmoBSC
----
-$ ./osmopy/rate_ctr2csv.py --header
+$ ./scripts/osmo_rate_ctr2csv.py --header
Connecting to localhost:4249...
Getting rate counter groups info...
"group","counter","absolute","second","minute","hour","day"