Page MenuHomePhabricator

Track daemon unique IDs in Phabricator daemon logs
ClosedPublic

Authored by epriestley on Feb 23 2015, 7:28 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Apr 11, 4:35 AM
Unknown Object (File)
Wed, Apr 10, 10:57 PM
Unknown Object (File)
Tue, Apr 9, 9:44 AM
Unknown Object (File)
Fri, Mar 29, 3:57 PM
Unknown Object (File)
Mar 20 2024, 11:21 PM
Unknown Object (File)
Feb 1 2024, 7:05 AM
Unknown Object (File)
Jan 7 2024, 2:20 PM
Unknown Object (File)
Dec 27 2023, 7:33 PM
Subscribers

Details

Summary

Ref T7352. We were previously identifying things by <daemonClass, overseerPID, startTime> but that's not unique in a world where one overseer can run multiple daemons.

We already have an internal "daemonID", it just doesn't get written into the DB right now.

Start writing it, then use it to clean up phd status.

Test Plan

Ran phd status, got more accurate/useful output than previously.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Track daemon unique IDs in Phabricator daemon logs.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: btrahan.
btrahan edited edge metadata.
This revision is now accepted and ready to land.Feb 24 2015, 5:15 PM
This revision was automatically updated to reflect the committed changes.