Errors reported to sentry.io result in an <unlabelled event>
See original GitHub issueIn our setup, we use sentry.io to report errors. This setup seems to be currently broken for our quarkus services though. Errors reported to sentry.io do not show any actual content but are marked as unlabelled events:
Expected behavior Errors in sentry should contain stacktraces, error messages etc.
Actual behavior All errors reported result in unlabelled events with actual no content.
Configuration gradle.properties:
# Add your application.properties here, if applicable.
#Gradle properties
#Fri Dec 18 09:44:23 CET 2020
quarkusPluginVersion=1.12.1.Final
quarkusPlatformArtifactId=quarkus-bom
quarkusPluginId=io.quarkus
quarkusPlatformGroupId=io.quarkus
quarkusPlatformVersion=1.12.1.Final
org.gradle.logging.level=INFO
dependencies from build.gradle
dependencies {
implementation enforcedPlatform("${quarkusPlatformGroupId}:${quarkusPlatformArtifactId}:${quarkusPlatformVersion}")
implementation 'io.quarkus:quarkus-amazon-dynamodb'
implementation 'software.amazon.awssdk:dynamodb-enhanced'
implementation 'io.quarkus:quarkus-smallrye-openapi'
implementation 'io.quarkus:quarkus-jackson'
implementation 'com.fasterxml.jackson.module:jackson-module-kotlin'
implementation 'de.spinscale.quarkus:quarkus-logging-ecs:0.0.2'
implementation 'io.quarkus:quarkus-logging-sentry'
implementation 'io.quarkus:quarkus-micrometer'
implementation 'io.micrometer:micrometer-registry-prometheus'
implementation 'io.quarkus:quarkus-cache'
implementation 'io.quarkus:quarkus-config-yaml'
implementation 'io.quarkus:quarkus-smallrye-health'
implementation 'io.quarkus:quarkus-smallrye-jwt'
implementation 'io.quarkus:quarkus-smallrye-jwt-build'
implementation 'io.quarkus:quarkus-container-image-jib'
implementation 'io.quarkus:quarkus-kotlin'
implementation 'io.quarkus:quarkus-resteasy-reactive'
implementation 'io.quarkus:quarkus-resteasy-reactive-jackson'
implementation 'org.jetbrains.kotlin:kotlin-stdlib-jdk8'
implementation 'io.github.microutils:kotlin-logging:1.12.0'
}
Environment (please complete the following information):
- Quarkus version or git rev: 1.12.1.Final
- Build tool (ie. output of
mvnw --version
orgradlew --version
): Gradle 6.3
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:10 (6 by maintainers)
Top Results From Across the Web
[Bug] <unlabeled event> #1271 - getsentry/sentry-javascript
I'm experiencing the same on an alternative javascript stack, using React with Redux and Redux Sagas, seeing the same error being reported both ......
Read more ><unlabeled event> when reporting error from embedded ...
Hello! I'm working on adding Sentry monitoring for JS errors that occur in a webview embedded in a native (Android) application.
Read more >Integrated error tracking compatibility with Sentry SDK - GitLab
The purpose of this issue is ensure that integrated error tracking works with all major Sentry SDK. Sentry SDK, Does it work? MR's...
Read more >React Error Handling And Reporting With Error Boundary And ...
Finally, we'll integrate Sentry into our error boundary for realtime error reporting. In this article, we'll look at error boundaries in React.
Read more >The Sentry alternative that solves way more crashes out of the ...
Sentry is an error handling tool myopically focused on logging and crashes. As an event-based approach, Sentry requires a ton of manual instrumentation, ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
FYI we are working on it on the Sentry SDK side: https://github.com/getsentry/sentry-java/pull/1329
You can mock the
transport
- which is the last piece before payloads are sent to Sentry. Maybe you can take a look at how I did the tests for Logback appender to verify events at the very end: https://github.com/getsentry/sentry-java/blob/main/sentry-logback/src/test/kotlin/io/sentry/logback/SentryAppenderTest.kt#L82 and https://github.com/getsentry/sentry-java/blob/main/sentry-test-support/src/main/kotlin/io/sentry/test/assertions.kt