logstash-plugins/logstash-output-file

Issues

• Provide additional compression options to output to zip, tar.gz, etc..

  #52 opened 7 years ago by ppf2
  2

• File Output Enhancement - file rotation

  #57 opened 6 years ago by red8383light
  4

• Log rotation handling

  #10 opened 9 years ago by bobrik
  3

• broken gzip file produced sometimes.

  #79 opened 5 years ago by TomonoriSoejima
  7

• The pipeline and workers stop permanently when there is no more space on the output path

  #91 opened 4 years ago by leludo84
  1

• The stale files cleanup cycle does not run if no new events

  #88 opened 4 years ago by luizgpsantos
  1

• Gzip compression results to uncompressable package

  #61 opened 6 years ago by admlko
  3

• add close_older option (like filebeat)

  #30 opened 8 years ago by fbaligand
  3

• Output file always tries to convert to UTF-8

  #8 opened 9 years ago by CalldiDoctor
  1

• cannot install

  #93 opened 3 years ago by oprogramador
  1

• A big value for `flush_interval` option prevents logstash from shutting down

  #90 opened 4 years ago by rocco8620
  0

• Unable to write to file after it is set to append only and closed/opened

  #51 opened 4 years ago by erikanderson
  6

• EEXIST on strategically placed symlink

  #87 opened 4 years ago by jrcichra
  0

• Add support for zstandard output format

  #86 opened 4 years ago by Ckram
  0

• Plugin is closing file with periodic updates

  #59 opened 4 years ago by ceeeekay
  6

• Deleted output files consuming filesystem space

  #81 opened 5 years ago by bpschuck
  0

• NoMethodError: undefined method `truncate' for #<IOWriter:0x3e9b038 @io=#<Zlib::GzipWriter:0x164b00d>

  #66 opened 6 years ago by ycombinator
  2

• dir_mode and file_mode are interpreted as decimal instead of octal numbers

  #78 opened 5 years ago by micoq
  4

• Logstash doesn't ship tail of my log file until I terminate logstash process

  #12 opened 9 years ago by jordansissel
  12

• SystemExit if mkdir fails (e.g. due to permissions), instead of using `filename_failure`.

  #74 opened 6 years ago by kreiger
  0

• Support file rename atomically

  #73 opened 6 years ago by guyboertje
  0

• Useless lseek() and stat() calls -> bad performance on NFS shares

  #54 opened 7 years ago by micoq
  2

• No output file

  #71 opened 6 years ago by Jacox98
  1

• Support Gzip level ？

  #69 opened 6 years ago by zhxiaom5
  0

• Dose gzip output support multi thread?

  #68 opened 6 years ago by zhxiaom5
  0

• flush_interval > 0 not working

  #62 opened 6 years ago by heli80
  7

• How can logs only have this?

  #65 opened 6 years ago by TiaraH
  1

• write_behavior option not showing in documentation

  #63 opened 6 years ago by andrewbanchich
  0

• The Logstash File Output line contains %{message} instead of event message field.

  #60 opened 6 years ago by elapse2039
  2

• Overwrite file

  #24 opened 7 years ago by runningman84
  9

• logstash-output-file ignores write permissions in file_mode option

  #49 opened 8 years ago by L4rS6
  2

• File: the event tried to write outside the files root, writing the event to the failure file

  #37 opened 8 years ago by yangxikun
  3

• Logstash exits if attempting to create directory when file exists in path

  #45 opened 8 years ago by purbon
  0

• Date based log rotation not working

  #34 opened 8 years ago by sdiazb
  0

• flush_interval 0 doesn't flush right away

  #32 opened 8 years ago by k2xl
  0

• Output file plugin is not supporting workers

  #29 opened 8 years ago by divjotsinghnanda
  0

• Configuration option for umask

  #18 opened 8 years ago by bobrik
  0

• failing specs under ng-pipeline

  #25 opened 8 years ago by colinsurprenant
  1

• Must support codec use

  #7 opened 9 years ago by wiibaa
  2

• Output is always in JSON

  #19 opened 9 years ago by NeckBeardPrince
  4

• Behavior when output file is deleted while LS is running

  #20 opened 9 years ago by suyograo
  7

• file output doesn't re-start on broken pipe

  #17 opened 9 years ago by IrlJidel
  0

• Logstash and redis (file output may not be flushing on write)

  #11 opened 9 years ago by jordansissel
  0

• Windows test failure

  #5 opened 9 years ago by jordansissel
  1

• Logstash 1.5.0 writing the event to the failure file, Bug?

  #3 opened 9 years ago by remotesyssupport
  4