Closed Bug 1454119 Opened 7 years ago Closed 6 years ago

Set SENTRY_NAME to a useful value in each pod

Categories

(Taskcluster :: Services, enhancement, P5)

Product:
Taskcluster
Component:
Services
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: dustin, Assigned: bstack)

References

Details

This will appear in the `server` field of Sentry. It will be useful to know at least the name of the ReplicaSet, but the name of the specific Pod might also be useful (for example, when a Pod "goes bad")
Assignee: nobody → bstack
I think we'll be using structured logging instead.. can we close?
Component: Redeployability → Services
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.