Skip to content

chore(context engine): New RPC endpoint for project instrumentation details#108413

Open
Mihir-Mavalankar wants to merge 4 commits intomasterfrom
rpc-get-organization-projects
Open

chore(context engine): New RPC endpoint for project instrumentation details#108413
Mihir-Mavalankar wants to merge 4 commits intomasterfrom
rpc-get-organization-projects

Conversation

@Mihir-Mavalankar
Copy link
Contributor

PR Details

@Mihir-Mavalankar Mihir-Mavalankar self-assigned this Feb 17, 2026
@Mihir-Mavalankar Mihir-Mavalankar requested a review from a team as a code owner February 17, 2026 23:51
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Feb 17, 2026
Comment on lines +311 to +312
"hasTraceMetrics": get_has_trace_metrics(project),
"hasLogs": get_has_logs(project),
Copy link
Member

Choose a reason for hiding this comment

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

are these two functions performant? thinking of case w/ orgs that have 1000+ projects

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The functions themselves are fast since they just check bit fields like project.flags.has_logs with an if statement but fetching a lot of projects can be problematic.
The rpc above get_organization_project_ids has the same pattern though. Maybe if we see timeouts we can revisit this?

Copy link
Member

@JoshFerge JoshFerge left a comment

Choose a reason for hiding this comment

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

lgtm, only other thought is should we just just pass these in when we initialize the explorer task instead? or will this be conditionally called etc.

@Mihir-Mavalankar
Copy link
Contributor Author

lgtm, only other thought is should we just just pass these in when we initialize the explorer task instead? or will this be conditionally called etc.

That would be preferable but eventually this is going to a daily cron task in Seer that calls this. So it won't be Sentry initializing this task.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants