Poor User Experience Under Adverse Network Conditions

A customer from a service provider in Europe wrote to tell us that the experience of using Graylog over a remote network connection can be difficult and frustrating.

## Expected Behavior

When network connectivity is lost, unsaved information in the browser should not be lost. When connectivity is restored, the user should be able to resume whatever activity they were performing before the interruption.

## Current Behavior

Customer Message:

"Hi,

the Graylog Webinterface is sometimes quite sensitive to network quality between it and the server. Especially when working from a bit more remote, we often observe the "Server Unavailable Modal", often for just a split second. While it's just very brief, the pain point is that all ephemeral objects are lost. Let it be aggregation widgets during analysis, dashboard changes or whole configuration dialogs.

I suppose this is not trivial to mitigate, since it changes how all the requests from the Webinterface ought to behave. But its worth dicussing, as it has impact on the quality of service perceived by technicians and customers alike."

## Possible Solution

## Steps to Reproduce (for bugs)

1.
2.
3.
4.

## Context

Time spent configuring something is lost, whether aggregation widgets during analysis, dashboard changes or whole configuration dialogs. Customer and technician frustration impacts the service provider and Graylog.

## Your Environment

* Graylog Version:
* Java Version:
* Elasticsearch Version:
* MongoDB Version:
* Operating System:
* Browser version: