I am evaluating moving our centralized logging from elasticsearch/kibana to graylog. Our current setup has several external applications that link directly to specific Kibana searches by generating the proper parameters in the URL. Eg:
http://mycentral.log/app/kibana#/discover?_g=(refreshInterval:(display:Off,pause:!f,value:0),time:(from:'2016-09-14T17:20:00.000Z',mode:absolute,to:'2016-09-14T17:25:00.000Z'))&_a=(columns:!(_source),filters:!(),index:logstash-1,interval:auto,query:(query_string:(analyze_wildcard:!t,query:'*')),sort:!(timestamp,desc),vis:(aggs:!((params:(field:programname,orderBy:'2',size:20),schema:segment,type:terms),(id:'2',schema:metric,type:count)),type:histogram))&indexPattern=graylog_0&type=histogram As you can see, we can generate a URL on the fly that has control over most of the search and display functions available in Kibana. We use this to link directly to specific application logs for less technologically inclined staff. It appears from the URL of the Graylog web interface that it uses some kind of hash to link to specific content. Is there a way to generate these on the fly to link to specific information within the system? I have searched for a while today and I can't seem to find any documentation on the subject. Thanks in advance for any assistance. -- 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/b5dd50cd-03ab-4b67-bdfa-a9f67f7d7e0a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
