Re: [graylog2] 404 Error at Login
Hi Jochen, I have the same problem: Error - the server returned: 404 - cannot POST https://graylog.example.com/system/sessions (404) I use a proxypass rule for https. My conf is: server.conf rest_listen_uri = http://graylog01.internal.net:12900/ #rest_transport_uri = http://graylog.example.com:12900/ web_listen_uri = http://graylog01.internal.net:9000/ web_endpoint_uri = https://graylog.example.com:9000/api/ SSL conf file RequestHeader set X-Forwarded-Proto "https" RequestHeader set X-Forwarded-Port "443" RequestHeader set X-Graylog-Server-URL "https://graylog.example.com:12900/; ServerName graylog.example.com ProxyPass / http://172.31.20.211:9000/ ProxyPassReverse / http://172.31.20.211:9000/ ProxyRequests Off SSLEngine on SSLCertificateFile /etc/ssl/certs/example.com.crt SSLCertificateKeyFile /etc/ssl/private/example.com.key SSLCertificateChainFile /etc/ssl/certs/gd_bundle-g2-g1.crt http://172.31.20.211:9000/> Order deny,allow Allow from all Any idea how to fix it? Thanks Tony Il giorno lunedì 29 agosto 2016 18:24:39 UTC+1, Jochen Schalanda ha scritto: > > Hi Dave, > > the rest_transport_uri setting and the rest_listen_uri setting you've > chosen are incompatible. > > I'd recommend setting only rest_listen_uri to your public IP address and > using the default for rest_transport_uri (i. e. remove your own setting). > > Cheers, > Jochen > > Am 29.08.2016 um 17:42 schrieb Dave <dca...@swillers.com >: > > Hello, > > I'm trying to stand up Graylog on a RHEL 7 VM. The webui is throwing this > error when I attempt to authenticate: > "Error - the server returned: 404 - cannot POST > http://:12900/system/sessions > (404)" > > System info: > >- RHEL 7.2 >- Graylog 2.1.0-8.rc.1 >- Elasticsearch 2.3.5-1 >- MongoDB 3.2.9-1 > > Config: > > is_master = true > node_id_file = /etc/graylog/server/node-id > password_secret = > root_password_sha2 = > root_timezone = America/New_York > plugin_dir = /usr/share/graylog-server/plugin > rest_listen_uri = http://0.0.0.0:12900/api/ > rest_transport_uri = http://:12900/ > trusted_proxies = 127.0.0.1/32, > web_listen_uri = http://0.0.0.0:9000/ > rotation_strategy = count > elasticsearch_max_docs_per_index = 2000 > rotation_strategy = count > elasticsearch_max_docs_per_index = 2000 > elasticsearch_max_number_of_indices = 20 > retention_strategy = delete > elasticsearch_max_number_of_indices = 20 > retention_strategy = delete > elasticsearch_shards = 4 > elasticsearch_replicas = 0 > elasticsearch_index_prefix = graylog > allow_leading_wildcard_searches = false > allow_highlighting = false > elasticsearch_analyzer = standard > output_batch_size = 500 > output_flush_interval = 1 > output_fault_count_threshold = 5 > output_fault_penalty_seconds = 30 > processbuffer_processors = 5 > outputbuffer_processors = 3 > processor_wait_strategy = blocking > ring_size = 65536 > inputbuffer_ring_size = 65536 > inputbuffer_processors = 2 > inputbuffer_wait_strategy = blocking > message_journal_enabled = true > message_journal_dir = /var/lib/graylog-server/journal > lb_recognition_period_seconds = 3 > mongodb_uri = mongodb://localhost/graylog > mongodb_max_connections = 1000 > mongodb_threads_allowed_to_block_multiplier = 5 > content_packs_dir = /usr/share/graylog-server/contentpacks > content_packs_auto_load = grok-patterns.json > > > Any ideas? > > > Thanks, > > > --Dave > > -- > 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+u...@googlegroups.com . > To view this discussion on the web visit > https://groups.google.com/d/msgid/graylog2/04cfbadc-5b5f-43ef-8b61-402dd40edca0%40googlegroups.com > > <https://groups.google.com/d/msgid/graylog2/04cfbadc-5b5f-43ef-8b61-402dd40edca0%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > -- 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 web visit https://groups.google.com/d/msgid/graylog2/f4292acc-091a-4e12-94b9-0a988473c012%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [graylog2] Different color for different status
Thank you for your answer Jan, but to be honest I don't really know how to do that with decorators. As you can see in the screenshot the lines already comes with the ANSI escape color sequence but are shown in cyan on Graylog. Thanks Tony 2016-09-18 11:51 GMT+01:00 Jan Doberstein <j...@jalogisch.de>: > Hi Tony, > > I have a question. Is it possible have different color for different entry > status in Tomcat log files? > For example when I watch the log files in Graylog (Messages) all entries > are blue and is difficult identify in real time any error or warn, which is > possible with tail -f in a console terminal. So I would like to see Yellow > for Warn, Red for Error, Green for INFO. > Is it possible? > > I guess that the Message Decorators are what you are looking for: > http://docs.graylog.org/en/2.1/pages/queries.html#decorators > > For the use case you described I did not know a ready to use decorator, > but you should be able to create your own. > > > with kind regards > > Jan > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Graylog Users" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/graylog2/OYykXsjzobU/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > graylog2+unsubscr...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/graylog2/etPan.57de71b2.56a95827.3a1%40jalogisch.de > <https://groups.google.com/d/msgid/graylog2/etPan.57de71b2.56a95827.3a1%40jalogisch.de?utm_medium=email_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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 web visit https://groups.google.com/d/msgid/graylog2/CACjATf-apJmA5Zm6FcQ2GuN0A947QSvO27rSuB2vQkg_fMZS7w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [graylog2] Re: Weird Stream behaviour
Thank you Jochen to Highlight me :-) Now it works. Thanks Tony 2016-09-21 11:06 GMT+01:00 Jochen Schalanda <joc...@graylog.com>: > Hi Tony, > > your last post is missing the important part: Are the stream rules > evaluated with logical AND (all rules have to match) or logical OR (only > one rule has to match). > > Additionally, your second rule, "message field must match exactly WARN" > is wrong, as the message field clearly does not only contain the word > "WARN". You can either use a regular expression to match the message > field or extract that word into a separate field. > > Cheers, > Jochen > > On Wednesday, 21 September 2016 00:06:53 UTC+2, Tony wrote: >> >> Hi Jochen, >> thank you for your answer and help. In the first screenshot I capture >> from the field debug_level the word INFO and it works. >> The second is supposed to capture the word WARN from the field message >> and doesn't work. The third screenshot is the message line. >> >> Thanks >> >> Tony >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "Graylog Users" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/graylog2/61L7jHB8jok/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > graylog2+unsubscr...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/graylog2/213a75cf-28d3-43cb-90b9-7b5225080307%40googlegroups.com > <https://groups.google.com/d/msgid/graylog2/213a75cf-28d3-43cb-90b9-7b5225080307%40googlegroups.com?utm_medium=email_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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 web visit https://groups.google.com/d/msgid/graylog2/CACjATf-WotDW_qiqs-72xZHQ5FzQ9XUzXYz7UO02k8DXkDECKg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Re: Weird Stream behaviour
Sorry small errata corrige: Than I made another one with field = message match exactly = DEBUG and doesn't work nothing is catchup, even in the message field DEBUG is present. Il giorno martedì 20 settembre 2016 15:54:06 UTC+1, Tony ha scritto: > > Hi All, > I'll try to create a stream and the callback alert, but I have a problem. > First test stream field = debug_level match exactly = INFO and it works > 100% Than I made another one with field = message match exactly = WARN (or > INFO or whatever) and doesn't work nothing is catchup. > > Annexe a screenshot. The logs are Tomcat logs files. > > Any help please? > > Thanks > -- 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 web visit https://groups.google.com/d/msgid/graylog2/ecf903c6-9029-4267-9abf-dabdcf6622a8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] geolocation problem
Hi All, I have some trouble with the geoloc feature in Graylog with apache2 log files. When I click on World map got the error in the picture. I had already installed the city DB and GeoIP resolver is in the last position. I run Graylog 2.1 + Collector-sidecar and Nxlog. Any suggestion? Thanks in advance Tony -- 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 web visit https://groups.google.com/d/msgid/graylog2/f7dab284-9b45-451b-8f29-4c9b40b7ce61%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Different color for different status
Hi All. I have a question. Is it possible have different color for different entry status in Tomcat log files? For example when I watch the log files in Graylog (Messages) all entries are blue and is difficult identify in real time any error or warn, which is possible with tail -f in a console terminal. So I would like to see Yellow for Warn, Red for Error, Green for INFO. Is it possible? Thanks in advance Tony -- 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 web visit https://groups.google.com/d/msgid/graylog2/ed1c764e-d8f0-47de-9c01-828a87809c86%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [graylog2] NXLOG
Thank you Marius. Il giorno venerdì 9 settembre 2016 13:00:19 UTC+1, Marius Sturm ha scritto: > > Hi Tony, > nxlog is not included in the collector-sidecar package, so if you want to > use the nxlog backend you have to install it along with sidecar. > > Cheers, > Maris > > > On 9 September 2016 at 13:04, Tony <anes...@gmail.com > > wrote: > >> Hi Guys, >> I have a question. Is it necessary nxlog installation for >> collector-sidecar? My environments are Debian 7/8 and use Graylog 2, ES and >> MongoDB. >> >> Thanks >> >> Tony >> >> -- >> 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+u...@googlegroups.com . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/graylog2/0af6f4e6-b0c5-4fd5-8f00-a7333975514d%40googlegroups.com >> >> <https://groups.google.com/d/msgid/graylog2/0af6f4e6-b0c5-4fd5-8f00-a7333975514d%40googlegroups.com?utm_medium=email_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Developer > > Tel.: +49 (0)40 609 452 077 > Fax.: +49 (0)40 609 452 078 > > TORCH GmbH - A Graylog Company > Poolstraße 21 > 20335 Hamburg > Germany > > https://www.graylog.com <https://www.torch.sh/> > > Commercial Reg. (Registergericht): Amtsgericht Hamburg, HRB 125175 > Geschäftsführer: Lennart Koopmann (CEO) > -- 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 web visit https://groups.google.com/d/msgid/graylog2/edac90d1-6953-4286-a3b7-93277a192197%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] NXLOG
Hi Guys, I have a question. Is it necessary nxlog installation for collector-sidecar? My environments are Debian 7/8 and use Graylog 2, ES and MongoDB. Thanks Tony -- 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 web visit https://groups.google.com/d/msgid/graylog2/0af6f4e6-b0c5-4fd5-8f00-a7333975514d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [graylog2] Re: Cannot Configure Collector Inputs
Thank you Marius, everything works well. 2016-07-27 9:54 GMT+01:00 Marius Sturm <mar...@graylog.com>: > Hi Tony, > the collector option is implemented as a plugin. So please check in your > server configuration the plugin_dir directive and that the collector plugin > is actually located in that directory. > > > Cheers, > Marius > > > On 26 July 2016 at 18:32, Tony <anesp...@gmail.com> wrote: > >> Hi Marius, >> sorry to resume this post, but I have a problem in Graylog 2.0 server I >> installed it on Debian 8 by repository and following this procedure: >> http://docs.graylog.org/en/2.0/pages/installation/operating_system_packages.html >> unfortunately I wanna to collect logs from a remote apache server using >> graylog-collector-sidecar but in the Graylog server I don't find the >> Collector choice in System menu. Any ida to help me please? >> >> Thanks >> >> Tony >> >> -- >> 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 web visit >> https://groups.google.com/d/msgid/graylog2/b484a3e2-4413-4201-8078-aff336a51fa2%40googlegroups.com >> <https://groups.google.com/d/msgid/graylog2/b484a3e2-4413-4201-8078-aff336a51fa2%40googlegroups.com?utm_medium=email_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Developer > > Tel.: +49 (0)40 609 452 077 > Fax.: +49 (0)40 609 452 078 > > TORCH GmbH - A Graylog Company > Poolstraße 21 > 20335 Hamburg > Germany > > https://www.graylog.com <https://www.torch.sh/> > > Commercial Reg. (Registergericht): Amtsgericht Hamburg, HRB 125175 > Geschäftsführer: Lennart Koopmann (CEO) > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Graylog Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/graylog2/Matz1rRHBgU/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > graylog2+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/graylog2/CAMqbBbLZTN_RE17N8vSnyVXGhDTr%2BU-fQ2k_5LG62u-z0mm6Ew%40mail.gmail.com > <https://groups.google.com/d/msgid/graylog2/CAMqbBbLZTN_RE17N8vSnyVXGhDTr%2BU-fQ2k_5LG62u-z0mm6Ew%40mail.gmail.com?utm_medium=email_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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 web visit https://groups.google.com/d/msgid/graylog2/CACjATf8K5M1L95GFk8fBYr2DyAg0YVSUoNmVhctT0bBspaJJ%3DQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Re: Cannot Configure Collector Inputs
Hi Marius, sorry to resume this post, but I have a problem in Graylog 2.0 server I installed it on Debian 8 by repository and following this procedure: http://docs.graylog.org/en/2.0/pages/installation/operating_system_packages.html unfortunately I wanna to collect logs from a remote apache server using graylog-collector-sidecar but in the Graylog server I don't find the Collector choice in System menu. Any ida to help me please? Thanks Tony -- 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 web visit https://groups.google.com/d/msgid/graylog2/b484a3e2-4413-4201-8078-aff336a51fa2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] graylog-collector-sidecar issue
Hello everybody,
I would like to send my apache2 log files from a remote server to graylog
server. Actually I using graylog-collector-sidecar on Debian 7 and my
configuration files are:
collectoe_sidecar.yaml---
erver_url: http://10.5.10.242:12900
node_id: graylog-collector-sidecar-nagios
collector_id: file:/etc/graylog/collector-sidecar/collector-id
log_rotation_time: 86400
log_max_age: 86400
tags: apache
update_interval: 10
log_path: /var/log/graylog/collector-sidecar
backends:
- name: nxlog
enabled: true
binary_path: /usr/bin/nxlog
configuration_path:
/etc/graylog/collector-sidecar/generated/nxlog.conf
---nxlog.conf---
User nxlog
Group nxlog
Moduledir /usr/lib/nxlog/modules
CacheDir /var/spool/collector-sidecar/nxlog
PidFile /var/run/graylog/collector-sidecar/nxlog.pid
define LOGFILE /var/log/graylog/collector-sidecar/nxlog.log
LogFile %LOGFILE%
LogLevel INFO
Module xm_fileop
When@daily
Execfile_cycle('%LOGFILE%', 7);
---
This is the tree output
/etc/graylog/collector-sidecar$ tree
.
├── collector-id
├── collector_sidecar.yml
└── generated
└── nxlog.conf
So now when I try to do graylog-collector-sidecar -c
/etc/graylog/collector-sidecar/collector_sidecar.yml
I got this
INFO[] Using collector-id: e3d0fefc-f8fd-4f4e-becd-894d7f813532
INFO[] Fetching configurations tagged by: [apache]
INFO[] Starting collector supervisor
INFO[] [nxlog] Starting
INFO[0010] [RequestConfiguration] No configuration found for configured
tags!
INFO[0020] [RequestConfiguration] No configuration found for configured
tags!
INFO[0030] [RequestConfiguration] No configuration found for configured
tags!
But I see the instance in collectors in graylog server.
Any idea how to fix it?
Thanks in advance
Tony
--
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 web visit
https://groups.google.com/d/msgid/graylog2/27703308-3fe9-4a3f-8576-d54b70e2beaf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [graylog2] Re: Graylor-collector for Debian 7
Thank you Jochen, very appreciate Cheers, Tony 2016-07-22 12:43 GMT+01:00 Jochen Schalanda <joc...@graylog.com>: > Hi Tony, > > there currently aren't any DEB packages for the Graylog Collector working > on Debian 7. > > You can still download and install the official binaries from > https://github.com/Graylog2/collector#binary-download and make your init > system start it on boot. > > This being said, a working SysV init script for the Graylog Collector for > operating systems like Debian Wheezy as a pull request to the > https://github.com/Graylog2/fpm-recipes/ repository would be more than > welcome! > > Cheers, > Jochen > > On Thursday, 21 July 2016 18:49:37 UTC+2, Tony wrote: >> >> Hello everybody, >> I would like to install in several production servers graylog-collector >> using puppet. The problem is I don't found anymore package for Debian 7 >> only Debian 8. Unfortunately I can't upgrade all production servers to >> Debian 8 for a while. >> Thanks in advance for your help. >> >> Tony >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "Graylog Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/graylog2/WgxBZ_vYIhw/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > graylog2+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/graylog2/2a970fa9-331c-44c5-b030-e321b049bebe%40googlegroups.com > <https://groups.google.com/d/msgid/graylog2/2a970fa9-331c-44c5-b030-e321b049bebe%40googlegroups.com?utm_medium=email_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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 web visit https://groups.google.com/d/msgid/graylog2/CACjATf84NKVFpO_a0afo4srFRM2tvZvyB7yBrBQbrrUsVGJHcQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Graylor-collector for Debian 7
Hello everybody, I would like to install in several production servers graylog-collector using puppet. The problem is I don't found anymore package for Debian 7 only Debian 8. Unfortunately I can't upgrade all production servers to Debian 8 for a while. Thanks in advance for your help. Tony -- 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 web visit https://groups.google.com/d/msgid/graylog2/8348c889-009e-40f4-b7c0-bc9fee852b58%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Re: Graylog Use with SQL Server 2014
I too have numerous SQL Server installations and would like to hear about these options as well. On Friday, June 10, 2016 at 11:46:37 AM UTC-7, matt.k...@fivestarprofessional.com wrote: > > Hello, > > Does anyone have experience setting up Graylog for use with SQL Server > 2014 logs? > > Best practices/issues you encountered would be extremely helpful! > -- 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 web visit https://groups.google.com/d/msgid/graylog2/6ffe6297-c9a2-4855-8d9e-17faefd078e5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Re: Has anyone tried systemd socket activation for 514?
Good suggestions, not exactly what I asked, but thanks I'll probably use iptables for now. -- 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 web visit https://groups.google.com/d/msgid/graylog2/646babee-e8e2-40dc-b15a-7f7335c74f06%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Has anyone tried systemd socket activation for 514?
So we could run graylog as a non-root user. -- 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 web visit https://groups.google.com/d/msgid/graylog2/52190def-a19a-4fd8-a0a7-5f13ae9d156b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
