topic Re: Panorama - Logging and Reporting Settings in General Topics

Panorama - Logging and Reporting Settings

bbilut — Wed, 15 Feb 2017 22:28:39 GMT

I'm rather confused by the quota settings. I've had my Panorama for about 3 years and was asked to produce a report today and with 500GB of storage I relealized that my history was only about 5 days to produce a user activity report. I would have sworn that wasn't always the case, so I'm not sure what happened. I've been adjusting the quotas, and can't really find a good document to explain the various groups, but I really want to have my quota optimized so I can storage as much user activity as possible. It also seems that either I'm adjust something the wrong way or each time you adjust it wipes out your data because right now I only have 1 hour of history???? These are my current settings I pulled from command line. Can anyone offer any input recommendations.

Thanks!

system: 1.00%, 4.856 GB Expiration-period: 0 days
config: 1.00%, 4.856 GB Expiration-period: 0 days
appstat: 1.00%, 4.856 GB Expiration-period: 0 days
traffic: 20.00%, 97.130 GB Expiration-period: 0 days
threat: 2.00%, 9.713 GB Expiration-period: 0 days
trsum: 2.00%, 9.713 GB Expiration-period: 0 days
hourlytrsum: 1.00%, 4.856 GB Expiration-period: 0 days
dailytrsum: 1.00%, 4.856 GB Expiration-period: 0 days
weeklytrsum: 1.00%, 4.856 GB Expiration-period: 0 days
urlsum: 55.00%, 267.107 GB Expiration-period: 0 days
hourlyurlsum: 1.00%, 4.856 GB Expiration-period: 0 days
dailyurlsum: 1.00%, 4.856 GB Expiration-period: 0 days
weeklyurlsum: 1.00%, 4.856 GB Expiration-period: 0 days
thsum: 2.00%, 9.713 GB Expiration-period: 0 days
hourlythsum: 1.00%, 4.856 GB Expiration-period: 0 days
dailythsum: 1.00%, 4.856 GB Expiration-period: 0 days
weeklythsum: 1.00%, 4.856 GB Expiration-period: 0 days
extpcap: 1.00%, 4.856 GB Expiration-period: 0 days
hipmatch: 1.00%, 4.856 GB Expiration-period: 0 days

Re: Panorama - Logging and Reporting Settings

BenjAudy.MTL — Thu, 16 Feb 2017 03:42:31 GMT

URL filtering logs are included in the threat database, so you might want to increase the threat quota considerably. Maybe you thought those went in the URL summary database?

I had a weird bug once when I allocated exactly 100% of the quota. I ended up with a negative unallocated value and I think I lost some logs because of that. You seem to have 5% unallocated space, so this is probably not related to your problem.

Benjamin

Re: Panorama - Logging and Reporting Settings

bbilut — Thu, 16 Feb 2017 13:23:30 GMT

That is exacly what I thought that the URL filtering logs were in the URL summary. You would assume, right?

Thank you for the reply!

Re: Panorama - Logging and Reporting Settings

reaper — Thu, 16 Feb 2017 13:31:55 GMT

keep in mind the logdb is a database, so changing quotas requires the db to be rewritten thus purging the data inside

you will want to increase the traffic (+-30) and threat (+-15) quota considerably as these would be your 'workhorse' logs, and decrease urlsum dramatically (2-5?) as this is a summary db which takes up less space per log entry

you'll also want to up the trsum (5-10) and hourlytrsum (3) as this is where user activity reports come from

anything that has *sum in it is a summary database containing 'statistical' data versus cold hard log entries

Re: Panorama - Logging and Reporting Settings

bbilut — Thu, 16 Feb 2017 13:34:24 GMT

Thanks again for the info. I had a case open, but got better support here.

I reset to default and made some minor adjustments. This is what I have now.