coilyco-gaming/eco-app
2
0
Fork 0
Code Issues 16 Pull requests Projects Releases Packages Wiki Activity Actions

Restore a valid SENTRY_DSN in SSM (Sentry currently disabled in prod) #44

New issue
Open
opened 2026-07-03 21:18:35 +00:00 by coilyco-ops · 0 comments
coilyco-ops commented 2026-07-03 21:18:35 +00:00
Member
Copy link

Context

Follow-up to eco-app#43. The prod crash-loop was hardened away (a malformed DSN now log-and-skips), and eco-app is live again on the current image. But the root-cause misconfig is still present: /sentry-dsn/eco-mcp-app in AWS SSM holds a malformed value (64 bytes, no https:// scheme), last modified 2026-06-23.

Consequence: Sentry is silently disabled in production right now. The app boots fine and logs a warning (SENTRY_DSN is set but invalid; continuing without Sentry) on every start, but no errors are being captured.

Ask

Put the correct Sentry DSN back into SSM (SecureString), then restart the deployment so the running pod picks it up:

ward ops aws ssm put-parameter --name /sentry-dsn/eco-mcp-app --type SecureString --overwrite --value '<the real https://...@...ingest.sentry.io/... DSN>'
ward ops kubectl -- rollout restart deploy/coilysiren-eco-app-app -n coilysiren-eco-app

A valid DSN looks like https://<key>@o<org>.ingest.sentry.io/<projid>. Needs the real value, which only Kai has - not an agent action.

## Context Follow-up to eco-app#43. The prod crash-loop was hardened away (a malformed DSN now log-and-skips), and eco-app is live again on the current image. But the root-cause misconfig is still present: `/sentry-dsn/eco-mcp-app` in AWS SSM holds a malformed value (64 bytes, no `https://` scheme), last modified 2026-06-23. **Consequence:** Sentry is silently **disabled** in production right now. The app boots fine and logs a warning (`SENTRY_DSN is set but invalid; continuing without Sentry`) on every start, but no errors are being captured. ## Ask Put the correct Sentry DSN back into SSM (SecureString), then restart the deployment so the running pod picks it up: ``` ward ops aws ssm put-parameter --name /sentry-dsn/eco-mcp-app --type SecureString --overwrite --value '<the real https://...@...ingest.sentry.io/... DSN>' ward ops kubectl -- rollout restart deploy/coilysiren-eco-app-app -n coilysiren-eco-app ``` A valid DSN looks like `https://<key>@o<org>.ingest.sentry.io/<projid>`. Needs the real value, which only Kai has - not an agent action.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
issue-109
issue-106
ward-salvage/eco-app-a58b14ad
issue-104
No results found.
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
headless
Safe for autonomous warded engineer carry

  
consult
'A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
priority tier

  
P1
priority tier

  
P2
priority tier

  
P3
priority tier

  
P4
priority tier

No labels
burndown-2026-06
headless
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-gaming/eco-app#44
No description provided.