Why doesn't outputs.conf get migrated from 3.4.x->4.0.x?

[oreoshake]

We're upgrading our forwarders and we always get the warning that outputs.conf cannot be migrated. However, simply moving the file to etc/apps/search/local seems to do the trick. Is there a reason that outputs.conf doesn't get migrated?

It looks like the file that is created by running splunk add forward-server creates a file that is exactly the same. Perhaps it has to do with the app structure?

[jrodman · Accepted solution]

I believe there were some cases that were too complex to safely automatically handle, and the work was not scheduled. In common situations, the format is identical, as you point out.

Outputs.conf is indeed a global configuration still, so the app space it lives in is not really essential.