-
Notifications
You must be signed in to change notification settings - Fork 263
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
Add info from getInfo() to Sentry logs #359
Labels
feature
Adding functionality that adds value
Comments
Phergus
added
feature
Adding functionality that adds value
up for grabs
Minimal context and are well-suited for new contributors
labels
Aug 23, 2019
xdy
added a commit
to xdy-forks/maptool
that referenced
this issue
Dec 9, 2019
…eing untrusted. How to fix?
Calling getInfo("server") works, but not sure how to call getInfo("campaign") from MapToolEventQueue.reportToSentryIO so as to avoid permission problems. |
xdy
added a commit
to xdy-forks/maptool
that referenced
this issue
Dec 28, 2019
…Sentry. Switch to trusted context to add info from getInfo("campaign") to Sentry, then switch back.
Phergus
removed
the
up for grabs
Minimal context and are well-suited for new contributors
label
Dec 28, 2019
Phergus
added a commit
that referenced
this issue
Dec 28, 2019
#359 If server is running, add info from getInfo("server") to Sentry.
Code merged. Will see if info shows up in the Sentry reports. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The info from
getInfo("server")
andgetInfo("campaign")
can be useful in error reports and should be added.Currently, some of the information is there (like basic memory info) but the campaign info includes other configuration settings that can be useful for diagnosing stack traces.
The text was updated successfully, but these errors were encountered: