Skip to content

Conversation

@JoshuaMoelans
Copy link
Member

@JoshuaMoelans JoshuaMoelans commented Dec 2, 2025

Continuing from #102398, to be merged after that one was merged.

We add the logs onboarding for each of the platforms that now support logs.

There is also some additional cleanup & adding of tracing to the Getting Started docs.

ToDo

  • add Unity onboarding
  • double-check that all relevant onboarding docs exist & are correct (I will ping the SDK maintainers)
  • maybe add logs checkbox to project onboarding page for each of these SDKs (see original comment)

@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Dec 2, 2025
@JoshuaMoelans JoshuaMoelans changed the title Joshua/chore/logs onboarding chore: update SDK onboarding pages Dec 2, 2025
- fix link
- add minidump storage setting
@codecov
Copy link

codecov bot commented Dec 2, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #104234      +/-   ##
===========================================
- Coverage   80.60%    80.60%   -0.01%     
===========================================
  Files        9333      9333              
  Lines      398600    398597       -3     
  Branches    25497     25496       -1     
===========================================
- Hits       321275    321272       -3     
  Misses      76875     76875              
  Partials      450       450              

import {StepType} from 'sentry/components/onboarding/gettingStartedDoc/types';
import {t, tct} from 'sentry/locale';

type Params = DocsParams;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can use the DocsParams directly instead of using type Params

onboarding,
feedbackOnboardingCrashApi: crashReport,
crashReportOnboarding: crashReport,
logsOnboarding: logs,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need to add a performanceOnboarding too?

Comment on lines +43 to +49
params.isPerformanceSelected
? `
// Set traces_sample_rate to 1.0 to capture 100% of transactions for tracing.
// We recommend adjusting this value in production.
Settings->TracesSampleRate = 1.0f;`
: ''
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would add tracing in a separate PR

{
type: 'text',
text: tct(
'To enable performance monitoring, set the [code:TracesSampleRate] option in the Sentry configuration window. For example, set it to [code:1.0] to capture 100% of transactions.',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

aren't we calling it tracing?

Comment on lines +307 to +308
'cocoa-objc',
'cocoa-swift',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I noticed that we have several references to these platforms in the codebase, but we don’t present them as options when users create a project. My understanding is that users can also create projects through the public API - Is that why we need to include these platforms here?

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

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants