mwiget
commented
6 years ago Turns out, the shell script based conversion from xpath to influxdb rest format works equally well and without any change when using another shema: snabb-softwire-v2:
snabb config get-state -s snabb-softwire-v2 -f xpath $HOSTNAME / \
| tr '/' ' ' | tr '[|]' ' ' | awk '{print $4 "," $2 "," $1 "=" $3 " value=" $5}' \
|grep -v 'value=$' \
| curl -i -XPOST 'http://influxdb:8086/write?db=lwaftr' --data-binary @-
snabb gained yang based configuration and state information via snabb config. Counters are nicely exposed via snabb config get-state using two display output formats: yang or xpath.
I was in need to display near real-time telemetry data of running snabb lwaftr instances via a web page and reverted to Grafana with InfluxDB backend. Starting from the xpath format, I translated it via tr/awk into the required InfluxDB HTTP API:
Granted, not very nice, but functional for the demo. I open this issue to discuss ways to extend get-state to adhere to various output formats for easy consumption of third party time series databases.
Does it make sense to add DB specific output formats to get-state? If so, what are the most common programmatic API's in use?
A running lwaftr installation with 5 interfaces reports these stats:
converted to InfluxDB consumable output via HTTP API: