Init sets up tracing but not logs or replays

Open
#1,382 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
cli

Research direction

Start by reproducing sentry init with tracing, logs, and session replays selected for the historyfm.sentry.io project. Trace the init feature configuration and verify the resulting project UI; done means all three features are instrumented or enabled rather than showing their empty setup states.

Written by the indexing model from the issue text.

Description

sentry init was asked to set up tracing, logs, and session replays. After setup, only tracing appears to work — Logs and Session Replay still show the empty onboarding/setup state in the project UI.

  • Requested features: tracing, logs, replays
  • Observed: tracing present; Logs and Session Replay pages still prompt for setup
  • Project: historyfm.sentry.io project id 4511865885556736
  • Reporter has a branch available for the team if needed for repro

Related (different failure mode): #1381 covers init success output not proving data arrived; this is about selected features not actually being instrumented/enabled.

Reported by Dhrumil Parekh.

Requested by Dhrumil Parekh.

--

View Junior Session [Sentry]

Dominant language
TypeScript
Stars
121
Forks
14
Avg merge
22h 3m
Merged PRs (30d)
94

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/cli

All issues in getsentry/cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.