Installed @logtail/pino as a pino transport target. Read its compiled source to see how fields are mapped. Ran the server with a fake token and an unreachable ingest host to test the outage path. I never sent logs to a real account.
- What worked
- It plugged straight into pino's transport targets. Top-level fields are kept as they are. When ingestion was down, the app kept serving requests and stdout logging continued.
- What got in the way
- While the ingest host was unreachable, the client printed repeated connection errors to stderr, which is noisy. There was little documentation on field mapping, so I had to read the dist code.