# Releases Releases in Real User Monitoring give you a release-centric view of how each deployment behaves in front of real users. Every release appears as its own row with the health metrics that drive your roll-forward / roll-back decision: adoption, crash free rate, crashes, and error templates. Use Releases to confirm that a new deployment is healthy, catch a regression before it spreads to your whole user base, and decide with confidence whether to continue or roll back a deployment. ## What you need Upload source maps for your releases. Source maps give Coralogix full context for a release, including its release date. Without them, the release still appears in the table (built from log events for the selected time range), but the Released column stays empty. See [Source maps](https://coralogix.com/docs/user-guides/rum/sdk-features/source-maps/index.md). ## See every release at a glance Go to **RUM**, then **Releases**. Each release appears as its own row in a flat table, sorted with the newest release first. There is no nesting or expanding—every release is visible at a glance. The Releases page lists every release as its own row with adoption, crash free rate, crashes, and error templates. Each row shows: | Column | Description | | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Release | The release name with its application name, type icon, and a source map indicator. A Latest or Previous badge marks the two most recent releases. Select the source map icon to open the source map catalog—a searchable list of every file uploaded for the release. | | Released | The release date, available only for releases that have [source maps](https://coralogix.com/docs/user-guides/rum/sdk-features/source-maps/index.md). Releases without source maps still appear in the table—based on the events in your logs for the selected time range—but without a release date. | | Adoption | The share of sessions or users on this release compared to the total for the application, with a small chart of activity over the selected period. Until enough users reach the release, the other metrics in this row are noisy. | | Crash free rate | The percentage of sessions or users with no crash, with a color-coded severity indicator. A drop versus the previous release is the clearest regression signal. | | Crashes | The number of crash events recorded for the release. Rising counts versus the previous release are your earliest roll-back signal. Select it to view the crashes in [Error tracking](https://coralogix.com/docs/user-guides/rum/product-features/error-tracking/index.md). | | Error templates | The number of distinct error templates seen in the release, highlighted when greater than zero. An error template groups similar errors, so a repeated error counts once rather than as many separate events. Any nonzero count is worth investigating; the highlight is your cue. Select it to view them in [Error templates](https://coralogix.com/docs/user-guides/rum/product-features/error-template-view/index.md). | Note MFE releases show crashes and error templates only. ## After a deploy When you ship, work the page top-down: 1. Open Releases. The newest row is your release; the previous release carries the Previous badge. 1. Compare the new row's Crash free rate and Crashes against the Previous row. 1. If either has regressed, select the new row to open the drilldown. 1. In Top errors, find the new or spiking error template, then select the row to investigate in Error tracking. 1. Decide: roll forward with a fix, or roll back. ## Narrow to the releases that matter A high-traffic application can produce thousands of releases. Focus on the releases that matter—by environment, application, or release name—and change how their health is calculated: - **Select environment** — filter the data to one or more environments, such as production or staging. Releases with no data in the selected environment still appear, with empty values. - **Select MFE app** — focus on a specific micro frontend (MFE) application. - **Sessions / users** — show Adoption and Crash free rate by sessions or by users. - **Search releases** — find a release by name. Switches Adoption and Crash free rate between session-based and user-based calculation. ## Diagnose a single release Select any release row to open a panel with the full health picture for that release. The panel adapts to the application type—browser, mobile, or MFE. ### Release info Tells you which release the panel describes and the scope (environment + time range) the rest of the panel applies to. The header shows the release name, application name and type badge, a source map badge that opens the source map catalog, an environment selector, and a time range picker. ### Query bar Use this when the row-level numbers look fine but you suspect a specific subset of traffic has regressed. Enter a Lucene query to filter all the data in the panel. The health chart, top errors, and performance cards update to reflect only the matching data—for example, narrow to a single browser to see this release's health for Edge users only. ### Health Use this chart to answer: is this release performing worse than the baseline of every other release? A time-series chart that overlays **This release** against **Other releases**, so a regression in the new release stands out against the baseline of every other release. For browser and mobile applications, switch the chart between crash free session rate, session count, and crash free user rate. Each mode shows the value for this release alongside the change versus other releases, colored green for an improvement and red for a regression. For MFE applications, the chart shows error count over time. Compares this release's crash free session rate against the baseline of all other releases over the selected period. ### Top errors Use this list to find what's actually crashing in this release. The most frequent error templates in this release, with the error count and affected users for each, and when the error was first and last seen. Select a row to open the error in the [Error tracking](https://coralogix.com/docs/user-guides/rum/product-features/error-tracking/index.md) drilldown. ### Performance cards Use these to answer: is this release fast enough for real users, and if not, which metric regressed? For browser applications, a row of [Web Vitals](https://coralogix.com/docs/user-guides/rum/product-features/core-web-vitals/index.md) cards: Largest Contentful Paint (LCP), Interaction to Next Paint (INP), Cumulative Layout Shift (CLS), and First Contentful Paint (FCP). Each card shows the 75th percentile (p75) value for the release, rates it against its threshold, and shows the change versus all releases. For mobile applications, a row of mobile performance cards: cold and warm app start time, slow frames, and frozen frames. Rates LCP, INP, CLS, and FCP for this release and shows each metric's change versus all releases. ## Permissions | Permission | Description | | ------------------------------------------------------------------------------------------------------------- | ------------------------------------- | | [`RUM:VIEW`](https://coralogix.com/docs/user-guides/aaa/access-control/permissions/permissions-list/index.md) | View Releases and all other RUM data. |