I'm wondering if anyone out there has a good way to approach this; a point 
of contact,or a paid support option. We need a feature implemented in 
Graylog and realize the feature may not be valuable to everyone. Apparently 
we can't wait for the feature to be implemented through traditional means. 
I'm not sure why, but heads are starting to roll, even though this feature 
wasn't on anyone's radar until this Monday. 

Anyway, it's up to me to fork graylog2-server and graylog2-web-interface 
and add some simple features: 

   1. Modify graylog2-web-interface "Quick Values" widget to include an 
   "Export All to CSV" button, where the CSV contains *all* values matching 
   the query, not just those top 50
   2. Modify graylog2-server if necessary to make the 
   GET /a/search/fieldterms, or GET /a/csv, REST resources kick back a 
   distinct list of all terms, preferably using the chunked CSV approach. 
      1. The org.graylog2.indexer.searches.searches::terms() function 
      already accepts a "size" parameter, I just can't seem to pass the param 
      from the REST request, so the list is always truncated to 50 items
      2. Notice line 260 in org.graylog2.indexer.searches.Searches.java
      public TermsResult terms(String field, int size, String query, String 
      filter, TimeRange range) {
      if (size == 0) {
              size = 50;
      } 
   
Of course when I'm done I'll do a pull request to contribute it back if 
it's up to par. My problem right now is that while I've written several 
Graylog plugins, the server and web-interface have some interesting 
conventions and paradigms going on that I am not familiar with, and I'm 
having trouble finding the kind of documentation I'd need to get rolling. 
For example, it's hard to trace the REST routes from URL to controller and 
the rest of the MVC cycle. It is probably well known to others in the Java 
space, but not for me. 

I'm not looking for someone to hold my hand by any means, but sometimes 
it's nice to have someone there to say "oh, this is a Spring convention", 
or "we build the route programatically using a custom approach, check out X 
and Y". 

We're probably in this for the long term and will likely be contributing 
the better (more general) features back to the community. 

If anyone has some suggestions, I'd very much appreciate it!

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/62c58e55-5cbf-4dec-a20b-b69de00ea286%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to