Skip to content

feat(autopilot): Prepare missing integration detection for experiment#107671

Merged
vgrozdanic merged 1 commit intomasterfrom
vg/experiment-on-integration-detector
Feb 5, 2026
Merged

feat(autopilot): Prepare missing integration detection for experiment#107671
vgrozdanic merged 1 commit intomasterfrom
vg/experiment-on-integration-detector

Conversation

@vgrozdanic
Copy link
Member

@vgrozdanic vgrozdanic commented Feb 5, 2026

Prepares missing sdk integration detector for a shadow run experiement. We are planning to run this on 200 projects to get the feeling how often this could detect a problem in a real world traces and repositories. This will not create real issues as they will not get ingested, but we will use the metrics and logs to learn more about the performance of the detector.

Closes TET-1899: Implement shadow run for 200 pre-selected projects

@vgrozdanic vgrozdanic requested a review from a team as a code owner February 5, 2026 13:29
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Feb 5, 2026
)
metrics.incr(
"autopilot.missing_sdk_integration_detector.issue_created",
tags={"project_id": str(project.id), "integration": integration},
Copy link
Member Author

Choose a reason for hiding this comment

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

this is only temporary and it wouldn't be more than 200 projects and a couple of integration values, so no high cardinality concerns atm.

"""
metrics.incr(
"autopilot.missing_sdk_integration_detector.run",
tags={"project_id": str(project_id)},
Copy link
Member Author

Choose a reason for hiding this comment

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

this is only temporary and it wouldn't be more than 200 projects, so no high cardinality concerns atm.

except Exception as e:
metrics.incr(
"autopilot.missing_sdk_integration_detector.error",
tags={"project_id": str(project.id), "error_type": type(e).__name__},
Copy link
Member Author

Choose a reason for hiding this comment

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

this is only temporary and it wouldn't be more than 200 projects, so no high cardinality concerns atm.

Copy link
Contributor

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

"autopilot.missing_sdk_integration_detector.issue_created",
tags={"project_id": str(project.id), "integration": integration},
sample_rate=1.0,
)
Copy link
Contributor

Choose a reason for hiding this comment

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

Metric emitted before issue creation succeeds

Medium Severity

The "autopilot.missing_sdk_integration_detector.issue_created" metric is emitted before create_instrumentation_issue() is called. If the issue creation fails, the code has already counted it as created, then an error metric is also emitted. This produces misleading metrics for the shadow run experiment — a single failed creation would show both an "issue_created" count and an error count. For an experiment designed to measure real-world performance through metrics and logs, this inaccuracy could skew the analysis.

Fix in Cursor Fix in Web

Copy link
Member Author

Choose a reason for hiding this comment

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

not a problem

@linear
Copy link

linear bot commented Feb 5, 2026

@vgrozdanic vgrozdanic merged commit af1867b into master Feb 5, 2026
96 checks passed
@vgrozdanic vgrozdanic deleted the vg/experiment-on-integration-detector branch February 5, 2026 14:39
jaydgoss pushed a commit that referenced this pull request Feb 12, 2026
…#107671)

Prepares missing sdk integration detector for a shadow run experiement.
We are planning to run this on 200 projects to get the feeling how often
this could detect a problem in a real world traces and repositories.
This will not create real issues as they will not get ingested, but we
will use the metrics and logs to learn more about the performance of the
detector.

Closes [TET-1899: Implement shadow run for 200 pre-selected
projects](https://linear.app/getsentry/issue/TET-1899/implement-shadow-run-for-200-pre-selected-projects)
dcramer pushed a commit that referenced this pull request Feb 17, 2026
…#107671)

Prepares missing sdk integration detector for a shadow run experiement.
We are planning to run this on 200 projects to get the feeling how often
this could detect a problem in a real world traces and repositories.
This will not create real issues as they will not get ingested, but we
will use the metrics and logs to learn more about the performance of the
detector.

Closes [TET-1899: Implement shadow run for 200 pre-selected
projects](https://linear.app/getsentry/issue/TET-1899/implement-shadow-run-for-200-pre-selected-projects)
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.

2 participants