I've created some new thresholds in the vmware app settings, but they only show up for me, other people hit the proactive monitoring page and get errors saying that a threshold is not set for the given value. I've been trying to find where that might be defined so I can fix it, but should this be the desired behavior of the thresholds?
You need to merge the contents of etc/user/username/splunk_for_vmware/sa_threshold.conf with etc/apps/splunk_for_vmware/local/sa_threshold.conf and then remove your etc/user/username/splunk_for_vmware/sa_threshold.conf. I was able to reproduce this behavior by modifying the etc/splunk_for_vmware/local directories permissions to be read-only. Please make sure that your local directory is writable by splunk.
In this case, I navigate here and I have a history, local, and metadata directory, but no conf file at this level.
I definitely did it through the web app. so if I find a thresholds.conf folder in the location you specify, I should be able to move that information to the one under apps/local?
This would imply that some how your threshold.conf got placed in your personal user folder (etc/user/username) instead of the appliaction's /local folder. When you created the threshold, did you do it from the vmware/configration page? Or was it done outside the vmware app?