On 08.09.24 3:49 PM, Tor Arne Vestbø wrote:
Hi Nicolas,
How are you integrating KDE with Sentry?
I wrote a very minimal integration for Qt
herehttps://docs.sentry.io/platforms/native/guides/qt/ that plumbs
qInstallMessageHandler to the sentry
eventshttps://github.com/getsentry/sentry-native/blob/master/src/integrations/sentry_integration_qt.cpp.
Do you do something similar?
The client-side integration works with systemd-coredumpd and KCrash
(https://invent.kde.org/frameworks/kcrash/), which is mostly about
collecting metadata such as application and Qt version, OS/graphics
information, and logs. Therefore we currently only have it working on
Linux. For e.g. our Windows applications we want to rely on Windows'
native crash reporting and are looking into aggregating that into our
Sentry.
When you get reports from users in Sentry, do you have the ability to get in
touch with them and run the app with additional Qt logging categories enabled?
We don't have that kind of communication channel with Sentry, only with
our Bugzilla-based system which is running in parallel but receives
fewer reports.
If so, that might be useful data to pass on to us (in some way).
Alternatively, perhaps some generic instructions can be given to users that if
they opt in to crash analytics, and are experiencing crashes, to enable a
common subset of relevant logging categories?
https://invent.kde.org/frameworks/kcrash/-/merge_requests/56 is
exploring automatically increasing the log verbosity.
Regarding the reporting, does Sentry allow sharing individual incidents? If so
that would be helpful to include in the bug reports you create for Qt.
Depending on the volume of reports you get, it might be beneficial to group
them (option two in your proposal). But having access to the Sentry dashboard
would also be nice.
I'd have to check with Harald who is driving Sentry on our side, but we
should be able to arrange something useful.
Cheers,
Tor Arne
On Sep 8, 2024, at 3:25 PM, Nicolas Fella via
Development<development@qt-project.org> wrote:
Hi,
at Akademy I had a chat with Volker Hilsheimer and now want to open this
to a wider audience.
In KDE we have an automatic crash reporting system based on Sentry.
Naturally some amount of the crash reports point to the problem being in
Qt instead of in KDE code. In those cases we of course want to create
useful Qt bugreports for you. Unfortunately it is not always easy for us
to narrow down or reproduce the problem so a lot of issues are never
reported to you, even if they could be potentially interesting to you.
Now I am wondering how we can improve the communication pipeline in that
regard and make sure you Qt people are aware of the reports we get and
can give your input on it. I see a few possible ways to go about this,
which aren't necessarily mutually exclusive:
- We report every Qt-related-looking crash we get as a QTBUG, even if we
don't have a reproducer or much information on what's going on
- Someone from KDE writes a weekly(?)/monthly(?) summary email with
relevant looking reports that we would like someone from Qt to look at
- We give some Qt people access to our crash reporting system directly
Let me know what you think about this
Cheers
Nico
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
