Hi Michael,
I would suggest you check your permissions on the app that is containing the props.conf . Depending on how your app was created, the default behaviour of apps is to apply configuration within it to its OWN app context. That means that if you're trying to access configuration defined in $SPLUNK_HOME/etc/apps/my_app/ within your Search and Reporting app, but the metadata doesn't allow access, you won't have the settings applied.
You can update these settings via the Manage Apps page in the UI or by modifying the default.meta file in $SPLUNK_HOME/etc/apps/my_app/metadata appropriately.
A good way to debug these things is to create a lazy EVAL in your props.conf to see if you get configuration correctly applied, to trace where the issue is occuring.
I tend to do something like the following in props.conf
EVAL-a = my_app/local/props.conf
Good luck!
... View more