API log export hard-coded to a 20 entry limit?

cevans2 — Wed, 22 Jan 2014 00:52:39 GMT

In panorama 5.1.5 code, I'm attempting to pull down traffic logs for analysis of application type vs rule. My query is structured like this:

https://10.x.x.240/api/?type=log&log-type=traffic&query=%28%20receive_time%20geq%20%272012/12/31%2008:00:00%27%29&key=my…

Which gives me a success return, along with "query job enqueued with jobid 181"

When I query the results using

https://10.x.x.240/api/?type=log&action=get&job-id=181&key=mykeyhere

I'm only getting 20 results - although there are many, many more entries in the logs. Is this a hard-coded limit on results? Is there a way around it?

Re: API log export hard-coded to a 20 entry limit?

dward — Wed, 22 Jan 2014 07:08:19 GMT

20 is the default, but this is customizable up to 5000 using nlogs. Use the following format:

https://<firewall>/api/?type=log&log-type=<type>&nlogs=<number of logs to return>&query=<URL encoded query parameters>&key=<API key>

You can use additional modifiers outlined in the API guide to start 5000 logs back and pull the previous 5000 logs. You can continue doing this until all of the logs of interest are pulled.

topic Re: API log export hard-coded to a 20 entry limit? in Automation/API Discussions

API log export hard-coded to a 20 entry limit?

Re: API log export hard-coded to a 20 entry limit?