Re: [graylog2] Maximum Widget columns in Dashboard
Hello, I was trying to reproduce the issue and what I saw is that the number of dashboards is only calculated when the page is loaded, so if you make the window bigger you won't get any new columns. After a page reload you'll be able to see more columns, but that is not really obvious. As you were able to use more columns after deleting a widget (which trigger a page reload), I assume this is the issue you had. I have created this ticket to fix that issue: https://github.com/Graylog2/graylog2-web-interface/issues/1184 Regards, Edmundo On 24 Mar 2015, at 19:14, Phil Cohen pcmo...@gmail.com wrote: somehow, I fixed for myself...I deleted one of the widgets from the page and then was able to move to the top right for a 3rd column. Prior to this the same exact drag attempt was failing. On Tuesday, March 24, 2015 at 2:11:50 PM UTC-4, Phil Cohen wrote: Unfortunately, I am not observing the same behaviour - when I attempt to drag anything to the upper right I am locked to just two total columns. Please see attached screenshot, where I am attempting to drag the text widget up to the 'unlock' icon (as far to the top right as possible) with no possibility for more than two columns offered On Friday, March 20, 2015 at 6:48:26 AM UTC-4, Edmundo Alvarez wrote: Hi Phil, There is no limitation on the number of columns, only the screen resolution and the widget size. There was an issue reported for that a few days ago, maybe it can help you: https://github.com/Graylog2/graylog2-web-interface/issues/1139 Regards, Edmundo On 19 Mar 2015, at 21:12, Phil Cohen pcm...@gmail.com wrote: Hello, I am using Graylog 1.0.0 and have run into an odd limitation I cannot seem to make my dashboard more than two 'columns' wide - is this a known limitation in this version? screenshots from the documentation make it seem like it supports three. I have attached a screenshot that hopefully illustrates what I mean - I'd like to be using the grey space to the right. If I attempt to drag a widget in that direction, I do not get any representation of that as usable space. Thanks -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+u...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. Screen Shot 2015-03-19 at 4.10.35 PM.png -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Retention
Ok, I am still new to Graylog but am trying to setup a pilot system. I currently have 4 graylog servers setup, 1 configured as a server node, 2 configured as data nodes running just elasticsearch and a web interface node. I am trying to set my retention to a size of 5GB and 80 indices. I configured this on my Elasticsearch node using sudo graylog-ctl set-retention --size=5 and --indices=80, i think ran a reconfigure but this is not updating on on the website. It is still showing as 1GB and 10 indices. Am I doing something wrong? -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [graylog2] Retention
Hi, you have to set the retention on the server node. That should update the message in the web interface as well. On 25 March 2015 at 15:50, tslog...@outlook.com wrote: Ok, I am still new to Graylog but am trying to setup a pilot system. I currently have 4 graylog servers setup, 1 configured as a server node, 2 configured as data nodes running just elasticsearch and a web interface node. I am trying to set my retention to a size of 5GB and 80 indices. I configured this on my Elasticsearch node using sudo graylog-ctl set-retention --size=5 and --indices=80, i think ran a reconfigure but this is not updating on on the website. It is still showing as 1GB and 10 indices. Am I doing something wrong? -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. 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 Steckelhörn 11 20457 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 graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [graylog2] Retention
Thanks for the help!! That fixed the issue...so I am assuming that replicates down to the ElasticSearch servers. On Wednesday, March 25, 2015 at 11:41:45 AM UTC-4, Marius Sturm wrote: Hi, you have to set the retention on the server node. That should update the message in the web interface as well. On 25 March 2015 at 15:50, tslo...@outlook.com javascript: wrote: Ok, I am still new to Graylog but am trying to setup a pilot system. I currently have 4 graylog servers setup, 1 configured as a server node, 2 configured as data nodes running just elasticsearch and a web interface node. I am trying to set my retention to a size of 5GB and 80 indices. I configured this on my Elasticsearch node using sudo graylog-ctl set-retention --size=5 and --indices=80, i think ran a reconfigure but this is not updating on on the website. It is still showing as 1GB and 10 indices. Am I doing something wrong? -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+u...@googlegroups.com javascript:. 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 Steckelhörn 11 20457 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 graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] More Graylog/Elastic questions from the cheap seats
In looking at trying to increase the heap size today after a general overhaul of our logging system I was reminded about a few things I never seemed to get answers to in the past. Some of these statements are in fact questions. Setting mlockall in elasticsearch apparently does NOT set it for graylog? I can't seem to find a way to increase the heap size for the graylog index beyond 972MB. From the beginning I have wondered why I need the default elastic index (node with the dynamic naming) that never seems to be used, as well as the graylog index(node). The default elastic index seems to have all of the recommended tweaks (like mlockall), but the graylog index doesn't. Where exactly am I supposed to be changing them? Many times today on both of my graylog systems clicking on System:Nodes produces This exception has been logged with id 6libgij97.. I don't see any other issues. If I run curl http://localhost:9200/_nodes/process?pretty; when I look at the nodes parameters the graylog node is version 1.3.7 but the default node is 1.3.4 with different build numbers. More dumb questions to follow if I can remember them ;-) -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Re: [ANN] Graylog 1.0.1 has been released
Nice... BTW, I have been getting This exception has been logged with id 6libgij97. quite a bit today when I click on the nodes link. This is happening on both of my graylog servers. On Monday, March 16, 2015 at 8:00:44 AM UTC-7, Jochen Schalanda wrote: 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 API browser to new Graylog logo - Avoid spamming the logs if the original input of a message in the disk journal can't be loaded (#1005 https://github.com/Graylog2/graylog2-server/issues/1005) - Allows reader users to see the journal status (#1009 https://github.com/Graylog2/graylog2-server/issues/1009) - Compatibility with MongoDB 3.0 and Wired Tiger storage engine (#1024 https://github.com/Graylog2/graylog2-server/issues/1024) - Respect rest_transport_uri when generating entity URLs in REST API ( #1020 https://github.com/Graylog2/graylog2-server/issues/1020) - Properly map NodeNotFoundException (#1137 https://github.com/Graylog2/graylog2-web-interface/issues/1137) - Allow replacing all existing Grok patterns on bulk import (#1150 https://github.com/Graylog2/graylog2-web-interface/pull/1150) - Configuration option for discarding messages on error in AMQP inputs (#1018 https://github.com/Graylog2/graylog2-server/issues/1018) - Configuration option of maximum HTTP chunk size for HTTP-based inputs (#1011 https://github.com/Graylog2/graylog2-server/issues/1011 ) - Clone alarm callbacks when cloning a stream (#990 https://github.com/Graylog2/graylog2-server/issues/990) - Add hasField() and getField() methods to MessageSummary class (#923 https://github.com/Graylog2/graylog2-server/issues/923) - Add per input parse time metrics (#1106 https://github.com/Graylog2/graylog2-web-interface/issues/1106) - Allow the use of log4j-extras https://logging.apache.org/log4j/extras/ classes in log4j configuration (#1042 https://github.com/Graylog2/graylog2-server/issues/1042) - Fix updating of input statistics for Radio nodes (#1022 https://github.com/Graylog2/graylog2-web-interface/issues/1122) - Emit proper error message when a regular expression in an Extractor doesn't match example message (#1157 https://github.com/Graylog2/graylog2-web-interface/issues/1157) - Add additional information to system jobs (#920 https://github.com/Graylog2/graylog2-server/issues/920) - Fix false positive message on LDAP login test (#1138 https://github.com/Graylog2/graylog2-web-interface/issues/1138) - Calculate saved search resolution dynamically (#943 https://github.com/Graylog2/graylog2-web-interface/issues/943) - Only enable LDAP test buttons when data is present (#1097 https://github.com/Graylog2/graylog2-web-interface/issues/1097) - Load more than 1 message on Extractor form (#1105 https://github.com/Graylog2/graylog2-web-interface/issues/1105) - Fix NPE when listing alarm callback using non-existent plugin (#1152 https://github.com/Graylog2/graylog2-web-interface/issues/1152) - Redirect to nodes overview when node is not found (#1137 https://github.com/Graylog2/graylog2-web-interface/issues/1137) - Fix documentation links to integrations and data sources (#1136 https://github.com/Graylog2/graylog2-web-interface/issues/1136) - Prevent accidental indexing of web interface by web crawlers (#1151 https://github.com/Graylog2/graylog2-web-interface/issues/1151) - Validate grok pattern name on the client to avoid duplicate names ( #937 https://github.com/Graylog2/graylog2-server/issues/937) - Add message journal usage to nodes overview page (#1083 https://github.com/Graylog2/graylog2-web-interface/issues/1083) - Properly format numbers according to locale (#1128 https://github.com/Graylog2/graylog2-web-interface/issues/1128, #1129 https://github.com/Graylog2/graylog2-web-interface/issues/1129) Thanks to everyone who helped creating this release by using Graylog and reporting bugs and regressions to the mailing list and on GitHub. The official RPM and DEB packages, as well as the virtual machine images have been updated with the new version. As always, if you find any bugs in this release, please open an issue on GitHub at https://github.com/Graylog2/graylog2-server/issues. Best regards, Jochen (in the name of the Graylog team) -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [graylog2] [ANN] Graylog 1.0.1 has been released
Hey, You can get the system details from System - Nodes - Action - Details section. It gives the correct INFO about your system for example like this : Hostname:graylog.example.com Node ID:24d98657-bf45-4a77-aca7-511afd77a231Version:1.0.1 (e1b89b8) (*Jever* )JVM:PID 31749, Oracle Corporation 1.7.0_71 on Linux 2.6.32-504.8.1.el6.x86_64Time: 2015-03-26 01:54:44.760 +02:00 26 Mart 2015 Perşembe 00:19:51 UTC+2 tarihinde Mark Moorcroft yazdı: It was just a heads up. Thanks On Wed, Mar 25, 2015 at 3:09 PM, Henrik Johansen h...@myunix.dk javascript: wrote: AFAIK it’s a cosmetic issue caused by a mishap during the release of 1.0.1 - the web interface will report 1.0.0 even though it’s 1.0.1 … The dev’s (at least the ones I spoke to on IRC) are aware of this. On 25 Mar 2015, at 22:44, Peter Loron peter...@gmail.com javascript: wrote: I'm also seeing this. Glad I'm not going crazy... -Pete On Tuesday, March 24, 2015 at 8:19:01 PM UTC-7, Mark Moorcroft wrote: It still says 1.0.0 for graylog-web at the bottom of the interface despite yum reporting 1.0.1. FYI On Monday, March 16, 2015 at 8:00:44 AM UTC-7, Jochen Schalanda wrote: 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 API browser to new Graylog logo - Avoid spamming the logs if the original input of a message in the disk journal can't be loaded (#1005 https://github.com/Graylog2/graylog2-server/issues/1005) - Allows reader users to see the journal status (#1009 https://github.com/Graylog2/graylog2-server/issues/1009) - Compatibility with MongoDB 3.0 and Wired Tiger storage engine ( #1024 https://github.com/Graylog2/graylog2-server/issues/1024) - Respect rest_transport_uri when generating entity URLs in REST API (#1020 https://github.com/Graylog2/graylog2-server/issues/1020 ) - Properly map NodeNotFoundException (#1137 https://github.com/Graylog2/graylog2-web-interface/issues/1137) - Allow replacing all existing Grok patterns on bulk import (#1150 https://github.com/Graylog2/graylog2-web-interface/pull/1150) - Configuration option for discarding messages on error in AMQP inputs (#1018 https://github.com/Graylog2/graylog2-server/issues/1018) - Configuration option of maximum HTTP chunk size for HTTP-based inputs (#1011 https://github.com/Graylog2/graylog2-server/issues/1011) - Clone alarm callbacks when cloning a stream (#990 https://github.com/Graylog2/graylog2-server/issues/990) - Add hasField() and getField() methods to MessageSummary class ( #923 https://github.com/Graylog2/graylog2-server/issues/923) - Add per input parse time metrics (#1106 https://github.com/Graylog2/graylog2-web-interface/issues/1106) - Allow the use of log4j-extras https://logging.apache.org/log4j/extras/ classes in log4j configuration (#1042 https://github.com/Graylog2/graylog2-server/issues/1042) - Fix updating of input statistics for Radio nodes (#1022 https://github.com/Graylog2/graylog2-web-interface/issues/1122) - Emit proper error message when a regular expression in an Extractor doesn't match example message (#1157 https://github.com/Graylog2/graylog2-web-interface/issues/1157) - Add additional information to system jobs (#920 https://github.com/Graylog2/graylog2-server/issues/920) - Fix false positive message on LDAP login test (#1138 https://github.com/Graylog2/graylog2-web-interface/issues/1138) - Calculate saved search resolution dynamically (#943 https://github.com/Graylog2/graylog2-web-interface/issues/943) - Only enable LDAP test buttons when data is present (#1097 https://github.com/Graylog2/graylog2-web-interface/issues/1097) - Load more than 1 message on Extractor form (#1105 https://github.com/Graylog2/graylog2-web-interface/issues/1105) - Fix NPE when listing alarm callback using non-existent plugin ( #1152 https://github.com/Graylog2/graylog2-web-interface/issues/1152) - Redirect to nodes overview when node is not found (#1137 https://github.com/Graylog2/graylog2-web-interface/issues/1137) - Fix documentation links to integrations and data sources (#1136 https://github.com/Graylog2/graylog2-web-interface/issues/1136) - Prevent accidental indexing of web interface by web crawlers ( #1151 https://github.com/Graylog2/graylog2-web-interface/issues/1151) - Validate grok pattern name on the client to avoid duplicate names (#937 https://github.com/Graylog2/graylog2-server/issues/937) - Add message journal usage to nodes overview page (#1083 https://github.com/Graylog2/graylog2-web-interface/issues/1083) - Properly
[graylog2] Re: More Graylog/Elastic questions from the cheap seats
I'm not sure if it's considered a best practice to tweak the default /etc/sysconfig/graylog-server? GRAYLOG_SERVER_JAVA_OPTS=-Xms2g -Xmx2g -XX:NewRatio=1 -XX:PermSize=128m -XX:MaxPermSize=256m -server -XX:+ResizeTLAB -XX:+UseConcMarkSweepGC -XX:+CMSConcurrentMTEnabled -XX:+CMSClassUnloadingEnabled-XX:+UseParNewGC -XX:-OmitStackTraceInFastThrow But this at least seems to give you double the heap space. It's still not obvious how you should set mlockall. Or if I should even try. On Wednesday, March 25, 2015 at 7:31:38 PM UTC-7, Mark Moorcroft wrote: In looking at trying to increase the heap size today after a general overhaul of our logging system I was reminded about a few things I never seemed to get answers to in the past. Some of these statements are in fact questions. Setting mlockall in elasticsearch apparently does NOT set it for graylog? I can't seem to find a way to increase the heap size for the graylog index beyond 972MB. -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
