You can set up a user with the "SELECT ANY DICTIONARY" privilege, which will include access to to the V$ views without granting full DBA privileges. Unfortunately, it will also grant select access to certain dictionary tables that your DBA might not want exposed, like USER$, so no guarantees that this will be allowed. You should also be able to create a custom role with select access to the specific views you want, but this may take a while to fine-tune to the point where you're seeing everything you want.
The other thing to be aware of is that v$ views are extremely volatile - the information in them is constantly changing and is only accurate for the split second that the data is returned. Many database activities, including some entire sessions, are completed in milliseconds, so depending on what your refresh rate on your Splunk input is, you will likely miss a LOT of data, including events that you want to capture. Conversely, if your monitor rate is very fast, you will be collecting a lot of duplicate data on longer-running activities that will not really benefit you much, and will quickly exhaust your Splunk license - and still likely miss a lot of data on activities that you want to capture. A better option is to target specific activities that you want to monitor with general or fine-grained auditing, then Splunk the audit trails for changes. This allows you to focus your attention on the things that matter most, while not sucking up your Splunk license with a lot of data that will ultimately be meaningless.
For a complete step-by-step guide on configuring Splunk for Oracle and the various ways to collect data, including auditing, see the Real-Time Log File Analysis for Oracle 11g add-on.
... View more