I had to revert, so this is from memory. I’m sure others may have already reported these, but if not:
I use graylog behind a proxy. Everything is working except the stream links from the menu. They are redirecting to the wrong place, and I get the 404 gorilla. Everything is fine if I access the backend directly.
For dashboards, I have some stacked columns. The problem is that in addition to the aggregates that I want, graylog is also adding all values combined as another data set.
I liked the ability to ‘play’ a widget’s query search. Is this hopefully coming back? I feel the workflow now is tedious and frustrating.
I look forward to using the new version when these things are addressed.
I use graylog behind a proxy. Everything is working except the stream links from the menu. They are redirecting to the wrong place, and I get the 404 gorilla. Everything is fine if I access the backend directly.
There might be an issue with your graylog config. Please have a look at this config section:
#### External Graylog URI
#
# The public URI of Graylog which will be used by the Graylog web interface to communicate with the Graylog REST API.
#
# The external Graylog URI usually has to be specified, if Graylog is running behind a reverse proxy or load-balancer
# and it will be used to generate URLs addressing entities in the Graylog REST API (see $http_bind_address).
#
# When using Graylog Collector, this URI will be used to receive heartbeat messages and must be accessible for all collectors.
#
# This setting can be overriden on a per-request basis with the "X-Graylog-Server-URL" HTTP request header.
#
# Default: $http_publish_uri
#http_external_uri =
For dashboards, I have some stacked columns. The problem is that in addition to the aggregates that I want, graylog is also adding all values combined as another data set.
I liked the ability to ‘play’ a widget’s query search. Is this hopefully coming back? I feel the workflow now is tedious and frustrating.
We did not implement it for this version but will bring something like this back for 3.3 which should be released hopefully in summer. In the mean time have a look at Show documents for value in the value actions.
