My first question is why are you trying to create a new TA for access combined? It is in our “ List of pretrained source types ” that is defined in the file system/default/props.conf Add-On Builder is detecting this and preventing you because of the layering of apps and the rules of Precedence. If config is in a location with a higher precedence, your new TA will not be able to overrule it.
If your data differs from access combined, it should have a different sourcetype name.
If it is the same but you want to add a couple of field extractions you can just create a new app and build those extractions whilst in it.
If you want to normalise it to a data model, (which one/’s?) then it is a little more complex. Best practice is to create new apps on a development system where you can move any existing config to your new app without risking making a mistake in production. Only move to prod when you are happy.
If you have to do this in production, I would :-
First create a new sourcetype I called it ac2
Under advanced delete the category line and replace it with
REPORT-access = access-extractions
Then click next
Upload sample data and continue as normal.
Once you have built your app, edit the app’s props.conf from the command line. Replacing ac2 with access_combined
reboot splunk for it to take effect.
But this takes away most of the advantage of the Add-On Builder being GUI.
... View more