Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add Support for Traces #2

Closed
GoGoCarl opened this issue Jul 19, 2013 · 0 comments
Closed

Add Support for Traces #2

GoGoCarl opened this issue Jul 19, 2013 · 0 comments
Assignees
@GoGoCarl
Labels
enhancement

Comments

@GoGoCarl
Copy link
Owner

Exceptions should be sent through /traces for reasons.
@ghost ghost assigned GoGoCarl Jul 19, 2013
GoGoCarl added a commit that referenced this issue Jul 19, 2013
@GoGoCarl
Support for Traces, multiple API keys, Logger.
a5192e6 
Appygram4J now support sending Traces to Appygram, the
preferred way for sending exceptions.  The README has
been updated with examples on how to use this.

Also, Appygram.send is now Appygram.Global.send.  This
is to allow for users to configure multiple instances of
AppygramMessenger, which are connected to differing API
keys.  Configuration works the same way; information is
in the README.

Finally, all logging is being routed through AppygramLogger.
There isn't much to log, aside from configuration errors
when trying to send an Appygram, but it's there.

See #2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@GoGoCarl GoGoCarl

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoGoCarl