https://community.splunk.com/t5/Getting-Data-In/is-it-safe-for-app-developers-to-use-pulldown-type-true-on-their/m-p/52067#M10000 <P>props.conf has a boolean setting called "pulldown_type".<BR /><BR /> If you set it to true, then the name of your sourcetype will appear in the end-users' sourcetype dropdowns in manager. <BR /> For app developers, who are often defining their own custom sourcetypes as a part of their shipping app, this key is obviously quite nice for their end users. </P> <P>In the documentation however, pulldown_type is listed under "internal fields", with a note saying "Not yours - do not set". </P> <P>My question is -- is there some hidden pitfall to setting that key? Is that warning really warranted? If not I'm going to start setting it to true in all my apps that define one or more custom sourcetypes. </P> Mon, 16 Jan 2012 19:04:34 GMT sideview 2012-01-16T19:04:34Z https://community.splunk.com/t5/Getting-Data-In/is-it-safe-for-app-developers-to-use-pulldown-type-true-on-their/m-p/52067#M10000 <P>props.conf has a boolean setting called "pulldown_type".<BR /><BR /> If you set it to true, then the name of your sourcetype will appear in the end-users' sourcetype dropdowns in manager. <BR /> For app developers, who are often defining their own custom sourcetypes as a part of their shipping app, this key is obviously quite nice for their end users. </P> <P>In the documentation however, pulldown_type is listed under "internal fields", with a note saying "Not yours - do not set". </P> <P>My question is -- is there some hidden pitfall to setting that key? Is that warning really warranted? If not I'm going to start setting it to true in all my apps that define one or more custom sourcetypes. </P> Mon, 16 Jan 2012 19:04:34 GMT https://community.splunk.com/t5/Getting-Data-In/is-it-safe-for-app-developers-to-use-pulldown-type-true-on-their/m-p/52067#M10000 sideview 2012-01-16T19:04:34Z https://community.splunk.com/t5/Getting-Data-In/is-it-safe-for-app-developers-to-use-pulldown-type-true-on-their/m-p/52068#M10001 <P>Interestingly enough, Splunk 4.3 sets this value when creating new sourcetypes as part of the initial setup 'Add data' screens and choosing "Set a new sourcetype". Certainly that would seem to imply that the warning isn't warranted, but it would be nice to see confirmation and some insight into the original reason for the warning.</P> Tue, 17 Jan 2012 04:24:47 GMT https://community.splunk.com/t5/Getting-Data-In/is-it-safe-for-app-developers-to-use-pulldown-type-true-on-their/m-p/52068#M10001 southeringtonp 2012-01-17T04:24:47Z https://community.splunk.com/t5/Getting-Data-In/is-it-safe-for-app-developers-to-use-pulldown-type-true-on-their/m-p/52069#M10002 <P>I'd set it to true, and also set the new <CODE>description</CODE> and <CODE>category</CODE> fields.</P> Fri, 27 Feb 2015 10:43:47 GMT https://community.splunk.com/t5/Getting-Data-In/is-it-safe-for-app-developers-to-use-pulldown-type-true-on-their/m-p/52069#M10002 dart 2015-02-27T10:43:47Z