No one?
bumping in case it got overlooked over the weekend.
Thanks
On Friday, November 18, 2016 at 1:54:59 PM UTC-5, 123Dev wrote:
>
> Let me first explain what we're trying to achieve with a practical example
> to see if there is a way to achieve it without creating multiple s
Let me first explain what we're trying to achieve with a practical example
to see if there is a way to achieve it without creating multiple streams
with identical rules.
Example Stream:
Let's keep it simple
Messages that include Error 500
Alert
Triggered for every message that shows up in this
Thanks Marius,
Appreciate the update.
On Friday, November 11, 2016 at 4:48:34 PM UTC-5, Marius Sturm wrote:
>
> Hi,
> current not but we are working on a restart action.
>
> Cheers,
> Marius
>
> On 11 November 2016 at 19:25, 123Dev >
> wrote:
> >
Quite often, when there is a network disruption, nxlog (which is controlled
and started by graylog-collector) stops sending data.
We can detect this through Graylog Stream alerts.
Restarting nxlog on the remote nodes fixes the issues.
We achieve this by making a Collector configuration change, sp
5 minute" query.
>
> On Wednesday, November 2, 2016 at 12:08:34 PM UTC-4, 123Dev wrote:
>>
>> Thanks for the follow up
>> Although our symptoms are the same, probably the root causes are
>> different.
>>
>> In our case, our ES never goes red (not ev
> routines. The query analyzer is excluding yesterday's index when in fact
> that is the one that has the events we're looking for. Doing anything to
> trick the query analyzer into including that index makes the query start
> succeeding.
>
> On Tuesday, Novem
: Delete
Max number of indices:28
So all of the current data should be present in the latest index for 24
hours, why isn't Graylog able to find it, it's not like it is changing.
On Tuesday, November 1, 2016 at 1:07:06 PM UTC-4, 123Dev wrote:
>
> I've been pulling my hai
lting.com wrote:
>
> Surprisingly, I ran into this issue this morning as well. After some
> poking around I found that my current index time ranges hadn't been updated
> in 15 hours, which I assume was breaking the logic used to select indices
> for searching. In System -> In
Was this ever resolved.
i never had this issue, and been running Graylog for a long time.
Just today with the latest Graylog (2.1.1)
Search * for Last, 5m 15m, 30m, 1hr don't return and results
Search * in the last 2 hours returns messages just few seconds ago,
This is across the board, in a clust
Although the Web Interface is not exhibiting any issues, I noticed the
following error in the developer console.
webpack:
///../graylog2-server/graylog2-web-interface/src/stores/nodes/NodesStore.js
Uncaught TypeError: (0 , l.default)(...).then(...).finally is not a function
NodesStore.js:
post the complete Graylog configuration file and the complete
> Graylog log file.
>
> Are there additionally any error messages in the Developer Console
> <https://developers.google.com/web/tools/chrome-devtools/> of your web
> browser when opening http://10.20.2.75:9000/api/?
I should also point out that we're not running behind a reverse proxy and
this is a single node server with ES and MongoDB running on the same server.
--
You received this message because you are subscribed to the Google Groups
"Graylog Users" group.
To unsubscribe from this group and stop rec
Just upgraded to graylog-2.1.0-rc.1 using graylog-2.1.0-rc.1.tgz
Web Interface does not come up on http://:9000
however API endpoint http://http://10.20.2.75:9000/api/
Graylog log doesn't show any errors
Any idea what it might be.
I'll turn off some of the plugins that were enabled in 2.0.2 an
Thanks Jochen,
On Friday, August 26, 2016 at 3:19:54 AM UTC-4, Jochen Schalanda wrote:
>
> Hi,
>
> On Thursday, 25 August 2016 23:33:54 UTC+2, 123Dev wrote:
>>
>> Or is it simply following these steps.
>>
>> http://docs.graylog.org/en/latest/pages/configurat
Awesome, thanks for all the great work.
Would like to know if there are any special upgrade instructions from 2.0.3
to 2.1, specifically for an AWS image that was upgraded from 1.x to 2.0 by
following the AWS upgrade steps.
Or is it simply following these steps.
http://docs.graylog.org/en/latest
e are simply
> lacking real world examples, much appreciated!
>
> Cheers,
> Marius
>
>
> On 19 July 2016 at 20:03, 123Dev >
> wrote:
>
>> Thanks Marius for the explanation, and totally understand that the
>> solution needs to be scalable and needs to a
Thanks Marius for the explanation, and totally understand that the solution
needs to be scalable and needs to address equally the small and big
deployments.
Before Graylog Sidecar, all our client machines that were running nxlog,
each and every one of them had their own configuration locally st
Agreed, the tag is confusing to us too.
On Graylog, if I have 3 configurations.
- Config1 - tag1
- Config2 - tag2
- Config3 - tag3
On the collector side, I was wrongly expecting that if I set tag1 and tag2,
the client would get both configurations.
But that didn't work
Because each c
Thanks Jan,
This is awesome news, can't wait for the next release :)
Certainly we will submit all our findings to help make this great product
even better.
Thanks
On Tuesday, July 5, 2016 at 3:20:24 AM UTC-4, Jan Doberstein wrote:
>
> Hej,
>
>
> On 4. Juli 2016 at
11 AM UTC-4, Jan Doberstein wrote:
>
> Hej
>
>
> On 30. Juni 2016 at 16:09:28, 123Dev (hr...@123loadboard.com )
> wrote:
> > REST API access part is a bit flaky and I agree it can benefit from
> better
> > documentation / code, but Graylog folks have always been
That is not true,
We have AWS image based deployment (2 graylog servers, 2 datanodes)
(production) and one manual install (staging) all working in AWS.
REST API access part is a bit flaky and I agree it can benefit from better
documentation / code, but Graylog folks have always been proactive an
The server that I set up, does not have that file.
Which file are you referring to?
nginx.conf or graylog.conf?
Yet you mention the setting, so where are you reading this setting?
How did you setup the Graylog server? from an AWS image?
then you should have the file.
If this is your first experi
Why is it that the server cannot access the public address?
what is the value of *rest_listen_uri* in */opt/graylog/conf/graylog.conf*
have you tried binding to 0.0.0.0:12900
what is the value of *proxy_set_header X-Graylog-Server-URL* in
*/opt/graylog/conf/nginx/nginx.conf*
Is it $host or your
erver issue per se.
>
> Thanks,
> Marius
>
> On 23 June 2016 at 16:06, 123Dev >
> wrote:
>
>> Found the offending code.
>>
>> /opt/graylog/service/graylog-server/run
>>
>> Hardcoded mongodb to be localhost, even though graylog.conf has it set to
>&
Found the offending code.
/opt/graylog/service/graylog-server/run
Hardcoded mongodb to be localhost, even though graylog.conf has it set to
the primary mongodb.
#!/bin/sh
exec 2>&1
umask 077
if [ -f "/opt/graylog/embedded/share/graylog/installation-source.sh" ]; then
. "/opt/graylog/embed
Thanks Jan,
To answer your questions.
> did you check your /etc/hosts for this IP?
>
Not sure what you want me to check? confirm that it has a hostname defined?
Server 1
ubuntu@graylog-server1:~/bak$ cat /etc/hosts
127.0.0.1 localhost
# The following lines are desirable for IPv6 capable hosts
0 0 - 2615 pipe_w 14:13 pts/000:00:00
grep --color=auto 12919
>
> with kind regards
> Jan
>
> --
> | -
> | get trusted and secure VPN services http://jalogis.ch/vpnsh
>
> On 17.
We've upgraded our production system (AWS images) from 1.3.x to 2.0.2
On the primary server the Graylog Server is fully operational
Whereas on the secondary server, the process is running (or it seems), but
it's not writing anything to the logs and it does not appear in the UI as a
node.
On
ticsearch can be reached by anyone
>
> If you want to create your own customised setup take a look at our other
> installation methods
> <http://docs.graylog.org/en/2.0/pages/installation.html#installing>.
>
On Monday, June 13, 2016 at 3:32:53 AM UTC-4, Jochen Schalanda wrot
Just like Pasqual,
*graylog-ctl enforce-ssl *is not setting the REST transport on HTTPS
In our case API browser is on: http://10.20.1.229:12900/api-browser and is
accessible
If I try to check if it is also accessible on SSL,
https://10.20.1.229:12900/api-browser *it fails*
Would be nice if *en
Or you could track it in each application, in addition to injecting
correlation_id to Graylog messages, you can also inject elapsed_time.
This gives you a better view of your application performance, unless of
course you are trying to track all the way to Graylog.
We also add task sequence numbe
Thanks Jochen for quick response.
I look forward to the manual upgrade documentation.
Would you drop a note here when that is ready or if there is any page I can
monitor, it would be great.
Thanks
On Friday, April 29, 2016 at 10:54:40 AM UTC-4, 123Dev wrote:
>
> Hi Jochen,
>
> A
Hi Jochen,
Any advice on upgrading AWS image based 1.3 deployment to 2.0?
The cluster is made of two Graylog Servers, two datanode servers and one
web portal (ES running on Graylog Servers and Datanode Servers, MongoDB
running on GS Servers).
Should one be upgrading ES and MongoDB on each insta
33 matches
Mail list logo
