docs/designs/redfish-eventservice.md

22 - [Redfish event logging](https://github.com/openbmc/docs/blob/master/redfish-logging-in-bmcweb.md)
29 - [Upgrade connection for SSE](https://gerrit.openbmc.org/#/c/openbmc/bmcweb/+/13948/)
463    events and how the http/https connections are handled in bmcweb.
487     [link](https://github.com/openbmc/docs/blob/master/redfish-logging-in-bmcweb.md)
516 bmcweb webserver and synced with config json file for restoring and persisting
578 be cached in bmcweb to identify the new events in redfish event log file.
581 events logged before bmcweb service start.
673 consumers(Telemetry service or event log service). In SSE connection, bmcweb
675 failure/timeout/congestion. If there is error like connreset/badf, bmcweb will
692 - During bmcweb service start, it gets all the configuration and subscriptions
707 The bmcweb service will update the config store data including EventService
709 /var/lib/bmcweb/eventservice_data.json). This will be persistent across the
710 bmcweb service restarts or bmc reboots and loads this while initializing bmcweb
716    connection can't be re-established when bmcweb service or BMC goes for
721    Limitation: If bmcweb server closes abruptly due to some reasons like
722    watchdog trigger, then bmcweb can't send close connection event to SSE
752 bmcweb server keep the connection open and conform to the HTML5 Specification
753 until the client closes the socket. The bmcweb service should sent the response
775 filters, bmcweb create an EventDestination instance in the subscriptions
776 collection. Once bmcweb receives the SSE stream request, the open connection
780 [link](https://gerrit.openbmc.org/#/c/openbmc/bmcweb/+/13948/) for details on
786 it. All bmcweb related security threat model applies here.
789 at any time and close the connection. The bmcweb server can delete the
795 - Server(bmcweb) can close connection and send notification to client with
799 bmcweb service doesn't know the client connection state. This is limitation on
800 SSE connection. In such scenario bmcweb service may delete a subscription, if
805 - The SSE subscription data is not persistent in nature. When bmcweb restarts or
806   BMC reboots, client should re-establish the SSE connection to bmcweb to listen
843 Unlike the SSE (where bmcweb act as server) push style events works in different
953 specific to redfish/bmcweb and not consumed/updated by any other processes in
979 connections on bmcweb can slow down the performance.
1009 - Reboot BMC or reset bmcweb service and check all "push style events"
1011 - Reboot BMC or reset bmcweb service and check all "SSE" subscription data is
1131      connection and so bmcweb service can close and delete the subscription