rochaporto / dashing-openstack Goto Github PK

For others looking to call this via command line..

curl -d '{ "auth_token": "YOUR_TOKEN", "title": "Progress", "progress_items" : [ { "name": "Metric1", "progress": 20, "value": 1, "max": 5 }, { "name": "Metric3", "progress": 40, "value": 2, "max": 5 }, { "name": "Metric2", "pro
gress": 90, "value": 90, "max": 100 } ] }'  http://localhost:3030/widgets/widgetid

In addition to the percentage against their quota, it would be useful to get the actual numbers in (like 2/10 (20%) or something like that).

Weird but as we package aviator now, somewhere in the start procedure it requires git.

Easiest is to simply add it to the deb deps for now.

Right now we simply check for the current state. We should take into account acknowledged / downtime states too when displaying the numbers for warning and critical.

I use admin user wich have admin role only on admin tenant, but keystone does not fetch all tenant, so I can not see tenants on the dashboard. Is there a way to tell aviator to use admin URL.

Aviator logs a lot if one sets log_file in the Session object, but includes urls and too much detail, need to check if it can be tuned.

But icinga should also start logging, ideally to syslog. The json replies are quite useful, with things like:
{"success":false,"errors":["User has insufficient rights to access the api"]}

I see that this project is kind of old. I am having problems getting the dashboard up for my Icehouse openstack instance. Should it work for that version?

What are all the things that need to be configured?

I am getting this error when running dashing:
scheduler caught exception:
845: NaN not allowed in JSON
/var/lib/gems/1.9.1/gems/dashing-1.3.4/lib/dashing/app.rb:125:in to_json' /var/lib/gems/1.9.1/gems/dashing-1.3.4/lib/dashing/app.rb:125:insend_event'
/home/dashing/dashing-openstack/jobs/openstack.rb:157:in block (2 levels) in <top (required)>' /home/dashing/dashing-openstack/jobs/openstack.rb:138:ineach'
/home/dashing/dashing-openstack/jobs/openstack.rb:138:in `block in <top (required)>'

Any idea what to check?