Skip to content

prototype(logs): Add row pinning to logs explorer#114922

Draft
marthalyndon wants to merge 1 commit intomasterfrom
martha-peck/feat/ourlogs-row-pinning
Draft

prototype(logs): Add row pinning to logs explorer#114922
marthalyndon wants to merge 1 commit intomasterfrom
martha-peck/feat/ourlogs-row-pinning

Conversation

@marthalyndon
Copy link
Copy Markdown
Contributor

[POC prototype from Design]

Add the ability to pin log rows in the logs explorer table. Pinned rows appear in a collapsible section at the top of the table while remaining visible in the chronological list. Hovering any copy highlights all instances via a shared hover context. Pins persist in the URL for shareability.

Key implementation details:

  • New organizations:ourlogs-pinning feature flag
  • Context-based state with URL sync via replaceState (avoids React Router re-renders)
  • Pinned/chronological rows use independent expand keys so expanding one copy doesn't expand the other
  • Pin button appears on row hover next to the existing ellipsis menu
  • "Clear all" button and collapse/expand toggle in the pinned section divider

Add the ability to pin log rows in the logs explorer table. Pinned rows
appear in a collapsible section at the top of the table while remaining
visible in the chronological list. Hovering any copy highlights all
instances via a shared hover context. Pins persist in the URL for
shareability.

Key implementation details:
- New `organizations:ourlogs-pinning` feature flag
- Context-based state with URL sync via replaceState (avoids React
  Router re-renders)
- Pinned/chronological rows use independent expand keys so expanding
  one copy doesn't expand the other
- Pin button appears on row hover next to the existing ellipsis menu
- "Clear all" button and collapse/expand toggle in the pinned section
  divider
@github-actions github-actions Bot added Scope: Frontend Automatically applied to PRs that change frontend components Scope: Backend Automatically applied to PRs that change backend components labels May 5, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 5, 2026

🚨 Warning: This pull request contains Frontend and Backend changes!

It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently.

Have questions? Please ask in the #discuss-dev-infra channel.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 5, 2026

📊 Type Coverage Diff

✅ No new type safety issues introduced. Coverage: 93.40%

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant