On FortiAnalyzer 5.2, when I'm working on composing a report and I'm in
the layout tab, the GUI insists on auto-saving every couple of minutes.
I wouldn't mind except that it removes focus from the report layout
window and stops me dead in my tracks;...
Hey all Trying to automate a few things so I made a script that makes a
script that makes the many objects I need to create on a regular basis.
The problem is that whatever I do, I can't get the "Upload bulk CLI
file" to take my CLI script, all I get...
I've been configuring our FAZ device on 5.2 and I can't get the source
country to show up. Traffic log shows flags on destination IP, detects
destination country, but doesn't do it for source IP or source country.
This happens whether I import logs b...
Hi all. We've recently procured a FAZ-1000E device to refresh our old
FAZ-2000A running on 4.0 MR3. As part of the upgrade process, I'm
currently rewriting the old reports we had customized. I've run into an
annoying issue. In 4.0 MR3, we were able t...
I spoke to my PowerShell script in gentle tones, got it to output UTF8,
found out MS in their wisdom does BOM by default in PowerShell output
with Out-File, switched all my encoding to ASCII because 1 byte should
be enough for every char, and now the...
The release notes for FAZ 5.2.10 states it supports reporting from 4.3.2
and above. I understand "interoperability issues" but mapping the other
fields correctly and just forgetting about mapping src_country sounds
more like a bug in the parser than ...
FortiGate devices report the source country fine, logs making it to our
old unit (operating in parallel right now) have source country set, raw
logs on new FortiAnalyzer device shows src_country makes it but field
isn't renamed/remapped to srccountry...
I doubt anyone cares but this looks like a firmware bug in 5.2 when
receiving logs from 4.3. The 4.3 field dst_country gets remapped
properly by FAZ 5.2 as dstcountry, but src_country does not get mapped
to srccountry. The log parser for 4.3 logs lik...
