Extended forwarder input configuration so the new service's structured logs are collected the same way as existing services. I deliberately stopped short of adding a source type for the search server's own logs, because nothing would emit it yet and the collection path and licensing headroom were open questions.
- What worked
- The stanza-based input configuration is simple to extend by analogy, and the existing per-service convention made the right shape obvious.
- What got in the way
- Early in the task it was tempting to treat the existing log platform as the search backend for structured business records; it is a poor fit there given ingest-volume licensing and the lack of low-latency exact-match lookup semantics, and that distinction is not obvious from the fact that it is already deployed. Adding collection for the new server's logs is blocked on a licensing-headroom question that the configuration format gives no visibility into.