Sentry integration

[akolesen]

Summary by CodeRabbit

• New Features
  • Integrated Sentry for enhanced error tracking and diagnostics.
• Chores
  • Updated testing dependencies for improved reliability.
• Documentation
  • Added Sentry configuration details for source code integration.

[coderabbitai]

Walkthrough

The updates primarily focus on integrating Sentry for enhanced error tracking and debugging capabilities within the application. This includes adding the Sentry plugin, configuring it to enrich error reporting with source context, and ensuring source code is uploaded for better insight. Additionally, minor updates were made to the testing dependencies, alongside a crucial import statement for Sentry in the main application class to kickstart its functionality.

Changes

File(s)	Summary
build.gradle	Integrated io.sentry.jvm.gradle plugin, configured Sentry, and updated testing dependencies.
src/main/java/io/kontur/disasterninja/DisasterNinjaApplication.java	Added import for io.sentry.Sentry.

🐇✨
In the code's deep burrow, under digital skies,
A rabbit hops, where the Sentry lies.
With each leap and bound, errors it spies,
Catching bugs, under the coder's wise eyes.
🌟 In this digital field, where our code flies,
Together, we ensure it gracefully thrives.
🐾💻

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 1

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between dd73252 and 38355fa.

Files ignored due to path filters (1)

• src/main/resources/application.yml is excluded by: !**/*.yml

Files selected for processing (2)

• build.gradle (3 hunks)
• src/main/java/io/kontur/disasterninja/DisasterNinjaApplication.java (1 hunks)

Additional comments: 3

src/main/java/io/kontur/disasterninja/DisasterNinjaApplication.java (1)

• 3-3: The addition of the io.sentry.Sentry import statement aligns with the PR's objective of integrating Sentry for error tracking and performance monitoring. Ensure that Sentry is properly initialized and used where necessary in the application to fully leverage its capabilities.

build.gradle (2)

• 8-8: The addition of the Sentry JVM Gradle plugin (version 4.3.0) is correctly implemented. This plugin is essential for enabling Sentry's error tracking and performance monitoring capabilities within the JVM environment of the project.
• 74-84: The tasks configured for Sentry source code integration are set up to ensure they run in the correct order relative to the Apollo source generation tasks. This setup is crucial for ensuring that Sentry's source code integration does not interfere with or is negatively impacted by other build processes. Good job ensuring that these dependencies are correctly managed.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between dd73252 and 9b87f89.

Files ignored due to path filters (1)

• src/main/resources/application.yml is excluded by: !**/*.yml

Files selected for processing (2)

• build.gradle (3 hunks)
• src/main/java/io/kontur/disasterninja/DisasterNinjaApplication.java (1 hunks)

Files skipped from review as they are similar to previous changes (2)

• build.gradle
• src/main/java/io/kontur/disasterninja/DisasterNinjaApplication.java