-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Errors in generating New Metrics Endpoints #186
Comments
(please ignore different endpoints - basically started with bugreplicate but then needed to document the whole thing from start to finish) |
I think this is probably wholly down to the dates generated by default. The same endpoints I generated for above render just fine when creating a dashboard which uses Date Range Default Any refresh of the date range on metrics/{metric_name} updates the visusalisation and displays the JSON. I think this error is problematic in that up until this point nothing shows in the show JSON toggle - which could lead to presumptions of failed POST of data |
After replicating have determined that the behaviour at heart of this issue (a blank visualisation area) is currently isolated to what is described within #253 so I am closing this ticket |
If you follow steps in the API docs https://bothan.io/api for your own heroku instance the following error should occur
curl -X POST -H "Content-Type: application/json" -d '{"time": "2016-04-12T10:00:00", "value": 500}' "https://$uname:$pwd@$appname.herokuapp.com/metrics/$endpoint"
The endpoint URL should look like this
With these errors in console
If you manually adjust the date range so that one month is displayed in the graph you should see no change in the absent graph or the console errors
If you issue a second curl request with a sequential date (prior or subsequent) and a varied value, like so
curl -X POST -H "Content-Type: application/json" -d '{"time": "2016-04-13T10:00:00", "value": 300}' "https://$uname:$pwd@$appname.herokuapp.com/metrics/$endpoint"
The visualisation renders the most recent CURL
with the same pusher errors
The endpoint will render and store dates subsequent to the date entered in the second curl but not any dates prior
The text was updated successfully, but these errors were encountered: