fly/flightgear
1
0
Fork 0
Code Activity

Sentry experiment: record warnings/alerts

Browse source 
This means that when a crash/exception occurs, we can see the preceding
warnings and alerts. Not sure if this will really help, so giving it
a test.
This commit is contained in:
James Turner 2020-09-18 10:34:40 +01:00
parent d56e3857b6
commit 5329c4024b
1 changed files with 28 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

28
src/Main/sentryIntegration.cxx
View file

@ -20,6 +20,7 @@
#include "sentryIntegration.hxx"
#include <simgear/debug/LogCallback.hxx>
#include <simgear/debug/logstream.hxx>
#include <simgear/misc/sg_path.hxx>
#include <simgear/props/props.hxx>
@ -40,6 +41,31 @@ static bool static_sentryEnabled = false;
#include <sentry.h>
namespace {
class SentryLogCallback : public simgear::LogCallback
{
public:
SentryLogCallback() : simgear::LogCallback(SG_ALL, SG_WARN)
{
}
bool doProcessEntry(const simgear::LogEntry& e) override
{
// we need original priority here, so we don't record MANDATORY_INFO
// or DEV_ messages, which would get noisy.
const auto op = e.originalPriority;
if ((op != SG_WARN) && (op != SG_ALERT)) {
return true;
}
flightgear::addSentryBreadcrumb(e.message, (op == SG_WARN) ? "warning" : "error");
return true;
}
};
} // namespace
namespace flightgear
{
@ -100,6 +126,8 @@ void initSentry()
sentry_init(options);
static_sentryEnabled = true;
sglog().addCallback(new SentryLogCallback);
}
void delayedSentryInit()