You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I suspect that Grafana expects a forever open connection to redis.. as the redis connection expires after 5-6 seconds of inactivity, Grafana doesn't handle this gracefully, expires the session, reconnects, and creates a new session. This is filling redis with several abandoned sessions. If i constantly refresh my Grafana browser, I stay logged in. If I wait 10 seconds and then refresh grafana, my session is expired (and I am logged out again). As a note, I am also using ldap for authentication which is why maintaining session state is important.
The text was updated successfully, but these errors were encountered:
I am attempting to set up a cluster of grafana servers -- in the mean time, is there a work around so my users don't keep getting logged out (other than going to a single grafana server or having connections never expire)?
is there a way to not have the redis haproxy close connections? other option is to switch to mysql or postgres session storeage (depending on what you use for main db)
Please include this information:
grafana-4.2.0-1.x86_64
graphite
CentOS 7-latest
Set redis up as a session cache
Sessions should sustain
Session expire after a few seconds
relevant grafana ini:
relevant haproxy config in front of redis:
I suspect that Grafana expects a forever open connection to redis.. as the redis connection expires after 5-6 seconds of inactivity, Grafana doesn't handle this gracefully, expires the session, reconnects, and creates a new session. This is filling redis with several abandoned sessions. If i constantly refresh my Grafana browser, I stay logged in. If I wait 10 seconds and then refresh grafana, my session is expired (and I am logged out again). As a note, I am also using ldap for authentication which is why maintaining session state is important.
The text was updated successfully, but these errors were encountered: