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

Report additional context information via Sentry #660

Open
ahus1 opened this issue Feb 5, 2021 · 4 comments · May be fixed by #1329
Open

Report additional context information via Sentry #660

ahus1 opened this issue Feb 5, 2021 · 4 comments · May be fixed by #1329
Labels
enhancement good first issue help wanted

Comments

@ahus1
Copy link
Contributor

ahus1 commented Feb 5, 2021

Why the new feature should be added

When a problem is auto-reported by Sentry, the context information currently information like the IDE and plugin version.

It would be helpful to have the following information to reproduce the issue:

  • Is the IDE in light mode [at least at the time when the issue is forwarded by Sentry] (yes/no), as not all APIs are available in light editing mode.
  • Linux distro/version if the OS is a Linux system, as currently only the Kernel version is reported by Sentry by default and missing dependencies/incompatible packages are impossible to detect.

How the new feature should work

The information would be collected and submitted automatically every time the user submits an issue via Sentry.
No additional interaction will be necessary.
@ahus1
Copy link
Contributor Author

ahus1 commented Feb 5, 2021 •
edited

As will all issues marked as "help wanted", maintainers are willing to help when implementing this issue.

The current code for reporting context information to Sentry is in SentryErrorReporter.java.
Some more lines of code will be necessary to gather the context information described above.

In order to test this, it might be helpful for the developer to register for a free developer Account at sentry.io and exchange the DSN in this file so they can see the reported exceptions in their developer's instance.

@ahus1 ahus1 mentioned this issue Feb 5, 2021
Closed
@vcvitaly
Copy link

I can take it.

@ahus1
Copy link
Contributor Author

ahus1 commented Mar 25, 2023

Hi, that would be great. There are some docs here to get you started around coding for the plugin. https://intellij-asciidoc-plugin.ahus1.de/docs/contributors-guide/contribute-as-a-coder.html

Let me know if this is helpful or if you need more to get started.

vcvitaly pushed a commit to vcvitaly-forks/asciidoctor-intellij-plugin that referenced this issue Apr 14, 2023
Add theme, color mode and Linux platform version to tags reported to …
5fc9a51 
…Sentry (asciidoctor#660)
@vcvitaly
Copy link

@ahus1 Hi. Please check if the approach is ok.

This is the screenshot of reported tags:
image

vcvitaly added a commit to vcvitaly-forks/asciidoctor-intellij-plugin that referenced this issue Apr 14, 2023
@vcvitaly
Replace dots with underscores (asciidoctor#660)
6650180
@ahus1 ahus1 linked a pull request Apr 16, 2023 that will close this issue
Open
7 tasks
vcvitaly pushed a commit to vcvitaly-forks/asciidoctor-intellij-plugin that referenced this issue Jul 4, 2023
@vcvitaly
Add theme, color mode and Linux platform version to tags reported to …
c7d68bd 
…Sentry (asciidoctor#660)
vcvitaly added a commit to vcvitaly-forks/asciidoctor-intellij-plugin that referenced this issue Jul 4, 2023
@vcvitaly
Replace dots with underscores (asciidoctor#660)
a832478
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement good first issue help wanted
Projects
None yet
Milestone
No milestone
2 participants
@ahus1 @vcvitaly