Sentry
Are exports failing, or waiting? What do this morning’s traces show?
TRACKERS & MCP
GenieWorks lives in Jira, GitLab, or GitHub
Your team’s decisions and live evidence stay together on the issue. GenieWorks investigates through the compatible connections your project authorizes.
Follow the work01 · ASK THE SYSTEM FOR FACTS
The repository cannot show today’s customer state
The source explains how export limits work. It cannot reveal Northstar’s current queue, active setting, or commercial entitlement.
GenieWorks uses selected Sentry and Internal Operations MCP connections to bring those facts into the investigation before recommending a change.
Your internal service
What limit is active for Northstar, and what does the customer’s plan allow?
Compatible, authorized MCP connections selected for this project
02 · KEEP EVIDENCE IN THE SHARED HISTORY
The next teammate can follow the reasoning
Alex’s assignment, the tool questions, and the returned evidence remain part of the same work. A teammate with access can see what was checked and why the recommendation changed.
The investigation finds a configuration mismatch. It does not infer a worker defect simply because the ticket says exports are slow.
Northstar · Issue comments & history
Assigned to GenieWorks · Investigate slow exports for Northstar
Sentry: show this morning’s slow-export traces for Northstar.
Six exports queued for 18–24 minutes. No worker errors in the retrieved traces.
Internal Operations: compare Northstar’s active export limit with its entitlement.
Active limit: 1 export. Enterprise entitlement: 4. No intentional customer override recorded.
The active limit does not match the entitlement. Trace how it was set, then specify the correction and a regression check. The investigation has not changed production settings.
03 · MAKE THE NEXT STEP EXPLAINABLE
A mismatch to investigate
A reason to investigate it
The source of each fact stays explicit. Queue delay and a limit mismatch support the next investigation; the retrieved traces alone do not prove there are no worker defects anywhere.
6 exports waiting
18–24 minute queue delays; no worker errors in the retrieved traces.
1 active / 4 entitled
The live customer setting differs from its plan. No intentional override is recorded.
Trace the setting’s origin
Establish the cause, agree the correction, and verify behavior against the entitlement.
04 · MAKE IT PART OF THE TEAM’S WORK
Your tracker is already the shared workspace
Keep conversations, agreed decisions, and handoffs where teammates can find them. Connect compatible observability and internal services for the evidence the repository cannot supply.
Jira
GitLab
GitHub IssuesUse the project’s authorized MCP connections, including your custom/internal services.
CONTINUE THE WORK
Carry the evidence into an agreement
See how an investigation becomes a bounded specification the team can review and implement.