By desing, there is no collision between different users, since all requests are executed in sequence (single thread). The only problem is that the server becomes unavailable for others if it executes a long search. This is why most users of large lobooks restrict their search to let's say the last month or so by default. This speeds up the search and limits the dead time for others. This can be done via the show last default = <days> directive.

As an administrator of the logbook you could add an additional attribute, e.g. "when" of type datetime.

Each entry would then have the unchangeable entry time and an addtional time, e.g. of the event you are describing in the entry.

For more details look here: elog:67712

No. The date/time tag is there to actually document the time when the log was made. If you are late, you are late.

Is it possible to enter past date in logbook

I forgot to enter log yesterday, is it possible to add up now?

Are there any known or reported daemon stability issues with an increase of concurrent users logged in to view and search entries, while the elog client is also adding 5 to 10 new entries every minute during a peak 2-hour period each day?

Point your browser to http://localhost:8080 as written in the documentation