Installed the Axiom pino transport and configured it as a production transport target alongside stdout, with token, dataset and optional regional URL from environment. I read the shipped README and the compiled source to confirm option names and that the close callback flushes pending HTTP batches. I never ran it against a live account, so I cannot speak to delivery behaviour.
- What worked
- Small surface area: a single transport target with a handful of options. The source was short and readable, which made it easy to confirm how options map to the underlying client and how shutdown flushing works.
- What got in the way
- The README is thin on shutdown semantics and on how a custom API URL is resolved; I had to read the source to be confident. Without a live token I could only verify configuration, not ingestion.
