cef,infoblox_nios,keycloak,modsecurity,panw,pfsense,qnap_nas,snort,sonicwall: ensure timezones are strings - #5051
Conversation
🌐 Coverage report
|
|
/test |
|
These all pass locally, so I'm not sure what is going on. |
|
/test |
1 similar comment
|
/test |
…ap_nas,snort,sonicwall: ensure timezones are strings
811eabe to
a89bf1c
Compare
This depends on each stream container spawn getting a unique port and so distinguishing the docs.
This depends on file name differences.
ᕙ(⇀‸↼‶)ᕗ |
cdd3ad4 to
87ec81f
Compare
|
I'm going to back out the ms-dhcp, the error makes no sense. |
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
| {{/each}} | ||
| fields_under_root: true | ||
| fields: | ||
| tz_offset: {{tz_offset}} |
There was a problem hiding this comment.
This raises the question of what should the behavior be. This field was not used in a pipeline (or presenting the manifest). And the event.timezone produced by the add_locale processor does not appear to be used anywhere.
There was a problem hiding this comment.
Yes, this was my confusion here. I saw it wasn't being used. I'll add time zone config to the processor.
There was a problem hiding this comment.
Looking into this further, it looks like the logs always have a time zone. So I think the removal is the correct thing to do here.
There was a problem hiding this comment.
The time_stamp field in this test file does not have a TZ. And I think that time value is being parsed in the nginx-modsec pipeline. Maybe the value is always reported in UTC?
|
Package cef - 2.6.1 containing this change is available at https://epr.elastic.co/search?package=cef |
|
Package infoblox_nios - 1.6.1 containing this change is available at https://epr.elastic.co/search?package=infoblox_nios |
|
Package keycloak - 1.7.1 containing this change is available at https://epr.elastic.co/search?package=keycloak |
|
Package modsecurity - 1.5.1 containing this change is available at https://epr.elastic.co/search?package=modsecurity |
|
Package panw - 3.5.1 containing this change is available at https://epr.elastic.co/search?package=panw |
|
Package pfsense - 1.6.2 containing this change is available at https://epr.elastic.co/search?package=pfsense |
|
Package qnap_nas - 1.7.1 containing this change is available at https://epr.elastic.co/search?package=qnap_nas |
|
Package snort - 1.4.1 containing this change is available at https://epr.elastic.co/search?package=snort |
|
Package sonicwall_firewall - 1.3.1 containing this change is available at https://epr.elastic.co/search?package=sonicwall_firewall |
…nicwall: ensure timezones are strings (elastic#5051)

What does this PR do?
This ensures that timezone offsets in the form "+0n00" are not interpreted as octal integers.
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots