Release Health: Note on session and session replay (#11212)

* Release Health: Note on session and session replay * Update docs/product/releases/health/index.mdx Co-authored-by: Liza Mock <[email protected]> --------- Co-authored-by: Liza Mock <[email protected]>
getsentry · Sep 11, 2024 · c3f7a15 · c3f7a15
1 parent cd7ad49
commit c3f7a15
Showing 1 changed file with 6 additions and 0 deletions.
diff --git a/docs/product/releases/health/index.mdx b/docs/product/releases/health/index.mdx
@@ -4,6 +4,12 @@ sidebar_order: 50
 description: "Monitor the health of releases by observing user adoption, usage of the application, percentage of crashes, and session data."
 ---
 
+<Note>
+
+Note, that Sessions (as described below) are not the same as a [Session Replay](/product/explore/session-replay/), (a video-like reproduction of the user's session). We don't bill for release health sessions.
+
+</Note>
+
 You can monitor the health of releases by observing user adoption, usage of your application, percentage of [crashes](#crashes), and [session data](#sessions). Release health data provides insight into the impact of crashes and bugs related to user experience and reveals trends with each new issue through the release details, graphs, and filters. This data is primarily displayed on the [Releases](/product/releases/) and [Release Details](/product/releases/release-details) pages, but is also reflected in other parts of [sentry.io](https://sentry.io).
 
 > Many SDKs automatically manage the start and end of [sessions](#sessions) when the SDK is initialized, but release health configuration is key to ensuring you're receiving useful data, so check out our information on [which SDKs support release health](/product/releases/setup/#release-health) for links to configuring the SDK, as needed.