Introduction
The realm of error tracking and monitoring is intricate. Gain clarity effortlessly with our Sentry Glossary.
Understand pivotal terms in error tracking, monitoring, and performance optimization. Elevate your comprehension of Sentry while effortlessly enhancing your knowledge of error tracking systems.
Sentry Terms
A
Alerts: Alerts provide real-time notifications regarding code issues by alerting you when specific rule conditions are satisfied. Various types of alerts are accessible, featuring customizable thresholds and integrations for enhanced flexibility.
Attachments: Additional files stored, such as configuration or log files, that pertain to an error occurrence.
D
Data: Everything you transmit to Sentry, encompassing events (errors or transactions), attachments, and event metadata.
Dashboards: Offering a comprehensive insight into your application's well-being, enabling you to explore error and performance data across various projects. Dashboards consist of multiple widgets, each visualizing Discover or Issues queries.
Discover: Enables you to query events across different environments, granting visibility into errors and transactions while revealing insights into the overall system health. The Discover page presents the query results visually.
DSN: Data Source Name (DSN) is a crucial identifier that directs the Sentry SDK to the appropriate destination for events, ensuring they are linked to the correct project. Upon project creation, Sentry automatically assigns a DSN to you.
E
Environment: The environment is a Sentry-supported tag that you can incorporate into your SDK, intended to align with your code deployment naming conventions, such as development, testing, staging, or production. Environments enable more effective filtering of issues and transactions, among other use cases.
Error: The definition of an error varies across platforms, but generally, if there's an occurrence resembling an exception, it can be captured as an error in Sentry. Sentry automatically records errors, uncaught exceptions, unhandled rejections, and other types of errors, depending on the specific platform.
Event: Refers to a single instance of error data or other information that is sent to the Sentry for monitoring and analysis purposes.
I
Issues: An issue represents a collection of comparable errors or performance issues. Each event possesses a unique set of attributes known as its fingerprint, which Sentry utilizes for grouping purposes. For instance, Sentry consolidates error events that originate from the same code segment. This categorization of events into issues enables you to monitor the frequency and impact of a particular problem on users.
P
Performance Monitoring: Performance monitoring involves tracking application performance and measuring key metrics, such as the volume of transactions and the average response time across all occurrences of a given transaction. To achieve this, Sentry captures distributed traces comprising transactions and spans, allowing for the measurement of individual services as well as the operations within those services.
Project: A project in Sentry represents a specific service or application. You can create a project for a particular language or framework used within your application. For instance, you might have separate projects for your API server and frontend client. Projects enable you to associate events with a distinct application in your organization and assign responsibility and ownership to specific users and teams.
R
Release: A release in Sentry refers to a specific version of your code that has been deployed to an environment. By informing Sentry about a release, you can pinpoint new issues and regressions linked to it, verify if an issue is resolved in the subsequent release, and implement source maps.
Release Health: Release health data offers insights into the impact of crashes and bugs on the user experience, and reveals trends associated with each new issue.
S
sentry.io: Sentry's user interface, where event data captured by the SDK is visualized, is accessible to SaaS customers. For self-hosted users, the user interface resides on an internal domain within their company.
Sentry SDKs: Sentry's language or framework-specific libraries are utilized for application monitoring. By integrating one of our SDKs into your application, event data is captured and transmitted to Sentry, enabling us to furnish you with error and performance reports.
T
Team: Teams are associated with Sentry projects, and their members collectively receive notifications regarding issues.
Transaction: A transaction signifies a singular occurrence of a service being invoked to facilitate a specific operation you aim to measure or monitor, such as a page load, navigation, or asynchronous task. Transaction events are categorized based on the transaction name.