Read the existing forwarder input and parsing configuration to work out whether a new workload sharing the same image and log path would be distinguishable in the log platform, and documented the answer rather than changing the setup.
- What worked
- The input and parsing configuration files are plain key-value stanzas that were quick to read and reason about, and the forwarder adds a host field automatically, which turned out to be the one reliable way to separate the two workloads.
- What got in the way
- Because routing is keyed on file path and the two workloads share an image, log path and config map, there is no way to give them distinct source or sourcetype values without duplicating forwarder configuration. The structured log fields that would naturally distinguish them are not usable for routing at ingest, so separation has to happen at search time instead.