-
Folks,
I would appreciate very much if you'd consider adding [AMQP](http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-messaging-v1.0-os.html) as an output transport to lumberjack.
At least for …
-
We have just recently updated Logstash from version 2.3.4 to 2.4.0. It seems that since updating Logstash we have been having throughput issues (I suspect we are dropping logs somewhere, either in Fil…
-
I have created a new beat called Unifiedbeat (for lack of a better name) at:
https://github.com/cleesmith/unifiedbeat
This beat is useful for anyone wishing to index alert, event, and packet data from…
-
Too many logs getting generated inside /var/log/messages
```
Nov 18 12:51:47 ip-10-168-0-218 /usr/bin/packetbeat[27009]: log.go:111:
Stacktrace:
/go/src/github.com/elastic/packetbeat/Godeps/_workspa…
-
I did some local testing to get this to work but was not able to, instead i discovered this weird behavior.
**test log**
```
2015-11-10 10:14:38,907 line 1
line 1.1
2015-11-10 10:16:38,907 line 2
li…
-
current default configuration index shipper field as indexed causing host names like foo-bar-1 behave funny on visualizations.
I suggest set shipper as not_analysed so kibana can aggregate data prope…
-
Saw this on my install of packetbeat, "`Packetbeat version 1.0.0-beta2 (amd64)`" (the `amd64` is wrong, it is an `x86_64 CPU`):
```
[root@perf34 ~]# systemctl status packetbeat
packetbeat.service - L…
-
I tried to simulate the issue. I think what is happening is that the harvester isn't starting at the beginning of the new file. For testing, I set the timeout to 1 minute to simulate:
- } else …