hi Kay! Thanks a lot for your reply. I sent you email with the changelog and suggestions.
regards, Asad On Wednesday, 11 June 2014 07:40:26 UTC+9, Kay Röpke wrote: > > Hi Asad! > > I would be greatly interested in your plans and/or code around these > areas! > Of course we are very happy to accept contributions and are very > grateful for any work that your team is willing to put into graylog2. > Please feel free to contact me at [email protected] to schedule a time to > talk about your proposed changes, or I'm also happy to discuss these > on the mailing list, of course. > > If you could point me to a github repository, I'm more than happy to > review any changes you have! > > Many thanks, > Kay > > On Mon, Jun 9, 2014 at 2:53 AM, Asad Mehmood <[email protected] > <javascript:>> wrote: > > graylog2 v 2.20 is great with a lot of new features and it's a lot more > > stable than previous one, Though we modified the old source code but > before > > we could commit it back to graylog2 the new version was released, > however we > > are forked again the latest version and once the developer finishes we > will > > commit it back to graylog2 git repository. > > > > There are few changes that we would like to do to graylog2-server and I > > would really appreciate if the authors can help us guide so instead of > > wasting time on finding the right place to change we can proceed with > change > > quickly. > > > > 1. currently New Elasticsearch index is created when a certain number of > > documents are inserted in index, we would like to give users two options > in > > config. > > > > > > elasticsearch_index_close_cond: {count, time} > > > > if count > > elasticsearch_max_docs_per_index = N > > > > if time > > elasticsearch_index_close_interval = (1d, 1w, 1m) > > > > > > 2. IF possible we would help graylog2 team by adding Routing option for > ES, > > currently we experience the issue of balancing between cost of operation > and > > duration of logs we want to keep in our system, we are looking for an > option > > where the latest 1 week logs stay in high I/O performance nodes and old > one > > moves to low performance I/O. > > > > any guidance from the graylog2 team will be highly appreciated in this > > regard. > > > > 3. Scheduled report delivery. > > > > > > thanks > > > > Asad > > > > -- > > 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 [email protected] <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 [email protected]. For more options, visit https://groups.google.com/d/optout.
