[graylog2] Re: GeoIp lookup plugin

Hi, As far as I know it is not there yet, but kind of work in progres:https://graylog.ideas.aha.io/ideas/GL2E-I-364 Make s me think about the fact that elasticsearch itself has spacial geo fields fields built in it. On Monday, December 7, 2015 at 10:51:09 PM UTC+1, Raj Tanneru wrote: > > Hi,

[graylog2] Re: Shards and diskspace

> You could use a plugin like ELASTICHQ for elastic to have a better look at > what your ES servers are doing. > > Sounds great, but when I run: sudo bin/plugin --install http://github.com/royrusso/elasticsearch-HQ sudo bin/plugin --install royrusso/elasticsearch-HQ sudo bin/plugin

[graylog2] Re: Shards and diskspace

You might have to give the complete path to the plugin command. /usr/share/elasticsearch/bin/plugin . On Thursday, December 10, 2015 at 9:52:15 AM UTC+1, Per Erik Nordlien wrote: > > > > >> You could use a plugin like ELASTICHQ for elastic to have a better look >> at what your ES servers

Re: [graylog2] Re: GeoIp lookup plugin

On 10/12/15 23:03, Arie wrote: > As far as I know it is not there yet, but kind of work in > progres:https://graylog.ideas.aha.io/ideas/GL2E-I-364 That's not the case: the graylog staff have said there are no plans to implement this - and that ticket should actually be closed :-( (see "what can I

[graylog2] Problems using signed certificates in TLS input

Hi, I'm configuring NXLog to transport log data with TLS to Graylog. This works if I use the selfsigned certificate created by Graylog. But if I use our signed certificate I get these errors: 2015-12-10 10:31:38 INFO remote socket was closed during SSL handshake 2015-12-10 10:31:38 INFO

[graylog2] Re: Problems using signed certificates in TLS input

BTW: I'm using a wildcard certificate. -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. To view this discussion on the

[graylog2] "HTTP 415 Unsupported Media Type" when creating a token in API browser

Hi, I'm trying to create a API token using the API browser: http://logging.host.com:12900/api-browser#!/Users/generateNewToken_post_10 It fails with this response: Response Code: 415 Response Body { "type": "ApiError", "message": "HTTP 415 Unsupported Media Type" } API version is 1.3.0

[graylog2] Re: Upgrade from 1.2 to 1.3 yum

hahahaha I asked the same question, two minutes before. On Thursday, December 10, 2015 at 3:16:40 PM UTC-2, cmuench wrote: > > Hello, > first of great product guys. Graylog is awesome. I installed it via the > RPM on centos6. I was wondering what is the best step for me to do an > in-place

[graylog2] IllegalArgumentException: Invalid (date) format - malformed

Hey there, Ive got a big issue with malformed date format, so the nginx extractor is rejecting incoming messages and the dashboards are empty. My setup: Debian 7.9 graylog-server 1.3.0-3 graylog-web 1.3.0-3 java 1.8.0.66 In the nginx site of my webserver I configured this log_format:

[graylog2] Re: Graylog-server REST API returning incorrect results for /search/universal/keyword

NEVERMIND! I had to use -H 'Accept:application/json' instead On Thursday, December 10, 2015 at 10:41:04 AM UTC-6, Drew Miranda wrote: > > I should note, accessing directly from rest API page does work correctly, > but curl does not. > > On Thursday, December 10, 2015 at 10:40:22 AM UTC-6, Drew

[graylog2] Upgrade from 1.2 to 1.3 yum

Hello, first of great product guys. Graylog is awesome. I installed it via the RPM on centos6. I was wondering what is the best step for me to do an in-place upgrade from 1.2 to 1.3 using the RPM? I do a yum update and it doesn't find anything because I don't have those 1.3 packages yet..

[graylog2] Update Graylog 1.2 -> 1.3 via repositories

Hi, I have a Graylog 1.2 server running on a CentOS 7. The installation is done with yum in the official Graylog repositories. I would like to upgrade to 1.3, but I found no information on updating in the official documentation and I think: And if I change the /etc/yum.repos.d/graylog.repo

[graylog2] Re: Update Graylog 1.2 -> 1.3 via repositories

Hi Emerson I did the upgrade through YUM and graylog-server crash on start with the following error : https://paste.fedoraproject.org/299624/44977323/ So, i'm following this thread to see if someone knows the right path to do the upgrade (or fix my error) Regards Luciano On Thursday,

[graylog2] Elasticsearch keeps hanging in current VM/Docker images

I've been trying to get Graylog running stable for a couple weeks now, using Ubuntu Trusty and the latest Vagrant, Virtualbox and Docker on different hardware and all have the same problem. The first symptom is that eventually the login page says it failed with error 500 as in Joseph John's

Re: [graylog2] Re: graylog-ctl is parsing --time incorrectly

Well I just updated the Vagrant box to 1.3 and it seems to work now. I'll see how it goes. On Thu, Dec 3, 2015 at 12:15 PM, Jochen Schalanda wrote: > Hi Michael, > > what command (including all parameters) are you executing exactly? > > > Cheers, > Jochen > > On Thursday, 3

[graylog2] Graylog-server REST API returning incorrect results for /search/universal/keyword

I'm using /search/universal/keyword to check if the last 10 minutes contain any indexed messages for aboslute time ranges. Before upgrading to 1.3.0 (on 1.2.2) this returned the JSON object which does not require specifying return fields. However, after upgrading to 1.3.0 it ONLY returns the

[graylog2] Re: Graylog-server REST API returning incorrect results for /search/universal/keyword

I should note, accessing directly from rest API page does work correctly, but curl does not. On Thursday, December 10, 2015 at 10:40:22 AM UTC-6, Drew Miranda wrote: > > I'm using /search/universal/keyword to check if the last 10 minutes > contain any indexed messages for aboslute time ranges.