is `processes` inferfering with debugging filesystem-based issues?

[ignoramous]

@fleex

My new understanding is that, if I have two processes, they don’t share (non-persistent) disk and in fact they can’t see each other at all, which would explain why both my SSH session and the New Relic agent can’t see the log file from Postfix.

Your understanding is right (see).

@fleex

…how would I go about getting Postfix to dump logs into a place where the New Relic agent can tail them?

I haven’t done it, but I imagine:

1. Either running the New Relic agent as another process along side the main process of a regular Fly app (docs, also) (Fly’s multiprocess apps aren’t really meant for sidecars like observability daemons).
2. Or, running a separate Fly app that reads from Fly-managed NATS-based log shipper and feeds it into New Relic (ref announcement, also / see).

@fleex

Secondarily, is there a way I can SSH into a specific process’s, uh, namespace (?) and poke around its disk and process tree?

One can ssh from a running set of app instances (VMs) via fly ssh console -s -a <app-name> (ref).