Feature #2550
closedexample on how to periodically dump KPI/counter to CSV file
100%
Description
We need to create some example script/tool that periodically obtains a number of KPIs/counters from one or more osmocom programs (via CTRL) and logs/dumps them to a CSV file.
Related issues
Updated by msuraev over 6 years ago
Which language shall I use? Python? And to which repo shall I put this script?
Updated by laforge over 6 years ago
Yes, Python please.
I think if the tool is generic, it should go in libosmocore/contrib. If it's specific to one particular application, it should go into the repo of that program (e.g. osmo-bsc.git).
Updated by msuraev over 6 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 10
Gerrit 5017 with the implementation of necessary introspection function has been sent for review.
Updated by msuraev over 6 years ago
- % Done changed from 10 to 50
The C side is implemented in gerrit 5023, the python side is in gerrit 5029. The prerequisites were merged already, waiting for review/merge. Related documentation update is in gerrit 5014.
Updated by msuraev over 6 years ago
- Related to Feature #2684: add gerrit tests to osmo-python-tests added
Updated by msuraev over 6 years ago
- Related to Bug #2770: osmo-python-tests fails with both python-2.7 and 3.6 ?!? added
Updated by msuraev over 6 years ago
- Related to deleted (Bug #2770: osmo-python-tests fails with both python-2.7 and 3.6 ?!?)
Updated by msuraev over 6 years ago
- Blocked by Bug #2770: osmo-python-tests fails with both python-2.7 and 3.6 ?!? added
Updated by msuraev over 6 years ago
- % Done changed from 50 to 80
Prerequisite and related patches were merged, gerrit 5029 is rebased onto latest master.
Updated by msuraev over 6 years ago
- Status changed from Stalled to Resolved
- % Done changed from 80 to 100
- Resolution set to fixed
Merged to osmo-python-tests master as scripts/osmo_rate_ctr2csv.py
