The restricted-network cutover forces observability completeness against a non-negotiable security boundary.
The customer needs usable Java investigation on day one while security protects an irreversible production route.
Who you’d be doing this for
“If the fraud path fails after cutover, I need the transaction and error together, not a ticket saying telemetry is partial.”
Chiamaka Boateng · Principal Java Engineer
Runs the customer’s fraud-decision services and is accountable for production diagnosis after the network cutover.
What is at stake
A rehearsal shows Java errors arriving inconsistently and some transactions losing service context. You must weigh a customer-operated Relay route against launching with reduced investigation coverage while a network exception is pursued.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- cutover date vs verified telemetry completeness
- security boundary vs investigation access
- automated analysis vs manually verified evidence
- network exception vs reusable operating pattern
Why Sentry
Sentry Relay sits on the ingestion path that customers use when application telemetry must cross constrained environments.
Written with these in mind
Not your kind of problem? 20 more at Sentry, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.