Page MenuHomePhabricator

Write Phabricator HTTP and SSH logs in the production cluster
Open, NormalPublic

Description

See discussion in T12605. I want to configure log.access.path and log.ssh.path so we generate meaningful logs in production.

I identified the problem instance and user in T12605 through huge leaps of guesswork which no one who is less experienced could reasonably have been expected to perform, and still got lucky. Configuring these will let anyone plainly read values out of sensible logfiles and skip all this guesswork.

Revisions and Commits

Restricted Differential Revision
Restricted Differential Revision
Restricted Differential Revision
Restricted Differential Revision
Restricted Differential Revision
rPHU libphutil
D17777
rP Phabricator
D17776

Event Timeline

epriestley created this object in space Restricted Space.
epriestley created this object with edit policy "All Users".

I'm going to declassify this too since there's nothing private.

epriestley shifted this object from the Restricted Space space to the S1 Core space.Apr 21 2017, 7:21 PM
epriestley added a revision: Restricted Differential Revision.Apr 23 2017, 2:47 PM
epriestley added a revision: Restricted Differential Revision.Apr 23 2017, 2:57 PM
epriestley added a commit: Restricted Diffusion Commit.Apr 23 2017, 6:27 PM
epriestley added a commit: Restricted Diffusion Commit.Apr 23 2017, 6:34 PM

The Aphlict logs should probably get consolidated here too, they're set up a little weird and don't currently rotate during normal deployments.

Specifically, I'd like to make these changes:

  • Put the Aphlict log in log/ with the same organization as everything else, and have it share the same rotation code. It would currently conflict with a hypothetical instance named aphlict.phaclity.com.
  • Put log volumes on more devices. admin, web and notify-class devices currently serve logged traffic but do not have dedicated log volumes.
    • bin/provision should be aware of these volumes, and ideally should be used to retroactively provision and attach them.
  • Enable the SSH and HTTP application logs on the web, repo and admin tiers.
  • Move Apache logs to log/, so log accumulation is less able to endanger other processes by filling up disks.
  • Probably put them on the same rotation infrastructure as everything else, although logrotate currently interacts here.
  • Put notify in the regular push rotation. It currently gets deployed irregularly.
epriestley added a revision: Restricted Differential Revision.Feb 26 2021, 10:48 PM
epriestley added a revision: Restricted Differential Revision.
epriestley added a commit: Restricted Diffusion Commit.Feb 26 2021, 10:55 PM
epriestley added a commit: Restricted Diffusion Commit.

Enable the SSH and HTTP application logs on the web, repo and admin tiers.

After T13624, these logs are enabled on repo, and the path forward is a little shorter for other tiers.

web and admin don't have log volumes yet.

epriestley added a commit: Restricted Diffusion Commit.Feb 26 2021, 11:10 PM