I want to get more than 10000 results and after reading some answers about the limits in the email and I realized that if I bump from 10000 to 500000 results I will have a huge file that I will not be able to send by email. So I started to attack this. My first thought was to directly send with a custom alert action. A ptyhon script that emails the results_file through as is easy accessible by the results_file payload but this gives me raw results that I will have to parse (how?). The other alternative is to modify the default email script for my specific app. Any advice ? Is strange that the default email action only sends plain csv files and not give the option of compressing it. ... View more

I can create a new lookup with the admin user and thus create a new collection. When I try to use another user which has permissions to write to the app I get a "You do not have permission to make a KV store collection" message. I just tried to add rest_get and rest_set capabilities but does not work. Update: I've been performing some tests. When you create the lookup from the admin user it creates the collection under $SPLUNK_HOME/etc/apps/appsname/local/collections.conf and under the local.meta it sets the owner to admin user. I have not seen how to change the owner through the UI, so this collection is not usable by any user othen than admin. The api is more specific and tells you need the admin_all_objects capability (aka an admin user) $ curl -k -u poweruser:password -d name=mycollection https://localhost:8089/servicesNS/nobody/myapp/storage/collections/config <?xml version="1.0" encoding="UTF-8"?> <response> <messages> <msg type="ERROR">You (user=poweruser) do not have permission to perform this operation (requires capability: admin_all_objects).</msg> </messages> </response> What's the point to create a collection from the UI if only admin user can use it and you need to modify the files directly to change this behaviour? ... View more