# Behavior of Event Monitoring on Non-ESXi versus ESXi Servers

The following table details the behavior of event monitoring on non-ESXi versus ESXi servers.

Table 1. Event Monitoring on Non-ESXi Versus ESXi Servers
Event | Non-ESXi Server (Gateway, StandAlone, and DirectAgent) | ESXi (Indirect Agent)
--- | --- | ---
SysLog or email | Immediately after the LSA service is started. This includes new installations as well as restart of LSA services. | User should login at least once to the ESXi server after the Gateway service starts.
Syslog location | On Windows: Event viewer. On Linux: /var/log/messages | Events are logged in Gateway server's syslog location.
Differentiating syslog | No special attribute is added as part of the event description. | A corresponding server ID is added as part of event description, which helps the user to identify any particular event that belongs to a particular ESXi server.
LSA boot events | Boot events are handled for local controllers. | Boot events are not handled for ESXi controllers.
Time sync | Handled | Not handled
Alert configuration | Follows `config-current.json` | Follows Gateway's alert configuration.
SMTP server communication | LSA server communicates with SMTP server for email communication. | Instead of ESXi, Gateway server communicates with SMTP server for email communication.

Parent topic: Managing LSA on the VMware ESXi Operating Systems