Closed Bug 1451999 Opened 7 years ago Closed 6 years ago

Figure out plan for sentry in a r14y world

Categories

(Taskcluster :: Services, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: bstack, Assigned: bstack)

References

Details

Do we require people to set up a sentry account or do we build sentry instances into our clusters optionally or... what do?
Assignee: nobody → bstack
I think we just set MONITORING = false now?
We have a short-term and probably long-term plan for this, says brian :)
In my cluster, I'm seeing lots of whining about being unable to connect to sentry. Failed to get access to sentry, err: Error: Invalid token at Client.<anonymous> (/app/node_modules/sentry-api/lib/client.js:151:19) at Request.self.callback (/app/node_modules/request/request.js:186:22) at emitTwo (events.js:126:13) at Request.emit (events.js:214:7) at Request.<anonymous> (/app/node_modules/request/request.js:1163:10) at emitOne (events.js:116:13) at Request.emit (events.js:211:7) at IncomingMessage.<anonymous> (/app/node_modules/request/request.js:1085:12) at Object.onceWrapper (events.js:313:30) at emitNone (events.js:111:20) at IncomingMessage.emit (events.js:208:7) at endReadableNT (_stream_readable.js:1064:12) at _combinedTickCallback (internal/process/next_tick.js:139:11) at process._tickDomainCallback (internal/process/next_tick.js:219:9), jsoN: {} Brian, can you remind me what the plans are here? I can work on them..
Component: Redeployability → Services

This is obviated by structured logging

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.