@BPry Yes, the scripting solution works. The criticism that PaloAlto must accept is really about this "Domain" report. At least in my environment (we log EVERYTHING) I have almost 0 urls like www.amazon.com, www.google.com, www.paloaltonetworks.com and so on. In every log there is something after the domain like www.amazon.com/anything/anything/somefile.html. so when you want to create a script you need to split the URL at the first "/" to get the domain and then count these entries to get the hits to a particular domain. Other solutions/vendors do this out of the box (which actually shouldn't be really hard for paloalto to implement)... In addition with other solutions it is also possible to get a report with the amount of traffic to specific domains, which is also not possible with paloalto without a not so simple script or without something like splunk. Sometimes I don't really know what to think: one one hand there are some "basics" missing, which would be great for a lot of customers and on the other hand I love the API - if something isn't built in at least PaloAlto gives us the possibility do implement it by ourselfs. Yes, this means some work, but you then also get exactly what you need instead of buying another (expensive) product which then fits 80% of your needs (instead of lets say 60% without some scripting) ... advantages and disadvantages - we will always have to live with them
... View more