Re: [graylog2] [ANN] Graylog 1.0.1 has been released

2015-03-25 Thread Aydin Doyak
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 

Re: [graylog2] How to define default streams on a reader role in Graylog v1.0.0

2015-03-23 Thread Aydin Doyak
Thank you for your Edmundo,

I'll be tracking the issue.

Regards,

Aydin

23 Mart 2015 Pazartesi 11:34:30 UTC+2 tarihinde Edmundo Alvarez yazdı:

 Hi, 

 This is not possible in Graylog at the moment. You can track this issue to 
 know when we make some progress on this feature: 
 https://github.com/Graylog2/graylog2-web-interface/issues/437 

 Regards, 
 Edmundo 

 -- 
 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 

 Commercial Reg. (Registergericht): Amtsgericht Hamburg, HRB 125175 
 Geschäftsführer: Lennart Koopmann (CEO) 

  On 23 Mar 2015, at 09:15, Aydin Doyak ayd...@gmail.com javascript: 
 wrote: 
  
  Any thoughts? 
  
  20 Mart 2015 Cuma 00:25:36 UTC+2 tarihinde Pete GS yazdı: 
  I can't help with a solution but I'll add a +1 to the request as I have 
 exactly the same issue. 
  
  Cheers, Pete 
  
  On Thursday, 19 March 2015 08:17:56 UTC+10, Aydin Doyak wrote: 
  Hey, 
  
  I have a graylog v1.0.0 running on centos 6.6 like a charm. 
  
  I have several stream and dashboard definitions in my server and i 
 manage my graylog users with ldap integration which works great. 
  
  But i've a question : 
  
  When my ldap users login at the first time, graylog doesnt let them to 
 see any stream or dashboards because all ldap users come with the default 
 reader permissions which is normal. 
  
  I'd like to define some default streams and dashboards for reader 
 permission, and make all users allow to see those streams default. 
  
  Is there anyway to do that? I do not want to give admin permission to 
 everyone and i dont want to set permissions one by one for all the users. 
  
  What do you guys suggest? 
  
  Any help or answers will be appreciated, 
  
  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 javascript:. 
  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] Re: How to define default streams on a reader role in Graylog v1.0.0

2015-03-23 Thread Aydin Doyak
Any thoughts?

20 Mart 2015 Cuma 00:25:36 UTC+2 tarihinde Pete GS yazdı:

 I can't help with a solution but I'll add a +1 to the request as I have 
 exactly the same issue.

 Cheers, Pete

 On Thursday, 19 March 2015 08:17:56 UTC+10, Aydin Doyak wrote:

 Hey, 

 I have a graylog v1.0.0 running on centos 6.6 like a charm. 

 I have several stream and dashboard definitions in my server and i manage 
 my graylog users with ldap integration which works great.

 But i've a question :

 When my ldap users login at the first time, graylog doesnt let them to 
 see any stream or dashboards because all ldap users come with the default 
 reader permissions which is normal.

 I'd like to define some default streams and dashboards for reader 
 permission, and make all users allow to see those streams default.

 Is there anyway to do that? I do not want to give admin permission to 
 everyone and i dont want to set permissions one by one for all the users.

 What do you guys suggest?

 Any help or answers will be appreciated,

 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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[graylog2] How to define default streams on a reader role in Graylog v1.0.0

2015-03-18 Thread Aydin Doyak
Hey, 

I have a graylog v1.0.0 running on centos 6.6 like a charm. 

I have several stream and dashboard definitions in my server and i manage 
my graylog users with ldap integration which works great.

But i've a question :

When my ldap users login at the first time, graylog doesnt let them to see 
any stream or dashboards because all ldap users come with the default 
reader permissions which is normal.

I'd like to define some default streams and dashboards for reader 
permission, and make all users allow to see those streams default.

Is there anyway to do that? I do not want to give admin permission to 
everyone and i dont want to set permissions one by one for all the users.

What do you guys suggest?

Any help or answers will be appreciated,

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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.