Filebeat 7.7 panw module sends THREAT, but not TRAFFIC logs

[nverrill]

Versions here range from 7.1 to 8.1 which is within compatible ranges according to filebeat docs.
I just confirmed that we customized our traffic output logs. Some fields had been trimmed from the output.
I've now tested a default output and they are ingesting but with the wrong time zone in kibana, which appears to be a known issue where there is no timezone defined in the log itself:

Fix timezone parsing in iptables, mssql and panw modules

Filebeat-panw Module timezone issues

Sorry I explained that bad. My issue isn't the filebeats removing the event.timezone. This filebeats only exists to ingest that panos data for the SIEM app. My concern is that even with removing that field the data still was converted to 4 hours in the past. After changing the Kibana advance setting to UTC it set the data to the right time, but that also broke all the other data sources that come into ELK from various other applications. Their time instead of being correct was set to 4 hours i…

I'm a little uncertain how to fix this. I tried some of the fixes such as replacing the module/panw/panos/ingest/pipeline.yml in the pull request, as well as upgrading from filebeat 7.7.0 to 7.7.1 and it's still not the correct timezone in Kibana.

Is there something I can provide to help diagnose the issue?