Juniper / open-nti

Open Network Telemetry Collector build with open source tools
Apache License 2.0
231 stars 93 forks source link

not able to specify microseconds in the format field #187

Open ghost opened 7 years ago

ghost commented 7 years ago

Hi

what should I use in the format field to be able to display the yaxe in microseconds? I am autogenerating my dashboard through the python script and I cannot find which unit to use. Al

3fr61n commented 7 years ago

Hi

Are you talking about this parameter?

screen shot 2017-09-26 at 12 08 25
3fr61n commented 7 years ago

If so... inside the dashboard json file, the yaxes block should looks like

         "yaxes": [
            {
              "format": "µs",    <--- Left Y
              "logBase": 1,
              "max": null,
              "min": null,
              "show": true
            },
            {
              "format": "short",  <-- Right Y
              "logBase": 1,
              "max": null,
              "min": null,
              "show": true
            }
          ],
ghost commented 7 years ago

yep, but when I try to define "µs" in the dashboard template it does not work. I will try to post the error message

ghost commented 7 years ago

sorry for the delay, I got disturbed by a lot of issues in the past few days :(

but that's what I see when I set µs

opennti - INFO - Dashboard File name : data_collection_agent_dashboard.json Traceback (most recent call last): File "gendashboard.py", line 182, in text_file.write(dashboard_tpl_rdr) UnicodeEncodeError: 'ascii' codec can't encode character u'\xb5' in position 45648: ordinal not in range(128)

template: graph-lines-02.j2 datasource: influxdb title: "RPM Probes" span: 12 fill: 1

yaxes:

targets: A: query: > SELECT mean(value) FROM /($host_regex).rpm..max-delay/ WHERE $timeFilter GROUP BY time($GroupBy) B: query: > SELECT mean(value) FROM /($host_regex).rpm..min-delay/ WHERE $timeFilter GROUP BY time($GroupBy)

templatings_used: