# Behavior of Event History

LSI Storage Authority supports retrieving the list of previous events, also known as event history. LSA maintains the event history in three different log levels:

- `0` – Always read from firmware.

  - Firmware maintains a separate space to save event history, which can be retrieved using the `LSA.conf` file.

    - MegaRAID Behavior – The source of an event is firmware. All events are persisted in firmware and can be retrieved at any point in time.

    - Non-MegaRAID Behavior – The source of an event is Firmware, Driver, and StoreLIb. Firmware generated events can only be persisted and can be retrieved.

- `1` – By default, persists only non-MegaRAID events in the log file.

  - Non-MegaRAID events include IR/HBA.

- `255` – Persists all events in the log file.

  - LSA monitors the log location of the individual controller under $LSA_HOME/conf/monitor/logs.

  - The maximum number of events persisted in a file is 300. This can be configured through the `LSA.conf` file.

  - The maximum number of events that can be retrieved on a single page is 30. This can be configured through the `LSA.conf` file.

  - LSA maintains a set of events in the log file.

  - LSA starts maintaining the event history for Gateway, StandAlone, and DirectAgent installers from the time LSA is started.

  - For Indirect Agent installers, LSA maintains the event history from the time you log in and as long as LSA Service is running.

Parent topic: Managing LSA on the VMware ESXi Operating Systems