Hi Jochen,
I have not made any change to the code, simply compiled it using typesafe
activator and the made a jar from the compiled code.
I also compared my jar(graylog-web-interface.graylog-web-interface-1.1.6)
with the official jar(graylog-web-interface.graylog-web-interface-1.1.6)
and my jar
Hi,
I am running Graylog 1.1.6 server component and Graylog web component 1.1.6
which I have compiled.
I am running this on ubuntu 14.04.1. For this I have installed
Elasticsearch 1.7.1, mongodb version v3.0.6 and Java 1.8.0_60. The Graylog
1.1.6 server component, Graylog web component 1.1.6,
Hi Anant,
I can't reproduce your problem with the official Graylog 1.1.6 web
interface, so I guess it's because of some changes you've made to the code
of your custom compiled version.
Cheers,
Jochen
On Monday, 14 September 2015 14:10:29 UTC+2, Anant Sawant wrote:
>
> Hi,
>
> I am running
Hi Lorenzo,
the error message you've seen ("[…] We expected HTTP 200, but got a HTTP
-1.") is usually a sign of a request timeout. By default the request
timeout for HTTP requests from the Graylog web interface to a Graylog
server node is 5 seconds and can be customized in the configuration
Thanks Bernd,
https://graylog.ideas.aha.io/ideas/GL2E-I-447
On Wednesday, August 19, 2015 at 12:14:30 PM UTC+2, Bernd Ahlers wrote:
>
> Hey Zulfikar,
>
> Graylog cannot consume Kinesis streams yet. You could open a new feature
> request in our ideas portal for this.
>
>
Hello everyone,
i've been running Graylog (currently, version 1.1.6) on a three node
cluster for several months, and recently (i suspect, from last week) the
"System/Overview" page on the Web Interface has stopped running.
The error is
*Reason:* Could not fetch system information. We
I would like to know If I create a stream, it will process all messages
from all inputs, or is there anyway to select which input that stream will
process?
Thanks
--
You received this message because you are subscribed to the Google Groups
"Graylog Users" group.
To unsubscribe from this
Thinking about failure/recovery mode ...
Let's say we've had an incident, our search system flopped over and died or
something, and graylog is saturated with messages; graylog is busy flushing
out as fast as possible in order to catch up.
In this mode, for the duration of this "catching up"
Is there anything like an "include" statement to include different config
files for Graylog Collector.
I want to centralize the different configuration files of all windows
servers on a network share, so that multiple servers could be configured in
on file only?
Is something like this possible?
Hi Claus,
certain characters have to be escaped in the Lucene query syntax (which is
being used by Graylog and Elasticsearch), see
http://docs.graylog.org/en/1.1/pages/queries.html#escaping for details.
Cheers,
Jochen
On Tuesday, 8 September 2015 10:31:14 UTC+2, Claus Koell wrote:
>
> Hi !
>
Hi Fabian,
as a matter of fact, including other configuration files using an "include"
statement is supported in the configuration file used by the Graylog
Collector, see
https://github.com/typesafehub/config/blob/v1.2.1/HOCON.md#includes for
details.
Centralized management for the Graylog
Hi again !
Forgot to escape the ':' character
source_file:"C\:\\Program
Files\\IBM\WebSphere\\AppServer8\\profiles\\AppSrv01\\logs\\MyServer\\SystemOut.log"
but nothing wil be found.
Do i overlook something?
--
You received this message because you are subscribed to the Google Groups
12 matches
Mail list logo
