-
Notifications
You must be signed in to change notification settings - Fork 2
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
Enable logging errors per instance #3
Milestone
Comments
... possibly per-hub as well? |
I'm thinking something like > curl -XPOST http://localhost:5000/sessions/<id>/events -d '{"error":"app_specific_error_message", "timestamp":1411727900}'
> curl http://localhost:5000/sessions/<id>/events?count=5
[{"error":"app_specific_error_message", "timestamp":1411727900, "shale:time_received":":2014-09-26T10:39:00Z"}] WDYT @chris-martin? I figure a format like that will work for eg #12 as well as other services, and if shale keeps ephemeral access to the last X events, it can make routing decisions based on that. |
We'll probably also need a nodes endpoint > curl http://localhost:5000/nodes
[{"node":"http://some_host.example.com:5555/wd/hub", "tags":["aws"], "id":"<id>"}]
> curl http://localhost:5000/nodes/<id>/events
[{"error":"app_specific_error_message", "timestamp":1411727900, "shale:time_received":":2014-09-26T10:39:00Z"}] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: