don't press the TURBO button on your PC!!
Fix will be included in rc.3 later today. :)
On Thu, Feb 13, 2014 at 2:32 PM, Jochen Schalanda joc...@schalanda.name
wrote:
Hi,
I get the same notification on a single-node setup (Graylog2
0.20.0-rc.2) and the notification reappears every few
Hi,
it seems as if your deflector (an Elasticsearch index alias
http://www.elasticsearch.org/guide/en/elasticsearch/reference/0.90/indices-aliases.html
used by Graylog2) has been corrupted. Graylog2 currently doesn't support
index aliases with more than 1 target index.
You can either fix
Hi,
the graylog2-web-interface is using the graylog2-server.uris setting from
the configuration to build the hyperlinks to the graylog2-server API
browser.
In your case, you obviously run graylog2-server and graylog2-web-interface
on the same system and thus use the loopback interface
Hi,
Am Dienstag, 19. August 2014 18:04:18 UTC+2 schrieb Lab Coat:
:~# java -jar /opt/graylog2/server/graylog2-server.jar -f
/etc/graylog2/server.conf
Error: Unable to access jarfile /opt/graylog2/server/graylog2-server.jar
It seems that Graylog2 hasn't been installed in the location you've
Hi,
there's currently no automatic splitting of messages from within the same
UDP packet in the Raw UDP Input (feature request at
https://github.com/Graylog2/graylog2-server/issues is welcome).
For your use case you'll have to send one message per UDP packet to the Raw
UDP Input of Graylog2.
Hi,
- is LDAP authentication supported when logging onto graylog2 GUI?
Yes! The Graylog2 web interface is basically just a visualization and UI
layer on top of graylog2-server and if you've configured LDAP for the
server, the web interface will automatically authenticate against that
source.
Hi!
Am Freitag, 22. August 2014 11:11:12 UTC+2 schrieb Martin Schütte:
have tried to use Syslog UDP input without logstash, and there are also
these 2 fields facility = unknown and level = Invalid [-1]
(values are different from GELF). Version is gone.
That is another topic; BSD
Hi!
Am Freitag, 22. August 2014 16:48:33 UTC+2 schrieb Foobar Geez:
- I started reading about logstash and GL2 and it seems both have
overlapping functionality. Based on your experience, is there any reason
why I should be choosing one over the other? Given this is a GL2 forum, I
am
Hi Mark,
Am Dienstag, 26. August 2014 20:02:43 UTC+2 schrieb Mark Moorcroft:
Apache and postfix both manage to run as non-root on low ports.
The way most UNIX daemons (like Apache httpd or Postfix) are doing this is
by starting with root privileges (UID 0) which allows them to bind
Hi Mark,
authbind also works on CentOS. You can either build it yourself or use a
RPM like https://github.com/tootedom/authbind-centos-rpm
Cheers,
Jochen
Am Dienstag, 26. August 2014 20:40:31 UTC+2 schrieb Mark Moorcroft:
All CentOS here.
On Tue, Aug 26, 2014 at 11:05 AM, Lennart
Hi!
Currently there is no direct integration of Graylog2 and Openstack but of
course you can send all your Openstack logs into Graylog2 (e. g. via rsyslog
http://graylog2.org/resources/documentation/sending/syslog) and create custom
rules and extractors
Hi,
this sounds like an incomplete installation to me. Either the JAR file
isn't in the place you're expecting it to be, the JAR file is defect, or
the permissions of the directory are insufficient.
You can try out the official packages for Ubuntu 14.04
Am Freitag, 29. August 2014 10:46:50 UTC+2 schrieb mehmet hacısalihoğlu:
Where can I find sample rsyslog.conf and other configuration files?
Because Openstack has many services and mixed configurations. So, I dont
make this configuration.
Please refer to the Openstack documentation I've
Hi Mark,
In the current permission/account model of Graylog2 regular users (i. e.
non-admin accounts) are restricted to preconfigured streams and can't use
the freetext search. As a workaround you could create a stream which
matches all messages.
Cheers,
Jochen
Am Donnerstag, 4. September
Hi,
Graylog2 currently doesn't support Windows officially. At least we don't
run any tests with Windows. ;-)
But since the problem you've described is quite solvable, you might want to
create an issue for that at
https://github.com/Graylog2/graylog2-server/issues.
Cheers,
Jochen
Am
I'm glad that it worked out. :-)
Am Freitag, 5. September 2014 15:30:02 UTC+2 schrieb Lab Coat:
I got it working! I restored the box from vmware template and followed
the link you provided:
http://graylog2.org/resources/documentation/general/packages
I used this page to do the hashes in
Hi,
are there any log messages before that error? It might also help to
start `graylog2-server` with the `--debug` parameter to get more
detailed messages.
Do other (older) versions of Graylog2 also fail to start on your system?
Cheers,
Jochen
On 11.09.2014 12:08, Илья Кулик wrote:
Im sorry
Hi Jamie,
Am Mittwoch, 24. September 2014 19:58:38 UTC+2 schrieb Jamie Geyer:
just a quick question -
In general does adding extractors to an input cause any performance
impacts on the input?
In general yes, because the extractors have to be run for every message
which is processed by
Hi Cédric,
Am Freitag, 10. Oktober 2014 09:46:30 UTC+2 schrieb Cédric Madörin:
Our envireonement requires java 6 so I installed 7 in addition to get
graylog2 to run.
I saw that there is the parameter -java-home so I tried using it but
always got the error:
java_cmd can't be redeclared
Hi,
Am Dienstag, 14. Oktober 2014 14:52:11 UTC+2 schrieb smgo...@gmail.com:
I understand it is bound to local interface but I am only accessing this
from the local node not from any other system.
http://127.0.0.1:12900/api-browser using the drop down menu under Node
menu API browser - and
Hello Christian,
Am Sonntag, 19. Oktober 2014 21:34:02 UTC+2 schrieb Christian Schwerdtfeger:
When i now start my system, i get the following exception
org.apache.logging.log4j.core.appender.AppenderLoggingException: Attempted
to append to non-started appender gelfAppender
This is an
Hi Arie,
Am Dienstag, 21. Oktober 2014 10:19:31 UTC+2 schrieb Arie:
The problem is that I at first set up the wrong repo I guess. 0.91 in
stead of 0.90
now I have the repo standing allright but it keeps on comping with the
09.1 versions.
You could try to remove the old set-up package
Hi Stanislav,
Am Dienstag, 21. Oktober 2014 12:35:46 UTC+2 schrieb Stanislav Kopp:
I've done upgrade today from 0.90 to 0.91 via debian repos, now I have the
same error as Sébastien and Jim with graylog2-web in this thread
https://groups.google.com/forum/#!topic/graylog2/7LU3apz1GmI.
I
Hi Iain,
Am Mittwoch, 22. Oktober 2014 18:06:33 UTC+2 schrieb Iain Keddie:
Please could you point me in the right direction for a simple way to get
text from an arbitrary file, into Graylog2?
In general you can set-up a Raw UDP or Raw TCP Input on your Graylog2
server and send your logs
Hi Sanchal,
please check your IPTables configuration on the node hosting your Graylog2
server. The packet filter rules are basically applied one after another and
evaluation won't continue after the first hit.
I see in your `iptables` output that you have multiple REDIRECT rules for
514/udp
Hi,
it looks like your on-disk message cache has been corrupted. Please delete
the mentioned file(s) from your spool directory (check the
message_cache_spool_dir setting in graylog2.conf) and restart your Graylog2
server.
Cheers,
Jochen
Am Freitag, 24. Oktober 2014 07:02:33 UTC+2 schrieb
Hi Martin,
Am Freitag, 24. Oktober 2014 11:15:25 UTC+2 schrieb Martin René Mortensen:
I hope graylog2 0.91 will fix this by putting overflowing message into
temporary disk storage instead of filling up memory until it dies, but Im
not sure it can ever catch it up.
As a matter of fact
Hi Seby,
Am Sonntag, 2. November 2014 09:15:33 UTC+1 schrieb Seby Francis:
We have a cluster of graylog2 servers (3 instances on aws) configured and
I see the message_cache_spool_dir is getting filled up. Not sure what to
change.
Unfortunately the off-heap message cache is currently
Hi Marty,
damn it. That's actually another error not even related to the first one.
:-(
We will fix that one in the Graylog2 0.92.x version line. Another bugfix
release for Graylog2 0.90.x and 0.91.x is currently not planned.
Regards,
Jochen
--
You received this message because you are
Hi Miguel,
1. Since I have 3 logs types (for now, more will be added) coming through
the same input, do I apply all the extractors to that 1 gelf input?
Yes, you can add all extractors to that single GELF input. Alternatively
you can create a specialized GELF input with the necessary
Hi Michael,
it looks like your Graylog2 server hasn't been shutdown properly the last
time or there wasn't enough free disk space available at that time and the
message spool files have been corrupted. You can delete those files in the
spool directory (see message_cache_spool_dir in your
Hi Dirk,
The source host is running a Centos 5.11 with rsyslog 3.22.1-7.el5
configured to remote log to a Graylog2 server TCP syslog port 514.
Is Graylog2 really listening on port 514/tcp? You can check this with `lsof
-i :514` or `netstat -tplen | grep :514`.
The problem is, that Graylog2
Hi Jeremy,
Are these extractors, by the smallest chance, still somewhere that I can
recover them or am I out of luck?
I'm afraid that unless you have a backup of the MongoDB database of
Graylog2 you're out of luck. :-(
The extractors are persisted as embedded documents into the description
Hi Mark
On 06.11.2014 22:46, Mark Moorcroft wrote:
Looks like you can't use $.
Just to clarify this, do you have a '$' in your password or in the
SHA256 of your password?
Cheers,
Jochen
On Thursday, November 6, 2014 1:40:01 PM UTC-8, Mark Moorcroft wrote:
I am in the process of
Hi Jeremy,
since I'm also out of ideas right now (something *is* wrong with the list
of cluster nodes in Graylog2 but finding the culprit will probably take
some time…) reinstalling the Graylog2 server might just be the easier way
of resolving this. :(
Am Freitag, 7. November 2014 15:26:54
Hello Jeff,
from the output of netstat it looks like your graylog2-server isn't
running. Could you please check that the server is actually running?
Which version of Graylog2 are you using? Only Graylog2 0.90.x (and before)
work with Elasticsearch 0.90.10. Graylog2 0.91.x and later requires
Hi Jeff,
Am Montag, 10. November 2014 17:24:00 UTC+1 schrieb Jeff Schoolcraft:
My server log tail is:
2014-11-10T16:21:35.453Z INFO [Reflections] Reflections took 95 ms to
scan 1 urls, producing 5 keys and 19 values
2014-11-10T16:21:37.332Z INFO [Reflections] Reflections took 252 ms to
Hi Roddy,
Am Dienstag, 11. November 2014 02:15:25 UTC+1 schrieb Roddy Rodstein:
Could you please share the SSL setup to allow logstash-forwarder to send
messages to graylog2?
Graylog2 currently doesn't support the format used by logstash-forwarder
but feel free to open a feature request on
Hi Mark,
I think the easiest setup for your requirements would be to forward the
messages processed by the locked down Graylog2 server to the user-facing
Graylog2 server via the GELF output. This way you could filter messages or
run extractors in exactly one place and just forward the final
Hi Jeff,
do you see any other Exceptions in the logs of Graylog2? Which version of
Graylog2 are you running and can it connect to the Elasticsearch cluster?
Best regards,
Jochen
Am Mittwoch, 19. November 2014 16:54:32 UTC+1 schrieb Jeff Schoolcraft:
I’m trying to install Graylog2 and I’m
Hi,
we also like this idea and I have opened an issue
at https://github.com/Graylog2/graylog2-server/issues/773 for this change.
Cheers,
Jochen
Am Mittwoch, 19. November 2014 14:34:57 UTC+1 schrieb Jeremy Farr:
Or can't we create and maintain extractors separately from inputs and
later
Hi Seby,
I'm quite sure that this error isn't related to the PagerDuty plugin. Does
the error vanish when you remove the PagerDuty plugin?
Actually it resembles another bug which should've been fixed some time ago.
Which version of Graylog2 are you running?
Best regards,
Jochen
Am
/) and restarted the server.
On Thu, Nov 20, 2014 at 6:45 PM, Jochen Schalanda joc...@torch.sh
javascript: wrote:
Hi Seby,
I'm quite sure that this error isn't related to the PagerDuty plugin.
Does the error vanish when you remove the PagerDuty plugin?
Actually it resembles another
Hello Sandro,
it looks like you've only run the tool for a single Elasticsearch index
(graylog2_0). Graylog2 usually is using multiple indices for storing
messages (which can be configured in the retention settings in your
graylog2.conf). It's very likely that the messages with the defective
Hi Jamie,
seems like you've hit a bug that has been fixed in Graylog2 0.90.1 and
later.
Please refer to the news post about the release of Graylog2 0.90.1 at
http://www.graylog2.org/news/post/0006-two-new-graylog2-releases which
also explains how to fix these incorrect timestamps for existing
Hi Josep,
On 24.11.2014 13:30, Josep Maria Comas Serrano wrote:
which leads Graylog2 to get into the elasticsearch cluster as 1.3.4
client node. Is it possible to change it to 1.4.0, or maybe it must be
1.3.4?
The message is totally fine. Graylog2 currently ships with Elasticsearch
1.3.4
Hi Mark,
Am Dienstag, 25. November 2014 00:40:36 UTC+1 schrieb Mark Moorcroft:
Are there instructions available to help me setup up a GELF input from
Windows nxlog with TLS enabled?
I'm not familiar with this particular setup but you should note that
Graylog2 currently does not support TLS
Hi Andrea,
Am Dienstag, 25. November 2014 09:29:02 UTC+1 schrieb Andrea Consadori:
aaa (bbb) (ddd)
how can i create a regex that say take only the text in the second
parenthesis?
You can use a *non-capturing group* for this (see
Hi Martin,
without going into detail on your actual question, there is a great blog
series by Scott Pack about highly-available Graylog2 setups which you might
want to take a look at.
- http://secopsmonkey.com/migrating-graylog2-servers.html
-
Hi Dimitri,
multiple (or chained) message retention strategies are currently not
possible with Graylog, so I'm afraid you'll have to set-up multiple
instances to get different retention strategies for different messages.
Cheers,
Jochen
Am Dienstag, 25. November 2014 15:18:57 UTC+1 schrieb
Hi Josep,
that's a bug in Graylog2 0.92.0-rc.1 which has been fixed and will be part
of Graylog2 0.92.0.
Cheers,
Jochen
Am Dienstag, 25. November 2014 17:28:52 UTC+1 schrieb Josep Maria Comas
Serrano:
Sorry, actually the error is:
2014-11-25 17:25:27,469 ERROR:
Hi Tristan,
I don't think that creating symlinks of the Upstart configs in /etc/init.d/
is a good idea. Users might want to run those init scripts and it will
fail miserably. It's rather a problem of the bash-completion in Ubuntu and
we shouldn't try to work around that.
I'd rather add dummy
Hi everyone,
after an extended beta and release candidate phase we just released
Graylog2 0.92.0.
We'd like to thank everyone in the community who made it possible to
produce this release by thoroughly testing the beta and release candidate
versions!
There are lots of new features in
Hi,
could you please post your configuration of the CloudTrail plugin (minus
the sensitive stuff like credentials)?
Cheers,
Jochen
On Tuesday, 2 December 2014 00:16:03 UTC+1, blackberry wrote:
Getting these errors when trying to launch the plugin
2014-12-01 15:14:12,885 INFO :
Hi Martin,
please try deleting the files in your message_cache_spool_dir (see
graylog2.conf).
Cheers,
Jochen
On Tuesday, 2 December 2014 10:16:38 UTC+1, Martin René Mortensen wrote:
After upgrading to 0.92 Im having troubles with
java.lang.NullPointerException in GL2 server logs. I have
Hi Martin,
On Tuesday, 2 December 2014 14:22:56 UTC+1, Martin René Mortensen wrote:
cant see any difference, but the instance failing has 3 GL2 nodes and the
one not failing has only 1.
What exactly do you mean with this? Do you run a Graylog2 cluster with 3
distinct nodes or are you
Hi Aymeric,
the docs on that topic are a bit lacking at the moment, sorry.
On Wednesday, 3 December 2014 23:09:54 UTC+1, Aymeric Alibert wrote:
But it does not detail what private key formats are supported (PEM, DER,
PKCS8...). What type of encryption: RSA?
At the moment Graylog2 only
Hi Marty,
On Thursday, 4 December 2014 07:19:02 UTC+1, Marty wrote:
When using the UI for GL2 v0.91.3, no messages are shown.
Searching messages from the GELF TCP Input, show nothings. Any ideas why
this would be ?
Did this setup work before, i. e. forwarding messages using a GELF output
Hi Chris,
On Wednesday, 3 December 2014 19:06:42 UTC+1, Chris Tresco wrote:
I am wondering why this file gets so large and what I can do to keep the
size down. It being that big, it seems to me it would be a problem with
feeding messages to elasticsearch for indexing but I am not sure how
Hi Florent,
unfortunately there have been some incompatible changes between Graylog2
0.91.x and 0.92.x regarding the message format used by Graylog2 Radio.
Please update your Graylog2 Radio nodes to Graylog2 0.92.0 as well or
downgrade your server to Graylog2 0.91.3.
Cheers,
Jochen
On
Hi,
we just released Graylog2 0.92.1-rc.1 to fix some bugs that had slipped
into the Graylog2 0.92.0 release. Thanks to everyone who reported bugs in
the last release via GitHub, via the mailing list, and on IRC!
This is strictly a bugfix release. No new features have been introduced. If
no
Hi Marty,
please download Graylog2 0.92.1-rc.1 and see if it fixes the problem for
you.
You can find the release announcement at
https://groups.google.com/forum/#!topic/graylog2/Ssc4kTI2lDM.
Cheers,
Jochen
On Thursday, 4 December 2014 07:19:02 UTC+1, Marty wrote:
Hi Folks,
I have two
Jochen,
This is not exactly my problem :)
My radio node in 0.91.3 has an GELF TCP Input, and all is working fine
with server in 0.92.
My problem occurs when I upgrade radio to 0.92, it does not process
messages from my GELF Input :(
On 12/08/2014 02:50 PM, Jochen Schalanda wrote:
Hi
Hi everyone,
since the release candidate didn't show any new regressions, we're proud to
release Graylog2 0.92.1 to the world.
We'd like to thank everyone in the community who made it possible to
produce this release by thoroughly testing the release candidate version
and sending us their
Hi Aymeric,
On Sunday, 14 December 2014 11:24:51 UTC+1, Aymeric Alibert wrote:
I upgraded my Graylog server from 0.92.0 to 0.92.1 (Ubuntu Server). No
config changes, I just replaced the code.
When I restart my Graylog server, all my inputs are gone (Streams and
Dashboards are fine). When I
Hi Tomas,
unfortunately joining two messages (or in general applying filters or
actions to more than one message at once) is currently not possible. You'd
have to join those messages before sending them to Graylog2 in the current
version.
Cheers,
Jochen
On Monday, 15 December 2014 00:55:53
Hi Tomas,
as far as I see, the class name of the input is wrong. The correct class
name is org.graylog2.inputs.gelf.tcp.GELFTCPInput, as
org.graylog2.inputs.gelf.tcp2.* only existed very briefly during the
development of Graylog2 0.92.0.
Cheers,
Jochen
On Friday, 12 December 2014 18:46:46
Hi Martin,
Graylog2 does support structured syslog messages in general. That said,
some applications and (most notoriously) network appliances have an
interesting idea of what they should look like.
It would be great if you could create an issue for this at
Hi Kevin,
currently it is not possible to create public (i. e. automatically
accessible to all users) in Graylog2. You'll have to explicitly allow each
user to use a stream (and dashboard).
Cheers,
Jochen
On Friday, 19 December 2014 18:00:35 UTC+1, Kevin Davis wrote:
Is it possible to set
Hi everyone,
we just released Graylog2 0.92.3 as our slightly early Christmas gift. This
is strictly a bugfix release and fixes some of the memory issues found with
Graylog2 0.92.0 and 0.92.1.
Thanks to everyone reporting their problems in #graylog2 on Freenode
Just for completeness: This problem has been discussed and solved in issue
#830 on GitHub https://github.com/Graylog2/graylog2-server/issues/830.
On Tuesday, 23 December 2014 07:52:07 UTC+1, yanda@gmail.com wrote:
We are using following platform:
SLES 11 SP2
graylog2-server-0.20.6
Hi Nathan,
that sounds correct overall.
Did you install Graylog2 manually before (i. e. by downloading the
tar-balls from https://www.graylog2.org/download and extracting them on
your system)? If that's the case, you probably have two separate
installations of Graylog2 on your system and only
Hi Nathan,
which version of Graylog2 did you install and which APT repository (they
are versioned) did you add?
Cheers,
Jochen
On Friday, 2 January 2015 14:44:15 UTC+1, Nathan wrote:
I've been using a previous version of Graylog2 for about 4 months now.
I've attempted to update the
Hi Shubhra,
you could write a custom plugin for this. Currently there is no CSV output
for Graylog2 and the plugin development docs
https://www.graylog2.org/resources/documentation/general/plugins are a
bit scarce but you can at the GelfOutput
Hi Rich,
you can get a list of all sources from Graylog2 over its REST API at the
following URL (replace localhost with the actual hostname of your Graylog2
server and use HTTP/1.1 Basic Auth to authenticate an admin user):
*http://localhost:12900/sources?range=0*
The query parameter *range*
https://www.graylog2.org/news/post/0013-graylog2-v0-92-3 for upgrade
instructions.
Cheers,
Jochen
On Friday, January 2, 2015 12:04:46 PM UTC-5, Jochen Schalanda wrote:
Hi Nathan,
that sounds correct overall.
Did you install Graylog2 manually before (i. e. by downloading the
tar-balls
Hi Anders,
in my experience master only nodes aren't *that* useful in a small cluster
setup (as in your case: 3 ES nodes). I would recommend letting the third
node join the cluster and rebalance the shards and replicas across all 3 ES
nodes. If you're not already running Elasticsearch 1.4.x,
Hi Anders,
you can disable the time range calculation for all indices with the
*disable_index_range_calculation* (
https://github.com/Graylog2/graylog2-server/blob/0.92.4/misc/graylog2.conf#L340-344)
setting in your graylog2.conf.
As for the indices you could also use the time-based retention
Hi Rob,
that's pretty much exactly what the histogram widget does.
Simply create the query within the time-range you want (e. g. 1 day ago),
enter the query (source:YOUR_SOURCE message:WORD), run the query and
select the required resolution in the result histogram (e. g. Hour, below
the
Hi everyone,
we just released Graylog2 0.92.4. This is strictly a bugfix release and no
new features have been introduced since Graylog2 0.92.3. As we are
approaching the big one-dot-oh release (please also see our news post about
the release of Graylog2 1.0.0-beta.1
Hi Ronald,
unfortunately the documentation on plugins for Graylog and how to write
them is still rather sparse (or more precisely almost non-existent). We
plan to change this in the near future.
In the mean time you can take a look at the Telemetry plugin, which comes
with some JAX-RS
Hi,
we currently only test the AMQP functionality with RabbitMQ and we're using
the RabbitMQ Java client in Graylog to connect to the AMQP message broker.
Could you please elaborate on the problems you're facing with ActiveMQ?
Cheers,
Jochen
On Saturday, 17 January 2015 21:46:42 UTC+1,
Hi Yves,
On Wednesday, 21 January 2015 08:48:40 UTC+1, yvesloui...@gmail.com wrote:
I tried with graylog2-web 0.92.4 and this morning
with graylog2-web-interface-1.1.0-SNAPSHOT-20150115173058, without success.
FWIW, the Graylog web interface usually just works with the matching
version of
Awesome. Thanks for sharing!
On Wednesday, 21 January 2015 06:00:48 UTC+1, Pete GS wrote:
Tom, I know this is an old post but did you ever get this solved?
I had the same issue and have resolved it so I'll post the solution here
in case it is the same...
Essentially the issue for us was
Hi,
On Wednesday, 21 January 2015 15:23:01 UTC+1, kutscher wrote:
Hello, i want to use Loadbalance UDP Syslog Messages to the Graylog2
Nodes.
Unfortunately that won't be possible because of the chunking mechanism
being used when submitting GELF messages via UDP because all chunks must be
Hi Ubay,
this was a bug in Graylog2 0.92.4 and earlier and will be fixed in Graylog
1.0.0.
The related issue can be found at
https://github.com/Graylog2/graylog2-server/issues/896.
Cheers,
Jochen
On Monday, 19 January 2015 11:42:03 UTC+1, Ubay wrote:
Hi,
I have a graylog 0.92.4
Hi Sumit,
it looks like Graylog cannot connect to your MongoDB server running on
127.0.0.1:27017. Please check that MongoDB is actually running and can be
accessed from the system you're running Graylog on.
Cheers,
Jochen
On Tuesday, 17 February 2015 07:33:32 UTC+1, Sumit Gupta wrote:
Hi
, but other
than that it's a drop-in replacement.
Best regards,
Jochen
On Wednesday, 18 February 2015 18:21:26 UTC+1, Petar Koraca wrote:
Hi Jochen,
is it safe to upgrade from Elasticsearch 1.3.x to 1.4.3 ?
Thanks
On Wednesday, January 14, 2015 at 7:53:05 PM UTC+1, Jochen Schalanda wrote
Hi Olaf,
have you tried upgrading to Graylog2 0.92.4
https://www.graylog2.org/news/post/0015-graylog2-v0-92-4 and does the
problem still occur? In general I'd suggest deactivating the disk based
message spool
https://github.com/Graylog2/graylog2-server/blob/0.92.4/misc/graylog2.conf#L310-312
,
thank for report.
But my experience only in Python or PHP programming. I don't know about
Java or Maven.
Any solution for me ?
thanks!
Tam
Vào 18:57:01 UTC+7 Chủ Nhật, ngày 01 tháng 2 năm 2015, Jochen Schalanda đã
viết:
Hi,
Graylog currently doesn't ship outputs to Cassandra
Hi Arie,
the '-' character needs to be escaped since it has a special meaning in the
Lucene query syntax, see
https://www.graylog2.org/resources/documentation/general/queries for
details. You also want to only have exact matches so you have to put the
query in double quotes.
The correct
Hi,
just for reference (and additional to the discussion on IRC): the related
bug report is https://github.com/Graylog2/graylog2-web-interface/issues/958
and a fix for this should land in Graylog 1.0.0.
Cheers,
Jochen
On Monday, 9 February 2015 11:45:04 UTC+1, Sapo wrote:
Hello,
is there
Hello Joseph,
you can use the Logback JSON encoder for Logstash (
https://github.com/logstash/logstash-logback-encoder) with any Logback
appender to write JSON which is compatible with logstash.
Cheers,
Jochen
On Saturday, 3 January 2015 15:17:10 UTC+1, Joseph DJOMEDA wrote:
Hello All,
Hi Olaf,
could you please confirm the versions of Graylog2 and Elasticsearch that
you are using? Elasticsearch 1.3.x is only supported in Graylog2 0.91.0 or
later.
Please also check the Elasticsearch logs for any unusual messages (should
be WARN or ERROR level).
Cheers,
Jochen
On Tuesday,
Hi Pete,
thanks for sharing this!
In general, using real hardware for database applications like
Elasticssearch is always a good idea, especially since it prevents problems
caused with noisy neighbors and disk-cache thrashing in virtualized
environments.
Cheers,
Jochen
On Thursday, 8
Ah, damn it. I should get another coffee. The number of messages are of
course useless for your specific question. :-(
On Thursday, 8 January 2015 10:47:42 UTC+1, Jochen Schalanda wrote:
Hi Pete,
the most simple (and most manual way) to find the number of messages per
day is to use
Hi,
the index.refresh_interval setting in Elasticsearch and the
*output_flush_interval* setting in Graylog2 (specifying the interval after
which the contents of the output buffer should be flushed to the default
output, usually ES) are not directly related.
Cheers,
Jochen
On Sunday, 4
Hi,
I'm delighted to announce the release of Graylog 1.0.1 into the wild. This
is purely a bug-fix release and doesn't bring any new features.
The changes since Graylog 1.0.0 are:
- Properly log stack traces (#970
https://github.com/Graylog2/graylog2-server/issues/970)
- Update REST
similar with this
appender:
https://github.com/pukkaone/logback-gelf
On Wednesday, March 11, 2015 at 3:16:47 AM UTC-7, Jochen Schalanda wrote:
Hi Peter,
I haven't done this myself, but from what I know it should be as easy as
dropping one of the log4j GELF appenders (
https://github.com
Hi,
you can set the timezone for the admin user in your Graylog configuration
with the *root_timezone* setting (
https://github.com/Graylog2/graylog2-server/blob/1.0.1/misc/graylog2.conf#L28-30
).
As for the Web interface default JDK/JRE timezone, this is the configured
timezone of the system
1 - 100 of 1677 matches
Mail list logo
