Skip to content

Add support for trace beginning at session start#9735

Draft
MaesterChestnut wants to merge 2 commits intocrashlytics-tracingfrom
crashTraceCrashLinkResearch
Draft

Add support for trace beginning at session start#9735
MaesterChestnut wants to merge 2 commits intocrashlytics-tracingfrom
crashTraceCrashLinkResearch

Conversation

@MaesterChestnut
Copy link

No description provided.

@changeset-bot
Copy link

changeset-bot bot commented Mar 19, 2026

⚠️ No Changeset found

Latest commit: 32ab88f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances Crashlytics' error reporting capabilities by deeply integrating OpenTelemetry tracing with user sessions. The changes ensure that all errors and related activities are consistently linked to a session-specific trace, providing a clearer and more comprehensive view of user interactions and potential issues from the moment a session begins. This improves the context available for debugging and understanding the user journey leading up to an error.

Highlights

  • Session-level Tracing Integration: Introduced a custom SessionContextManager and SessionSpanProcessor to ensure that a dedicated trace is started at the beginning of each Crashlytics session. This session trace is automatically associated with all subsequent spans if no other active trace is present, and session IDs are automatically added to all spans.
  • Enhanced Error Reporting: Modified the recordError function to leverage the active session trace. If an error occurs and no other trace is active, it will now be logged within the context of the session's trace, providing better correlation for error analysis.
  • Session Lifecycle Management: Implemented logic to explicitly start a 'session-start' span when a new Crashlytics session is initiated and to properly end this span when the page becomes hidden or is unloaded, ensuring complete session trace lifecycles.
  • Dependency Updates and Refactoring: Updated OpenTelemetry dependencies, including the addition of @opentelemetry/context-zone and removal of @opentelemetry/instrumentation-user-interaction. The getSessionId logic was refactored into its own module for better organization.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assist
Copy link
Contributor

Warning

Gemini is experiencing higher than usual traffic and was unable to create the review. Please try again in a few hours by commenting /gemini review.

@MaesterChestnut MaesterChestnut force-pushed the crashTraceCrashLinkResearch branch from 0475259 to dfb3cad Compare March 19, 2026 18:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant