I don&#x27;t really understand what the heavy emphasis on &quot;real-time&quot; here.<p>I mean it&#x27;s log&#x2F;event aggregation for ops insight.  Unless the whole system is some tightly coupled feedback loop into an unsupervised machine learning model where the whole thing has actual hard-real-time requirements (something which might well be impossible to build), then there&#x27;s no possible way that having a second or two delay, between a message being created and when you can actually see it, can possibly matter.<p>I mean you don&#x27;t have someone with instantaneous reflexes and resolution ability sitting there 24&#x2F;7 with their eyes peeled as a stream of thousands of log messages flies by.<p>The whole premise seems spurious.  Is it really necessary for every startup and their uncle to delude themselves into thinking that their use case is &quot;mission critical&quot; or &quot;carrier grade&quot; or whatever?<p>Auth0 provides basically &quot;login as a service&quot;.  Its not like they&#x27;re managing the access control to nuclear launch codes or something.<p>Unless some medical device manufacturer was stupid enough to make a critical surgical assistance device require an internet connection, a WAN round-trip on unreliable networks, and reliance on a 3rd party service in order to start operating it... how can this service being down possibly be anything more than an annoyance?  What&#x27;s the worst possible scenario?  A session has to be rebuilt?  A user has to make an extra login attempt?<p>By their own admission the service has gone down already due to the old system architecture.  How many babies died?