[graylog2] Graylog server is using lots of RAM

We have a single machine install of Graylog (1.3.2). It is a VM running in our VMware cluster and is built on Ubuntu 14.04. The vm has 4 cores and 16GB of ram. We get 2-5 messages per second. There are 5 inputs running, a couple of streams with simple rules, and the services (mongo, elastic) are

Re: [graylog2] Timezone best practice?

-timezone ` command to adjust the timezone for the Graylog > root user, and your system. Don't forget to run `sudo graylog-ctl > reconfigure` after using the previous command. > > I hope that helps. > > Regards, > > Edmundo > > > On 25 Sep 2015, at 09:03,

[graylog2] Timezone best practice?

We are setting up a 1.2.1 server. The logs being gathered and the people using the interface for searches, etc are all in the US/Pacific timezone. Graylog was installed using the omnibus installer. Currently all of the entries in the web UI indicate UTC rather than PDT (see below). What is the

Re: [graylog2] Re: Upgrade steps for deb based system 1.0.2 --> 1.1.3

ersion 1.5.2 or 1.6.0, > though. > > Cheers, > Jochen > > On Wednesday, 24 June 2015 03:33:16 UTC+2, Peter Loron wrote: >> >> Hello. I've got a Graylog system running (Ubuntu 14.04) 1.0.2. I'm going >> to be upgrading, and have been unable to find any

[graylog2] Upgrade steps for deb based system 1.0.2 --> 1.1.3

Hello. I've got a Graylog system running (Ubuntu 14.04) 1.0.2. I'm going to be upgrading, and have been unable to find any specific instructions. Do I need to do anything other than install the updated deb packages? Thanks. -Pete -- You received this message because you are subscribed to the

[graylog2] Re: [ANN] Graylog 1.0.1 has been released

I'm also seeing this. Glad I'm not going crazy... -Pete On Tuesday, March 24, 2015 at 8:19:01 PM UTC-7, Mark Moorcroft wrote: > > > It still says 1.0.0 for graylog-web at the bottom of the interface despite > yum reporting 1.0.1. > > FYI > > On Monday, March 16, 2015 at 8:00:44 AM UTC-7, Jochen

[graylog2] Re: Log extractor for Atlassian products? Stash, JIRA, Confluence?

iguringLogging-properties > > for an example with Confluence). > > It would be great if you could post your results with this on the mailing > list! > > > Cheers, > Jochen > > On Wednesday, 11 March 2015 01:22:12 UTC+1, Peter Loron wrote: >> >> We have s

[graylog2] Log extractor for Atlassian products? Stash, JIRA, Confluence?

We have several Atlassian products in use (Confluence, Stash, JIRA), and I would like to get the logs into Graylog. I see that there is a Log4J GELF appender. Anybody know if I can easily add that appender to our app installs? Thanks! -- You received this message because you are subscribed to

Re: [graylog2] Anybody have a good extractor for ESXi 5.5 logs?

ent from a mobile device > > On 6. mar. 2015 kl. 19.09.25 CET, Peter Loron > wrote: > > Hi. We're running Graylog 1.0, and have a couple of VMware ESXi 5.5 > clusters. Sadly, the messages coming from ESXi don't conform to the syslog > standards. Anybody have a worki

[graylog2] Anybody have a good extractor for ESXi 5.5 logs?

Hi. We're running Graylog 1.0, and have a couple of VMware ESXi 5.5 clusters. Sadly, the messages coming from ESXi don't conform to the syslog standards. Anybody have a working extractor for these? Thanks. -Pete -- You received this message because you are subscribed to the Google Groups "gra

Re: [graylog2] Logs from Cisco ASA with bad "source" field

Roberto, you will need to have the device(s) send their logs to the new port instead of 10514. That way only the data that needs the extra parsing will be processed by the extractor. Cisco devices --> (or whatever) All other Syslog --> 10514 -Pete On Friday, February 27, 2015 at 11:17:25