You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The httpjson input should report filenames for application/zip events.
We have a bug for an integration that utilizes the filename to determine a log_type field as the field is in the name. For example, filename="delivery_20160705162902600.log" -> log_type: delivery. When utilizing compress: true, the filename is instead a random guid and so the log_type can't be derived, example filename="8578FCFC-A305-4D9A-99CB-F4D5ECEFE297.zip".
The text was updated successfully, but these errors were encountered:
The httpjson input should report filenames for
application/zip
events.We have a bug for an integration that utilizes the filename to determine a
log_type
field as the field is in the name. For example,filename="delivery_20160705162902600.log"
->log_type: delivery
. When utilizingcompress: true
, the filename is instead a random guid and so thelog_type
can't be derived, examplefilename="8578FCFC-A305-4D9A-99CB-F4D5ECEFE297.zip"
.The text was updated successfully, but these errors were encountered: