I was referring to deployment apps that a deployment server can provide to universal forwarders, and their corresponding server classes.
In a multiple cluster scenario, for outputs, it makes sense to create an app's outputs.conf file to match each indexer group.
With inputs things get more complex. We don't get to know how our customers are using the indexes they ask us to set up for them. Our role is to provide the support when stuff breaks. But it would be nice to provide a one-time on-boarding experience for them and have a deployment server maintain their configurations going forward.
The question then becomes, what's a logical way to organize deployment apps that have inputs.conf? Does one exist? At this point I don't think so. Unless there's a way implement a standard location for our users to send their log files on their machines, and stuff like that.
I'm not sure there's a "standard" way to organize deployment apps. There is a naming convention for apps, but I think that's not what you mean. While there are some common inputs you can give to all customers (Windows event log, Linux logs, etc.), most will be custom for the client. That's especially true for client names in the deployment server. I've yet to see two customers use the same naming scheme for their servers so DS client names are never routine.
--- If this reply helps you, an upvote would be appreciated.