• Home
• io.quarkus
• quarkus-logging-sentry
• 1.13.2.Final
• source code
• SentryConfig.jdp

×

Project download

Many resources are needed to download a project. Please understand that we have to compensate our server costs. Thank you in advance.
Project price only 1 $

You can buy this project and download/modify it how often you want.

io.quarkus.logging.sentry.SentryConfig.jdp Maven / Gradle / Ivy

#
#Wed Apr 14 14:22:01 CEST 2021
io.quarkus.logging.sentry.SentryConfig.release=Release\n\nA release is a version of your code that is deployed to an environment.\nWhen you give Sentry information about your releases, you unlock a number of new features\:\n- Determine the issues and regressions introduced in a new release\n- Predict which commit caused an issue and who is likely responsible\n- Resolve issues by including the issue number in your commit message\n- Receive email notifications when your code gets deployed
io.quarkus.logging.sentry.SentryConfig.environment=Environment\n\nWith Sentry you can easily filter issues, releases, and user feedback by environment.\nThe environment filter on sentry affects all issue-related metrics like count of users affected, times series graphs,\nand event count.\nBy setting the environment option, an environment tag will be added to each new issue sent to Sentry.\n\nThere are a few restrictions\:\n-> the environment name cannot contain newlines or spaces, cannot be the string “None” or exceed 64 characters.
io.quarkus.logging.sentry.SentryConfig.inAppPackages=Sentry differentiates stack frames that are directly related to your application (“in application”) from stack frames\nthat come from other packages such as the standard library, frameworks, or other dependencies. The difference is visible\nin the Sentry web interface where only the “in application” frames are displayed by default.\n\nYou can configure which package prefixes your application uses with this option.\n\nThis option is highly recommended as it affects stacktrace grouping and display on Sentry. See documentation\:\nhttps\://quarkus.io/guides/logging-sentry\#in-app-packages
io.quarkus.logging.sentry.SentryConfig.dsn=Sentry DSN\n\nThe DSN is the first and most important thing to configure because it tells the SDK where to send events. You can find\nyour project’s DSN in the “Client Keys” section of your “Project Settings” in Sentry.
io.quarkus.logging.sentry.SentryConfig.debug=Debug\n\nEnables Sentry debug mode.
io.quarkus.logging.sentry.SentryConfig.level=The sentry log level.
io.quarkus.logging.sentry.SentryConfig.minimumBreadcrumbLevel=The minimum breadcrumb level.\n\nEvery log statement that is greater than minimum breadcrumb level is added to Sentry scope as a breadcrumb,\nwhich can be later attached to SentryEvent if one is triggered.
io.quarkus.logging.sentry.SentryConfig.serverName=Server name\n\nSets the server name that will be sent with each event.
io.quarkus.logging.sentry.SentryConfig.enable=Determine whether to enable the Sentry logging extension.
io.quarkus.logging.sentry.SentryConfig.minimumEventLevel=The minimum event level.\n\nEvery log statement that is greater than minimum event level is turned into Sentry event.