#Define sentry full
#Define sentry code

Performance - The main view in sentry.io where you can search or browse for transaction data.

#Define sentry full

Learn more in the full Issues documentation. From here, you can go to the Issue Details page for a more granular view of any issue. Issues - Displays information about grouped errors in your application. Learn more in the full Projects documentation. From here, you can go to the Project Details page of each project for a more granular view. Projects - Lists the projects of which you're a member, by team, and provides you with a high-level overview of your projects. There are several types of alerts available with customizable thresholds and integrations.Įach of these key features in sentry.io is represented by a page (or set of pages) in the application.

#Define sentry code

To do this, Sentry captures distributed traces consisting of transactions and spans to measure individual services, as well as operations within those services.Īlerts - Alerts let you know about problems with your code in real-time by sending you notifications when certain alert rule conditions are met. Performance monitoring - Performance monitoring is the act of tracking application performance and measuring metrics such as how many transactions are being sent and the average response time for all occurrences of a given transaction. Learn more in the full release health documentation. Release health - Release health data provides insight into the impact of crashes and bugs as it relates to your user's experience and reveals trends with each new issue. Learn more in the full Releases documentation. When you notify Sentry about a release, you can identify new issues and regressions associated with it, confirm whether an issue is resolved in the next release, and apply source maps.

Release - A release is a version of your code deployed to an environment. Learn more in our full Environments documentation. Environments help you better filter issues and transactions among other uses. Learn more about setting up teams.Įnvironment - environment is a Sentry-supported tag that you can add to your SDK that's intended to refer to your code deployments' naming convention, such as development, testing, staging, or production. Team - Teams are associated with your Sentry projects, and their members receive issue notifications, in addition to becoming issue owners. Learn more in our full DSN documentation. Sentry automatically assigns you a DSN when you create a project. A DSN tells the Sentry SDK where to send events so the events are associated with the correct project. Projects allow you to associate events with a distinct application in your organization and assign responsibility and ownership to specific users and teams within your organization.ĭSN - Data Source Name. For more information, check out our best practices for creating projects. For example, you might have separate projects for your API server and frontend client. You can create a project for a particular language or framework used in your application. Project - A project represents your service or application in Sentry. This includes, events (errors or transactions), attachments, and event metadata. Transaction events are grouped by the transaction name.ĭata - Anything you send to Sentry. Transaction - A transaction represents a single instance of a service being called to support an operation you want to measure or track, like a page load, page navigation, or asynchronous task.

This grouping of events into issues allows you to see how frequently a problem is happening and how many users it's affecting.

For example, Sentry groups events together when they are triggered by the same part of your code. Fingerprint The set of characteristics that define an event., which is what Sentry uses to group them.